Zcash validators coordinate emergency Orchard fix, avoid full network shutdown

Zcash validators coordinated an emergency protocol upgrade after developers discovered a vulnerability affecting the network's Orchard shielded pool, temporarily suspending Orchard transactions while a fix is rolled out. In an update published on June 2, the Zcash team said the issue was identified through routine auditing and security reviews before any known exploitation occurred. The protocol-level change took effect at approximately 10:30 p.m. Eastern time on June 1. According to the announcement, Orchard-related transactions are currently not being mined as validators implement the coordinated upgrade. Wallet users are temporarily unable to send or receive Orchard funds until the rollout is complete. However, the rest of the Zcash network remains operational. The project expects Orchard transactions to be re-enabled later on June 2, following completion of the upgrade process. While the project has not yet disclosed the technical details of the vulnerability, developers indicated that the issue requires a protocol-level change rather than a routine software update. That distinction suggests validators needed to adopt new consensus rules to address the problem. The coordinated response has led some observers to characterize the upgrade as a hard fork-style intervention. Unlike contentious blockchain forks that produce competing chains, drama, and airdrop hunters, the Zcash ecosystem appears to have aligned around a single upgrade path designed to preserve network integrity while minimizing disruption. Rather than pausing the entire network, validators effectively isolated the affected Orchard subsystem while allowing most Zcash activity to continue uninterrupted — a notably civilized approach by hard fork standards. One of the more notable aspects of the announcement was Zcash's disclosure that it is notifying maintainers of other protocols that have deployed Orchard. The statement suggests the issue may extend beyond Zcash's own implementation and could potentially affect projects that utilize Orchard-related technology. Developers have not yet released full technical details, a common practice during active security upgrades to reduce the risk of exploitation before fixes are broadly deployed. The project said additional information will be shared once the upgrade process is complete.