Loading...
E depụtara isiokwu a site na: Okporo Ụzọ Ihe Àmà, akwụkwọ na-enweghị onwe ya nke kpuchiri nzuzo nchekwa: ZK, FHE, MPC, TEEs, na njirimara decentralized. E bipụtara mbụ dị ka "Kedụ ebe Zcash ruru na nkpughe nhọrọ, yana ihe fọdụrụ" na Septemba 7, 2026. E gosipụtara ya site n'ikike onye edemede dị ka akụkụ nke Onyinye Zcash Community #339Site n'aka Stephen Webber.
In Zcash, a viewing key lets an account holder reveal shielded transaction history to a party of their choosing. The keys are live and user-controlled. Builders and policy advocates are still at work on getting them to serve the compliance workflows that could use them.
N'ụbọchị 17 Ọgọstụ, kọmitii na-ahụ maka onyinye Zcash zutere iji tụlee atụmatụ a kpọrọ Shielded Compliance Bridge. Deborah Olaboye bụ onye nyere aka mepere emepe nke ọrụ ya gụnyere ebe nchekwa nkọwapụta arụmọrụ Ethereum wuru ihe ngosi echiche nke nwere igodo nlele zuru oke, nyocha mkpokọta mgbochi megide testnet indexer ma buru "ihe ntinye" na mpaghara memo Zcash jikọtara nnyefe echekwara na ndekọ Iwu njem ọpụpụ. O rịọrọ ka enye ego iji wuchaa ya, mana kọmiti ahụ jụrụ.
Ihe ahụ bụ: echiche nke onwe onye was that compliance integrations are shaped by the specific exchange or institution that will use them, that there are no common standards to build against, and that without a partner asking for the tool, adoption was unlikely. The same meeting declined other proposals for similar reasons, one for a "programmable selective disclosure" virtual machine, and a privacy and trust architecture framework, which included a map of US legal issues.
Of course, these decisions are not a sign that nobody wants this. Considered alongside the rest of the year, it is the opposite. Binance made a protocol-level ask in 2024 and had a ZIP within the year. Gemini has run shielded withdrawals under regulatory supervision since 2020. The ecosystem stood up a Washington policy organization in June and an institutional-integration shop in August. What the committee said, in effect, is that the need has not yet been written down as a requirement anyone can build to.
A shielded Zcash address is controlled by a spending key. Derived from it are viewing keys that can read transaction data without being able to move funds. The full viewing key sees incoming and outgoing transactions for the account, the incoming viewing key sees only received funds, and the outgoing viewing key lets a sender reconstruct what they sent. Since ZIP 316 Ihe e dere n'ala ala peeji, a na-agbakọta ha n'ime igodo ngosi zuru oke, otu zuru ezu ma nke ọzọ abata, ejedebere akaụntụ, ebe akaụntụ bụ ọnọdụ dị na osisi isi akpa ego ahụ. ZIP 32 Ụlọ ọrụIgodo nlele zuru ezu na-ejikọta ihe ndị dị iche maka ọdọ mmiri ọ bụla a na-echebe akaụntụ ahụ, ma nwee igodo ọha nke nwere nghọta doro anya. N'ihi ya ịkekọrịta otu ga - ekpughe usoro kwụ ọtọ yana akụkọ ntolite echekwara.
A viewing key is in this sense retroactive. It decrypts the account's entire history from the moment the account was created, and it cannot be withdrawn once shared, short of moving funds to a new account. There is no per-transaction viewing key and no time-bounded one. Josh Swihart, chief executive of ZODL, the company formed this year by the protocol's former ECC engineering team, confirmed this, also mentioning that per-transaction payment disclosure is "not implemented anywhere."
zcashd, mbụ akwụkwọ ọnụ, Ẹnam ekese abụọ RPC usoro, z_getpaymentdisclosure na nke a: z_validatepaymentdisclosure, nke na-eme ka onye zitere ya gosi otu ugwo nye ndị ọzọ. Ihe a bụ ihe e dere n'akwụkwọ ozi ahụ, ọ bụghị akwụkwọ ego. Akwụkwọ RPC na-eme ka ha bụrụ nnwale, ndị nwere nkwarụ ma ọ gwụla ma onye ọrụ ahụ setịpụrụ ọkọlọtọ atụmatụ nyocha, yana itinye "ZIP Nkwupụta Ịkwụ Ụgwọ Ọrụ Na-aga n'ihu". ZIP a, 303, bụ ugbu a akara ẹsịn, na ya nọchiri, ZIP 311 (Ụlọ ọrụ na-ere ahịa), na-anọgide a draft enweghị mmejuputa atụkwasị. Usoro kpuchie naanị Sprout ọdọ mmiri, mbụ 2016 echebe ọdọ mmiri ma ọ dịghị mgbe e gbasaa ka Sapling ma ọ bụ Orchard, nke ahụ bụ ikwu ndị ọdọ mmiri na-ebu bụla oge a chebere azụmahịa. zcashd onwe ya ọ na-eru ọgwụgwụ ndụ ya. on July 18, 2026, a planned halt ahead of the Ironwood upgrade. Neither Zebra, the Zcash Foundation's consensus node, nor Zallet, the successor wallet, ndepụta ndị dị na ya a ngosi usoro. N'ihi na ọdọ mmiri ndị dị mkpa, kwa-transaction ngosipụta anọgide a imewe n'uche.
Ebumnuche ahụ ka dị ndụ, mana ọ gafere karịa ihe o yiri na July. ZIP 231 (mkpụrụ akwụkwọ ozi), memo bundles, is the draft that would make room for it: Swihart described memo bundles as the eventual basis for an authenticated reply-to that could function as proof of payment, and the dependent draft, adreesị nzaghachi a kwadoro, chọrọ ihe àmà buru oke ibu maka ugbu a memo ubi. Memo ùkwù bụ azụmahịa format mgbanwe, na ise òtù ịhazi usoro nke ọrụ ahụ ga-eme ka ndị ahịa mara banyere ya ma ọ bụrụ na ha nwere ike iji mee ihe n'ụzọ ziri ezi. Ntuliaka NU7 nke ndị ji mkpụrụ ego eme ihe. agreed in August that format changes are out of scope for NU7 and in scope for the upgrade after. The vote itself, which runs from August 25 to September 14, put issuance, fee policy, block spacing and Sprout deprecation to holders; disclosure was not on the ballot. The older route, ZIP 311, needs no consensus change but remains a draft with no implementation and no Orchard coverage.
Ya mere, ihe ụgbọ mmiri taa bụ akaụntụ-scope nlele igodo, zuru ma ọ bụ na-abata naanị, retroactive, irrevocable na òkè ke onye nwe akaụntụ si nnwale, na azụmahịa larịị ngosi on ụzọ.
Disclosure mechanisms, in Zcash or anywhere else, can be located on the following: What is revealed (scope). To whom (grantee). When the grant takes effect and how far back it reaches (timing). Whether it can be withdrawn (revocability). And who initiates it, the data subject or an authority (initiation).
Compliance regimes are requirements over those, and architectures are positions on them. Zcash's viewing keys are by design broad scope, holder-chosen grantee, fully retroactive, irrevocable, user-initiated. The requirement side, as it is applied by exchanges and supervisors, tends to be scoped to a relationship or a period, granted to a named institution or its analytics vendor, continuous from onboarding forward, revocable when the relationship ends, and initiated by the institution as a condition of service.
A na-akpọ ihe abụọ a nhọrọ ngosi. Na ụwa nzere, nchịkọta nhọrọ pụtara igosi otu ụdị njirimara site n'aka akwụkwọ ikike e debanyere aha ya ma ghara ikpughe ndị ọzọ, nke bụ ihe ọ dị mkpa iji mee ka onye ahụ mara banyere nkwenye gị. SD-JWT, ISO mdoc na BBS + mbinye aka e wuru ime. Nkeji nke ngosi bụ àgwà, oge ahụ bụ oge ngosipụta, onye nwe ya kpebiri kwa mmekọrịta.
N'ụwa nke ịkwụ ụgwọ echekwara, okwu ahụ pụtara ikpughe data azụmahịa nye onye ahọpụtara, ebe otu bụ akụkọ ihe mere eme akaụntụ na oge ọ bụla a ga-enyefe igodo.
Swihart kwuru na naanị usoro iwu-ọkwa nke otu ndị ọrụ injinia natara site n'aka Binance, bụ onye chọrọ nkwa nkwenye doro anya maka ego itinye aka na Jenụwarị 2024. Nzaghachi ìgwè ahụ bụ: ZIP 320 Ọ dịghị onye na-eme ya., transparent-source-only addresses, and the ZIP text indeed records the origin "as required by Binance." A TEX address is an ephemeral transparent pass-through that guarantees the exchange receives funds from a transparent source. It gives the exchange a return path without giving it the sender's history. The one accommodation the protocol made to an exchange discloses exactly what the exchange asked for and nothing more.
Since the Sapling upgrade, Swihart argues, there has been no technical reason for an exchange not to support shielded transactions, because proving is fast, exchange customers are already identified at onboarding, and enhanced due diligence exists for the cases that need it. On that view the span between the machinery and the compliance workflow is not really a missing primitive, but in fact a missing conversation.
Divij Pandya is working the other end of that conversation. He is executive director of Pretty Good Policy for Zcash, the Washington policy organization stood up in June as a continuation of an earlier ECC-led initiative, and his organization's project is to get viewing-key disclosure recognized as an acceptable compliance mechanism in a document a compliance officer can cite. To his knowledge, he said, no regulator has yet engaged with viewing keys as an instrument. PGPZ's scope, naturally, is recognition rather than builder guidance. A tool cannot be specified against a requirement until someone with authority has ruled on the instrument, so recognition is the upstream step. The organization's filings are signed by Paul Brigner as PGPZ's founder and as ZODL's chief policy and regulatory officer, so the policy and engineering efforts share an officer as well as a thesis.
A July 21 statement for the record to a House subcommittee on FinCEN oversight describes Zcash as having "selective disclosure capabilities, allowing users to voluntarily share transaction details through the use of viewing keys with auditors, tax authorities, or compliance officers," and refers to zero-knowledge proofs "paired with selective viewing keys" for proving specified facts. A comment letter on FinCEN's docket, FINCEN-2026-0101-0050 Nkwupụta nke ndị isi obodo na-ahụ maka nchekwa., argues, per Pandya, that viewing keys and selective disclosure should be acceptable compliance mechanisms. The open question they put to the regulator is one of granularity, whether account-scoped, all-history disclosure is enough for "targeted transaction information," or whether the answer waits on ZIP 231.
Ruo mgbe nke ahụ ga-edozi, ndị otu na-agbaso iwu chere ihe mgbochi ihu na a pseudonymous forum poster, strahncryptography, kọwara in the discussion of Olaboye's proposal: they follow the rule to the letter, and will not adopt an unrecognized path without a regulator's or a law firm's attestation, however sound the cryptography. Any disclosure design that attaches a reference to a transaction proves only the last hop, and the last hop could be the depositor themselves. A viewing key has the same limit. It reveals the account holder's transactions, not where the counterparties' funds came from, which is the question a sanctions screen asks.
Viewing keys clear the bar wherever the requirement is proof by the data subject of what happened, like provenance of a deposit the depositor chooses to explain, a voluntary audit, a tax filing, a proof that a specific payment was made. Those are user-initiated, retroactive, one-time disclosures. They do not clear the bar where the requirement is continuous monitoring from onboarding forward, sanctions screening against counterparties the account holder does not control, scoping to a period or a relationship, or revocation at offboarding.
Gemini anabatala ịdọrọ ego gaa na adreesị echedoro kemgbe afọ 2000 . Septemba 2020, when a spokesperson credited ongoing conversations with regulators, extended that to the Orchard pool in November 2025, and to the post-Ironwood pool two days after activation in July 2026. It accepts deposits sent from shielded addresses into transparent custody. Kraken's ndepụta adreesị iwepụ na-akwado naanị adreesị ZEC doro anya, Coinbase dịkwa ka ihe ngosi dị ọcha, Binance chọrọ TEX. Ihe ọ bụla isi mgbanwe gbanwere ma nye bụ nchekwa echedoro, adreesì nkwụnye ego ezere, ma ọ bụ usoro ọrụ nke igodo nlele onye ahịa ga-aga.
The ingestion na-ewu a oyi akwa ala. N'etiti ndị amụma ke coinholder eduzi azu ike onyinye gburugburu na-enyocha nke a September are ZecBooks, a Mac bookkeeping tool that imports a view-only key, classifies notes, and exports a scoped package of rows for an accountant without granting lasting access to the wallet; ZecLedger, a read-only cost-basis and reconciliation tool built around a unified full viewing key, tested against a mainnet wallet; and seer-sync, a chain-sync engine that takes a viewing key so a payment processor or accounting system can observe shielded activity without holding spending keys. None is an exchange workflow, and none has a regulator's attention. Each is the accountant-facing half of the same problem, built by one or two people without a partner asking, and ZecBooks' scoped export is selective disclosure operating at the interface where it is most often needed first: between a shielded user and the person keeping their books.
Ndị na-ewu Zcash nọ n'ọrụ nsogbu nke ụlọ ọrụ nzuzo niile nwere.
In Zama's confidential-EVM design, an access control list determines which addresses may request decryption of a ciphertext, and a threshold network of key-management operators performs the decryption on request. That moves the grantee axis from a key the user hands over to a permission a contract records, and makes initiation programmable, since a contract can grant an auditor decryption rights as a condition of use. It does not make disclosure revocable in the sense a compliance officer means, because a ciphertext already decrypted stays decrypted, and it trades a user's key custody for operator honesty as the trust base. Asset-level auditor keys, of the kind in Solana's confidential transfer extension and Avalanche's encrypted ERC design, fix a grantee at the token level in that the issuer or a designated auditor can read balances and transfers for that asset.
Inco ebipụtala akwụkwọ akụkọ na-ekwu maka ihe ndị a. ihe owuwu. maka pre-kọwaa ikiri, ebe ohere na-ofu ke isi ihe onwunwe n'oge azụmahịa oge, megide programmable ele access, ebe ikike nke ikiri bụ nkwekọrịta ala nwere ike e nyere, scoped na napụrụ mgbe.
Kedu ihe na-ekewa igodo nlele site na usoro ọrụ nnabata?
A viewing key discloses the account holder's own history. Sanctions screening and continuous monitoring ask about counterparties, where the funds on the other side of each transaction came from, and that is precisely the information a shielded pool exists to withhold. Nobody has yet shown a design that answers a counterparty question without either a transparent ledger or a trusted third party.
Ọ bụrụ na ngwugwu memo abanye n'ọkwa mgbe NU7 gasịrị ma nzaghachi-adreesị draft sochiri, "ozi azụmahịa ezubere iche" na ntinye akwụkwọ PGPZ ga - abụ nke nkịtị. Nke ahụ bụ opekata mpe nkwalite abụọ dị anya, azịza nchịkwa rutere na usoro nhazi oge onye nlekọta.
The demand is easily seen by the number of people building toward it. What is missing is a fixed requirement for privacy-preserving disclosure. Zcash is the ecosystem where that decision is being negotiated in the open, by engineers, advocates, builders, an exchange and a grants committee who seem to agree on the destination and are arguing about the order of the steps. It is also being worked by solo developers who started on the accounting layer without waiting for the requirement to be written.
*Nkwupụta: a kwadoro mpempe akwụkwọ a site na onye ọrụ nke ụlọ ahịa ahụ. Zcash Community Grant (Nkwado nke Obodo)ZCG enyochaghị ma ọ bụ kwado edemede a tupu mbipụta ya. *
Ibe ndị metụtara ya: Igodo Nlele · E jiri ihe nzuzo tụnyere ya.