Coordinated Zcash Network Upgrade Underway


As part of routine auditing and security review processes, an issue affecting the Zcash Orchard pool was identified over the weekend. Orchard-related transactions have been temporarily suspended. Privacy is unaffected. All funds are safe.

To protect Zcash users and the integrity of the network, developers, infrastructure operators, and other independent participants across the Zcash ecosystem have come together to coordinate a protocol update that requires a temporary suspension of Orchard pool activity during the upgrade rollout.

Orchard transactions are expected to be re-enabled at 14:00 EDT on June 2, 2026. We will provide a status update at 10:00 EDT.

Key Facts:

  • The issue does not affect the privacy of any funds.
  • The issue was identified through routine auditing before any known exploitation.
  • The issue affects only Orchard, Zcash’s latest shielded pool.
  • Only Orchard pool transactions will be suspended during the upgrade window. Wallet users will be unable to send or receive Orchard funds until the upgrade is complete.
  • With the exception of the shielded Orchard pool, the Zcash network continues running. Transactions to and from the shielded Sapling and transparent pools are unaffected.
  • ZEC held on exchanges is unaffected and can continue to be traded normally.
  • This issue required a protocol-level change, which took effect at 22:30 EDT on June 1, 2026

This effort relies on voluntary cooperation among independent participants throughout the network. As part of our responsible disclosure, we are also notifying the maintainers of other protocols that have deployed Orchard.

Additional information will be shared when the upgrade is complete.

8 Likes

Are all the vulnerabilities being discovered by AI? How does that impact how protocol changes need to be made going forward?

We can’t say much at this very moment. Zcash core developers make responsible use of AI to enhance protocol development, strengthen our specifications, formalize our code and many other things that make us stronger.

3 Likes

everyone should update their nodes also, right? i don’t see any mention of this.

I’m preparing that part myself.

2 Likes

This information seriously damages the “Unstoppable Money” thesis. Stay strong, everyone.

Hey all,

I upgraded Cipherscan Zebra to v4.5.3 within 30 minutes of the notification and have been monitoring since.

During the soft-fork transition I saw multiple competing forks as miners upgraded. The longest was a 25-block fork (heights 3363431-3363455), plus scattered orphans as stragglers came online. 37 orphaned blocks total.

I cleaned up the database (had 45 stale block hashes from the competing chains), re-indexed from scratch, and everything is back in sync.

Also shipped a fork watch page so people can see what happened: cipherscan.app/reorgs, shows orphaned blocks, fork events, which miners were on the old chain, etc. There’s a public API endpoint too if anyone running nodes wants to report competing tips.

All services running: explorer, API, lightwalletd. Happy to help with anything else.