Zcash Schedules July 28 Hard Fork to Seal Orchard Pool
Zcash will execute a hard fork on July 28, called Ironwood, to seal the Orchard shielded pool and contain a potential counterfeit ZEC issue. The fork will use a turnstile mechanism to manage any affected supply.
Key Takeaways
- 1## The Ironwood Hard Fork Zcash developers scheduled a hard fork for July 28 to address a critical issue in the Orchard shielded pool.
- 2The upgrade, named Ironwood, will seal the pool and prevent further activity on it, according to the Zcash team.
- 3## Why Sealing Orchard Matters The Orchard pool was designed as Zcash's next-generation privacy mechanism.
- 4Sealing it reflects the presence of a bug that could lead to counterfeit ZEC entering circulation.
- 5By closing the pool, the network prevents additional coins from being minted through the vulnerability.
The Ironwood Hard Fork
Zcash developers scheduled a hard fork for July 28 to address a critical issue in the Orchard shielded pool. The upgrade, named Ironwood, will seal the pool and prevent further activity on it, according to the Zcash team.
Why Sealing Orchard Matters
The Orchard pool was designed as Zcash's next-generation privacy mechanism. Sealing it reflects the presence of a bug that could lead to counterfeit ZEC entering circulation. By closing the pool, the network prevents additional coins from being minted through the vulnerability.
The Turnstile Mechanism
Zcash will deploy a turnstile—a controlled migration path—to account for any counterfeit ZEC already in the pool. This mechanism ensures that affected funds are tracked and contained rather than left loose in the wider supply, protecting the integrity of the ZEC monetary base.
Why It Matters
For Traders
ZEC holders should ensure clarity on how the turnstile affects their holdings; verify your wallet is compatible with the July 28 fork before that date.
For Investors
A critical bug requiring hard fork consensus signals both responsible disclosure practices and potential supply-side risk that will now be mitigated by the upgrade.
For Builders
The Orchard pool closure may redirect privacy-focused development to alternative shielded pools or require protocol teams to audit similar pool implementations for similar bugs.
