On this page
  1. Shielded and transparent are different transaction paths
  2. What zero-knowledge proofs do
  3. The 2026 Ironwood upgrade
  4. ZEC supply and network security
  5. Wallet support is part of privacy
  6. Where practical limitations appear

Zcash is a privacy-focused cryptocurrency network with ZEC as its native coin. Its defining feature is the ability to validate shielded payments without publicly disclosing all of the information normally visible in a blockchain transaction. As of October 8, 2026, the network remains active, and its July 2026 Ironwood upgrade is an important part of understanding the current privacy architecture.

Shielded and transparent are different transaction paths

Zcash supports both transparent and shielded activity. Transparent transactions expose information in a way more comparable to ordinary public-ledger payments. Shielded transactions use cryptographic techniques to protect payment details. Simply holding ZEC does not mean that every transfer the holder makes is private.

The sender's wallet, recipient's supported address type and route through services all matter. An exchange may support ZEC while limiting the kinds of addresses it accepts. Moving value through a transparent endpoint can reveal information that would not be visible in a fully shielded transfer.

This distinction corrects a common misunderstanding: Zcash does not make all users completely anonymous in every circumstance. A service can know a customer's identity even when some on-chain details are protected. Information disclosed outside the blockchain can also affect privacy.

What zero-knowledge proofs do

A zero-knowledge proof lets someone demonstrate that a statement is true without revealing all of the underlying information. In a payment system, the protocol needs assurance that the transaction follows its rules, including that value is not created improperly and that spending is authorized.

The cryptography separates those validity checks from public disclosure of sensitive payment data. It does not remove the need for correct software, sound mathematics or secure key handling. A bug in an implementation or an incorrect assumption in the proof system can still have serious consequences.

The 2026 Ironwood upgrade

The official Zcash upgrade page states that Ironwood, also called NU6.3, activated on July 28, 2026, at block 3,428,143. It introduced a new shielded pool and restricted the original Orchard pool, with funds leaving Orchard passing through the protocol's turnstile to enter Ironwood.

The project describes this as a response to an Orchard soundness vulnerability discovered in late May 2026 and says the new pool improves independent verification of supply integrity. Those are security changes, not simply a faster user interface. Its upgrade page specifically says the release did not include performance improvements.

For users, the practical consequence is that old wallet instructions and explanations of supported pools may be incomplete. Updated software needs to understand the active protocol. A wallet's familiar name is not enough if the installed version predates a necessary network change.

ZEC supply and network security

Zcash's monetary design has a maximum of 21 million ZEC and a declining issuance schedule. It uses proof-of-work mining. The subsidy system also has a history of funding development and ecosystem work, with allocation rules changing through network decisions.

A maximum supply and privacy features answer different questions. The supply limit describes issuance rules; shielded cryptography governs what observers can learn about transactions. Neither guarantees a market value. Mining incentives, software reliability and the health of supporting infrastructure remain relevant to the network's operation.

Wallet support is part of privacy

A wallet must do more than display a ZEC balance. It needs to handle the relevant address formats, scan for the user's transactions and construct supported payments. Unified addresses can package receiver information for compatible software, but a sender still needs to use an appropriate transaction path.

Backups and viewing capabilities also deserve attention. Spending authority and the ability to view transaction information are not always the same permission. Sharing access for accounting or auditing purposes should be understood separately from handing someone the ability to move funds.

Where practical limitations appear

Privacy-focused assets face uneven service support. An exchange listing may change by jurisdiction, and a venue may accept only particular deposit or withdrawal types. A trading page alone does not establish support for shielded transfers or a currently functioning withdrawal route.

Zcash's value as a technology is that it makes privacy a protocol capability rather than relying solely on users obscuring a public transaction trail. Its limits are equally important: privacy is shaped by the whole payment path, the software version and the information shared with counterparties. Comparing it with a public payment network such as Bitcoin Cash begins with those differences, not with an absolute anonymity claim.