Zcash targets July 28 launch for Ironwood network upgrade

Zcash targets July 28 for the Ironwood network upgrade, a move designed to replace the compromised Orchard pool and investigate whether counterfeit tokens were minted through a recent vulnerability.

The upgrade represents the protocol's response to a critical flaw discovered earlier this year that allowed potential creation of fake ZEC tokens without detection. The Orchard shielded pool, which handles private transactions, becomes the primary focus of remediation efforts under Ironwood.

Replacing the Orchard pool carries significant implications for Zcash's privacy guarantees. The pool's compromise raised questions about the integrity of the network's zero-knowledge proof system, the cryptographic foundation enabling shielded transactions. The July 28 timeline gives developers roughly two months to finalize code and coordinate node operators for the mandatory upgrade.

The investigation into counterfeit token creation remains incomplete. Zcash developers have not definitively confirmed whether the bug resulted in any unauthorized ZEC minting before discovery. This uncertainty weighs on market confidence, as a successful exploit could mean Zcash's total supply exceeds the stated 21 million coin cap. Any evidence of phantom coins would fundamentally undermine the asset's scarcity narrative.

Ironwood extends beyond remediation. The upgrade introduces performance improvements and enhances the protocol's ability to detect similar vulnerabilities through improved cryptographic verification mechanisms. Zcash developers signaled commitment to preventing future compromises of shielded pools, which represent the network's core privacy value proposition.

The timing matters. Zcash trades on privacy fundamentals. Users choosing ZEC over Bitcoin or Monero specifically seek untraceable transactions. A compromised privacy layer erodes that differentiation. Ironwood's launch becomes a confidence checkpoint for the protocol's technical integrity.

Mandatory upgrades carry coordination risk. Node operators must upgrade by the deadline to maintain consensus