Technical Specifications and Changes
Published 6/8/2026, 12:05:19 AM
The Ironwood shielded pool, proposed by the Zcash Open Development Lab (ZODL) in June 2026, is a protocol upgrade designed to restore trustless supply verification following a remediated vulnerability in the Orchard pool [Source: https://www.kucoin.com/news, https://www.binance.com/en/square]. While it maintains the core privacy features of the Orchard protocol, its primary impact is the introduction of a mandatory "Turnstile" migration to ensure the integrity of the Zcash circulating supply.
Technical Specifications and Changes
Ironwood is built upon the existing Orchard protocol (introduced in NU5) but incorporates significantly higher assurance standards to prevent the recurrence of integrity flaws [Source: https://x.com/zcash, https://zcash.foundation/blog/].
- The Turnstile Mechanism: This is the core technical differentiator. Ironwood acts as a "clean" destination for ZEC. The existing Orchard pool will be restricted to "exit-only" mode—disabling new deposits and internal transactions. Funds must pass through a turnstile to enter Ironwood, allowing the network to verify that no more ZEC exits Orchard than was legitimately deposited [Source: https://zcash.foundation/blog/].
- Security Framework: Ironwood utilizes formal verification, independent audits, and AI-assisted security reviews (specifically using Claude Opus 4.6) [Source: https://zcash.foundation/blog/].
- Activation Target: Activation is planned for late July 2026 at block height 3,417,100, coinciding with the end-of-support for the
zcashdnode implementation [Source: https://forum.zcashcommunity.com/]. - Backward Compatibility: Users can retain existing Orchard receiving addresses, with wallets supporting a "one-click" migration to move funds from Orchard to Ironwood [Source: https://zcash.foundation/blog/].
Impact on Zcash Privacy Architecture
The introduction of Ironwood represents a strategic shift in how Zcash balances absolute privacy with economic soundness.
| Feature | Impact of Ironwood |
|---|---|
| Supply Verifiability | Restores the ability for nodes to independently verify the total ZEC supply, which was technically obscured by Orchard's privacy properties [Source: https://news.bitcoin.com/]. |
| Privacy Set | Temporarily fragments the privacy set as users migrate. Until a critical mass moves to Ironwood, its "anonymity set" will be smaller than the mature Sapling or Orchard sets [Source: https://cryptobriefing.com/]. |
| Protocol Hardening | Introduces "checkpointing" and improved exception safety for pool balance arithmetic to prevent undefined behavior from maliciously crafted blocks [Source: https://zcash.foundation/blog/]. |
| Ecosystem Migration | Accelerates the deprecation of zcashd in favor of Zebrad and the new Zallet command-line tool [Source: https://forum.zcashcommunity.com/]. |
Evidence Ledger Resolution
- c1 (Ironwood as an upgrade): RESOLVED. Proposed by ZODL in June 2026 [Source: https://www.kucoin.com/news, https://www.binance.com/en/square].
- c2 (Technical changes): RESOLVED. Introduces the Turnstile mechanism and formal verification [Source: https://zcash.foundation/blog/].
- c3 (Impact on privacy set): RESOLVED. Causes temporary fragmentation of the anonymity set during the migration period [Source: https://cryptobriefing.com/].
Conclusion
The Ironwood upgrade is a "trust-restoration" event. While the Orchard vulnerability (discovered in April 2026) was not exploited [Source: https://forum.zcashcommunity.com/], the nature of zero-knowledge proofs meant users had to trust developers that no inflation occurred. Ironwood replaces this trust with mathematical proof via the turnstile. While privacy remains the core value—with shielded pools surpassing 4.5 million ZEC (approx. 27.5% of supply) in late 2025—Ironwood prioritizes "sound money" to ensure long-term confidence [Source: https://techflowpost.com/].
Next Steps:
- Would you like to monitor the Zcash block height to track the countdown to the Ironwood activation at block 3,417,100?
- I can perform a deep dive into the
Zebradnode implementation to see how it handles the new Ironwood checkpointing.