What the evidence supports today
Shielded transfers can conceal transaction details
SupportedZcash uses zero-knowledge proofs so shielded transactions can be validated under consensus rules without publicly revealing their protected transaction data; Orchard uses the Halo 2 proving system without the earlier trusted setup.
Layer North view: This is protocol-level privacy capability, not proof that every wallet, exchange or transfer uses it correctly. Transparent Zcash activity remains public.
Z02Z03Z04A 2026 Orchard circuit flaw reached mainnet
SupportedThe Zcash Foundation disclosed that a critical Orchard soundness vulnerability was found on 29 May 2026, followed by an emergency soft fork that disabled Orchard actions and NU6.2 activation with a corrected circuit. The Foundation said the turnstile showed supply remained intact.
Layer North view: The response limited the disclosed impact, but it demonstrates that a proof-circuit error can create direct supply-integrity risk and require emergency network coordination.
Z08Privacy quality and mining control are not fully measured
UnresolvedThis draft lacks a current pool- and entity-adjusted hashrate map, standardized shielded-pool usage and leakage measurements, wallet-by-wallet privacy behavior, and an independent chain-level reconstruction of the 2026 emergency response.
Z02Z04Z08Snapshot, not a live ticker
Each value is tied to a named source and observation date. Market rank is context—not a quality score.
CoinGecko API snapshot; rank is not evidence of privacy quality, network security or executable liquidity.
As of 2026-08-13 11:50 UTC Z01Consensus supply cap under the documented issuance framework; supply integrity also depends on correct consensus and proof-circuit implementation.
As of Accessed 2026-08-13 Z05Z09Miner / Zcash Community Grants / protocol lockbox under the post-November-2024 funding model.
As of NU6 funding model Z06Z07CoinGecko total-supply field rounded from 16,874,579.853 ZEC; not an independent consensus audit.
As of 2026-08-13 11:50 UTC Z01Zcash supports privacy, but privacy is not universal
Shielded and transparent transfers coexist
SupportedOfficial guidance says wallets may shield all transactions, offer a privacy choice, or support only transparent activity. Transparent addresses expose wallet and transaction information on the public chain.
Layer North view: Zcash should not be described as making every transfer private. The actual anonymity set and metadata leakage depend on pool usage, wallet behavior and counterparties.
Z02Z04Orchard removed the earlier setup ceremony
SupportedNU5 introduced Orchard using Halo 2, which the project describes as removing trusted-setup dependence while supporting shielded mobile payments.
Layer North view: Removing one trust assumption does not remove circuit, implementation, wallet or endpoint risks, as the 2026 soundness incident illustrates.
Z03Z08Wallet construction affects privacy
SupportedZIP 315 recommends long-term shielded storage and warns that shielding from transparent addresses can link inputs or leak information to recipients and viewing-key holders.
Layer North view: A valid shielded transaction can still have weaker practical privacy because of its transaction graph or wallet construction.
Z04A capped issuance schedule also funds miners and ecosystem work
The current framework retains a 21 million cap
SupportedZcash documentation defines a 21 million ZEC maximum and a proof-of-work block subsidy that declines under the current halving schedule.
Layer North view: The cap constrains scheduled issuance, but confidence in realized supply also requires correct node and zero-knowledge circuit behavior.
Z05Z09Twenty percent of subsidy funds development paths
SupportedUnder NU6, 8% of block subsidy goes to Zcash Community Grants and 12% goes to a protocol-tracked lockbox; 80% goes to miners.
Layer North view: The lockbox creates visible earmarking, but its official description says no withdrawal mechanism was defined, leaving future access to community and protocol decisions.
Z06Z07Issuance smoothing remains a proposal
QualifiedZIP 234 proposes replacing step halvings with a smooth reserve-based curve while retaining the 21 million cap, but the ZIP index labels it Draft and a candidate for a future upgrade.
Layer North view: It must not be described as current policy until the relevant network upgrade is selected, implemented and activated.
Z09Z10Governance combines community signals with institutional coordination
Consensus upgrades are not governed by a universal coin vote
SupportedThe network page describes community polling and advisory processes, while the Zcash trademark agreement requires the Zcash Foundation and Electric Coin Company to agree to a network upgrade that creates a new consensus protocol.
Layer North view: Practical governance spans community sentiment, ZIP authors, implementers, miners, node operators and two trademark parties rather than one on-chain token-holder mechanism.
Z06Emergency response can restrict a shielded pool
ObservedThe 2026 response used an emergency soft fork to disable Orchard actions temporarily and then activated NU6.2 with the corrected circuit.
Layer North view: This is evidence of remediation capacity and evidence that users can depend on rapid coordination among core engineering and node-operator groups.
Z08Cryptographic assurance, mining security and liquidity need separate tests
Supply-integrity claims require circuit-aware review
QualifiedThe Foundation said the chain's turnstile confirmed intact total supply during the Orchard incident, while planned NU6.3 work explicitly focuses on strengthening confidence in supply integrity after the vulnerability.
Layer North view: A bounded supply rule is only as reliable as the cryptography, implementation and monitoring that enforce it.
Z08Z11Mining concentration is unresolved
UnresolvedZcash remains proof of work under the reviewed current rules, but this draft has not reproduced pool, beneficial-owner, hardware, hosting or geographic concentration.
Z05Z06Executable market liquidity remains Not Rated
UnresolvedCoinGecko ranked ZEC #15, but this review has not measured normal and stressed spreads, depth, slippage, venue concentration, shielded withdrawal support or service interruptions.
Z01Material risks and reassessment triggers
Impact labels are editorial judgments, not forecasts of price direction. Unsupported likelihood estimates remain unrated.
Proof-circuit and supply integrity
SupportedA critical Orchard soundness bug reached mainnet and required emergency restriction and a corrected circuit, even though the Foundation reported no supply breach.
Reassess when: A new circuit flaw, independent supply audit, pool migration or supply-integrity upgrade occurs.
Z08Z11Privacy implementation and metadata leakage
QualifiedShielded proofs protect transaction data, but transparent transfers, wallet construction, pool choice and network metadata can weaken practical privacy.
Reassess when: Shielded adoption or wallet defaults change materially, or a privacy vulnerability is disclosed.
Z02Z03Z04Mining and infrastructure concentration
UnresolvedProof of work is documented, but current hashrate, pool entities, hardware and hosting have not been independently mapped.
Reassess when: A reproducible entity-adjusted mining and infrastructure map is completed.
Z05Z06Governance and development funding
QualifiedCommunity input is visible, while consensus upgrades and lockbox access depend on institutional, implementation and node-adoption coordination.
Reassess when: Trademark control, funding allocation, lockbox access or upgrade governance changes materially.
Z06Z07Z10Executable market and shielded liquidity
UnresolvedMarket rank does not establish executable depth, venue resilience or the ability to deposit and withdraw shielded ZEC during stress.
Reassess when: Standardized depth, slippage, venue and shielded-transfer availability tests are completed.
Z01Z02Is ZEC a good investment? Evidence to test, not a recommendation.
The report does not issue a price target. It shows the observations that support the case, the countercase, and the signals that could change either.
- Zcash provides protocol-level shielded transfers and optional selective transparency.
- The 21 million cap and subsidy allocations are documented in consensus and upgrade materials.
- The 2026 Orchard response shows that the ecosystem can coordinate an emergency restriction and corrected upgrade.
- Optional privacy can be weakened by transparent activity, wallet behavior and metadata leakage.
- The Orchard incident shows that cryptographic implementation faults can threaten supply confidence.
- Mining concentration, governance control and executable shielded liquidity remain incompletely measured.
- Shielded-pool balances, transaction composition and wallet privacy defaults.
- Independent supply reconciliation and the migration path following the Orchard vulnerability.
- Entity-adjusted mining-pool, hardware and hosting concentration.
- Funding-stream, lockbox and network-upgrade governance decisions.
Claim-to-source record
Primary records establish documented rules and project-reported status. Dated measurements add observable context; neither substitutes for independent market, legal, or counterparty evidence.
Limitations, disclosures and change log
Known limitations
- Vinoth Kanna is the named analyst, but analyst sign-off has not been recorded for this draft. Jack General is the named reviewer; reviewer approval and independence have not been confirmed.
- The 2026 incident account is a first-party Foundation disclosure and has not been independently reconstructed in this draft.
- Shielded usage has not been converted into a standardized anonymity-set or metadata-leakage measurement.
- Mining pools and hashrate have not been resolved to beneficial owners or common infrastructure.
- No standardized executable-liquidity or shielded-withdrawal stress study is included.
- Market rank is a dated CoinGecko snapshot, not a durable fact or quality score.
Report disclosure
- Sponsorship
- No project sponsorship has been disclosed for this draft as of 13 August 2026. This statement has not received final publication sign-off.
- Affiliate links
- No affiliate links appear in this report.
- Holdings
- As of 13 August 2026, Vinoth Kanna and Jack General disclosed no crypto holdings or other material conflicts. These are personal disclosures, not independently verified statements.
- Automation
- Automation assisted source collection and drafting; named human verification and sign-off are pending.
Created a noindexed internal Zcash evidence draft covering optional privacy, capped issuance, development funding, governance and the 2026 Orchard circuit incident.