Zcash Activates Ironwood Upgrade on Mainnet, Restricts Orchard Pool and Introduces New Privacy Pool
Zcash Open Development Lab announced the activation of the Ironwood (NU6.3) network upgrade on the mainnet at block height 3,428,143, introducing a new privacy pool to enhance network security and allow independent verification of circulating supply integrity. With the launch of Ironwood, the original Orchard privacy pool is locked, and funds must be transferred out of Orchard through a "turnstile mechanism" before entering the new Ironwood pool.
The Ironwood upgrade was initiated in response to a critical "forgery/inflation risk" vulnerability discovered in the Orchard privacy pool at the end of May. This vulnerability has been addressed in previous emergency soft forks and the NU6.2 hard fork. Currently, there is no evidence that the vulnerability was exploited on the mainnet, nor is there data indicating that user funds or the total supply of ZEC were affected. Ironwood builds on the corrected Orchard protocol, introducing formal verification and independent security audits to strengthen the protocol's defense against future supply integrity vulnerabilities.
At the market mechanism level, funds in the Orchard pool need to be migrated to the new privacy pool supported by Ironwood. Mainstream clients will provide users with a one-click migration path, eliminating the need to change addresses or create new wallets. After the upgrade, the old pool will no longer accept new payments and will only allow funds to flow out unidirectionally through the "turnstile". Nodes and users can independently verify whether the ZEC supply is consistent, which will reduce the impact on ZEC prices and long-term credibility in case of misuse of the privacy pool or undetectable inflation risks.
Source: Public Information
ABAB AI Insight
Historically, Zcash has balanced privacy and verifiability: early upgrades from Sprout, Sapling to Orchard enhanced privacy and performance through zero-knowledge circuits. The design of Ironwood continues this rapid response path after the Orchard vulnerability was exposed, which could allow "infinite forged ZEC" to be minted within the privacy pool. It involves discovering the vulnerability, executing an emergency soft fork to freeze related transactions, and a hard fork to repair the circuit, followed by restoring confidence that "any user can check the total supply" through the new privacy pool and formal verification. This practice reflects the Zcash community's tradition of using chain-level governance to correct issues with privacy protocols during multiple parameter upgrades and circuit iterations.
From a capital perspective, this upgrade essentially restructures the "privacy asset pool" from a single Orchard to a new Ironwood pool with a turnstile and independent accounting: funds can only flow unidirectionally from the old pool to the new pool, and all cross-pool movements must undergo supply integrity checks. This means that any future teams wishing to build privacy financial applications on Zcash (including OTC, on-chain lending, or payment solutions) must accept the constraint that "privacy transactions are in the pool, but supply audits are off-chain or between pools". For long-term capital holders of ZEC, Ironwood effectively offers a structure of "sacrificing part of privacy for measurable supply risk", allowing institutions to hold, market-make, or design structured products with more confidence, rather than worrying about undisclosed inflation hidden in a privacy pool.
In comparison to other cases, Monero has chosen to continuously change privacy parameters and obfuscation strategies in response to pressure from ring signature and stealth address analysis, without introducing similar supply gates. Ethereum, after regulatory pressure on Tornado Cash, has relied more on front-end restrictions and compliance screening at the ecological level, rather than adding verifiable privacy pool mechanisms at the protocol level. Zcash, through Ironwood, transforms the risk of zero-knowledge circuit errors on supply integrity into a variable that can be managed through the "new pool + turnstile" structure, gradually shifting from "extreme privacy" to "auditable privacy" in the privacy coin track, moving from a phase of functional innovation during expansion to a phase of control and repositioning for long-term survival.
Structurally, Ironwood is closer to "industry chain reconstruction + regulatory expectations in advance": privacy protocols were once seen as difficult to regulate and audit. The Orchard vulnerability incident exposed not just a technical bug, but also the fact that if supply cannot be independently verified, privacy assets lose their qualification as "measurable collateral or store of value". Through the new pool and turnstile mechanism, Zcash reconstructs its originally purely technical privacy design into a link of "privacy transaction layer → turnstile cross-pool layer → network-wide supply verification layer", allowing potential regulators or institutional auditors to check system-level supply without compromising individual privacy. This structure reserves space for privacy coins on the path to compliance and institutionalization, and partially shifts pricing power from pure speculative liquidity to dimensions of "technical audit + supply transparency".
ABAB News · Cognitive Laws
Absolute privacy is a myth; auditable privacy is the asset.
Security vulnerabilities do not destroy projects; unquantifiable risks do.
True defense is not encryption, but making errors visible.