The Zcash $ZEC network failed to produce a block for more than four hours on June 3, according to InfinityHedge, extending a period of instability that began the previous day when developers
The Zcash $ZEC network failed to produce a block for more than four hours on June 3, according to InfinityHedge, extending a period of instability that began the previous day when developers coordinated an emergency protocol upgrade.
The Zcash Open Development Lab (ZODL) steered a coordinated network upgrade to patch a flaw in Orchard, the chain's newest shielded pool, after flagging the issue during a security review over the weekend. The upgrade activated at mainnet block height 3,363,426 at approximately 02:00 UTC on June 2, and required miners across the network to temporarily stop mining all Orchard-related transactions while the protocol-level fix was rolled out.
The issue was a soundness vulnerability in the Orchard shielded pool. In Zcash, soundness means the protocol should only accept valid transactions and valid state changes. A soundness bug can allow the system to accept something it should reject. In this case, successful exploitation could have allowed invalid state transitions inside Orchard, potentially affecting accounting guarantees for the pool.
The Zcash team said the issue was identified through routine auditing and security reviews before any known exploitation occurred. Transparent and shielded Sapling transactions remained unaffected. The fix proceeded in two stages: the first was a soft fork that temporarily disabled Orchard by blocking the creation of new outputs and the spending of existing funds, while the second was a hard-fork network upgrade that updated the zero-knowledge proof circuit and fully restored Orchard functionality.
One notable aspect of the announcement was Zcash's disclosure that it is notifying maintainers of other protocols that have deployed Orchard, suggesting the issue may extend beyond Zcash's own implementation.
Developers indicated the issue required a protocol-level change rather than a routine software update, meaning validators needed to adopt new consensus rules to address the problem. Unlike contentious blockchain forks that create competing chains, the Zcash ecosystem aligned around a single upgrade path, with validators effectively isolating the affected Orchard subsystem while allowing most network activity to continue uninterrupted.
The disruption arrives during an unusually active patch cycle for the network. A string of emergency patches, including Zebra 4.4.0 in early May, 4.5.0 on May 29, and 4.5.1 immediately after, has raised questions about the structural complexity of maintaining the protocol. The earlier 4.4.0 release fixed five security vulnerabilities, three of them consensus-critical, including a block-discovery halt that could be triggered with just one malicious connection.
Despite the turbulence, markets took the latest disruption in stride. The market interpreted the rapid, transparent response as a sign of robust protocol governance, with $ZEC decoupling from the broader crypto selloff and recording a sharp daily gain while Bitcoin dropped.
SourcesZcash Community Forum: Orchard Vulnerability Successfully RemediatedCrypto Times: Zcash Executes Emergency Fork After Critical Orchard Vulnerability DiscoveryCrypto Adventure: Zcash Restores Orchard After Critical Shielded Pool Vulnerability
