Zcash Activates Ironwood: How the Network Closed the Door on Fake ZEC

On July 28, the Zcash network activated the Ironwood upgrade and replaced the Orchard shielded pool, where a counterfeiting flaw was found back in May. Developers say it is now mathematically impossible to withdraw more ZEC from the network than was actually deposited. For a coin whose main value proposition is transaction privacy, the mere possibility of quietly printing extra coins amounted to an existential threat.

What the Network Activated on July 28

NU6.3, code-named Ironwood, replaced Orchard, the shielded pool that hides amounts and addresses in ZEC transactions. It held roughly 3.7 million coins, worth around $1.7 billion at current prices. The old pool stays on the network, but only for withdrawals. Closing a position in Orchard is still possible, opening a new one is not.

Zcash's shielded pools have changed before. The network launched in 2016 with the Sprout scheme, moved to Sapling in 2018, then introduced Orchard in 2022 alongside a new proving system called Halo 2. Each transition required migrating funds between pools, and Ironwood continues that pattern for the fourth time.

Two organizations share responsibility for the work: the nonprofit Zcash Foundation and Electric Coin Company, which created the protocol back in 2016. Project Tachyon, the team that wrote Ironwood's code directly, operates under their umbrella. The community had been discussing the switch since early July, when it was unclear whether exchanges and wallets would be ready in time, and the upgrade ended up going live right on schedule.

What Was the Threat to Private ZEC?

In May, security researcher Taylor Hornby found a four-year-old bug in the Orchard code. In theory, it could have let someone mint ZEC out of thin air. Because shielded transactions hide their details by design, there was no way to check whether anyone had actually exploited it.

Hornby reported the flaw privately, through standard responsible disclosure, giving development teams time to prepare a fix before any public details came out. That explains why nearly three months passed between the bug's discovery in May and a full technical solution.

The coin's price dropped 38% within days of the disclosure, even though ZEC had posted one of the best returns among leading cryptocurrencies earlier in the year. Zcash developers and the Project Tachyon team immediately started building Ironwood, and by June the price had clawed back roughly half the losses, adding about $2.5 billion in market cap purely on expectations of a fix.

How Does the Turnstile Stop Fake Coins From Appearing?

At the core of Ironwood sits a mechanism developers call the turnstile. It tracks the balance across the entire network and will not let a single coin leave the pool beyond the amount that was verifiably deposited into it.

In earlier versions of Zcash, balance checks lived only inside each individual zero-knowledge proof, and that is exactly where a missed edge case could hide. The turnstile adds another layer, namely network-wide accounting that does not depend on any single proof being correct. It works like a bank's dual-control system, where one check catches algorithm errors and another watches the actual money moving in and out.

Even if another bug were hiding somewhere in the code, it would not be enough to counterfeit ZEC. The network-wide accounting simply will not let a fake coin pass through the turnstile.

• Balance accounting: the network checks the amount entering and leaving the pool at every block.
• New coins cannot appear without a matching deposit in the old or new pool.
• Wallets migrate from Orchard to Ironwood gradually, with no forced deadline for users.
• The public part of a transaction stays open to audit, while the private part is protected by a zero-knowledge proof.
• Block explorers now show old-pool and new-pool balances separately, making the migration easier to audit.

Why Do 2,700 Mathematical Proofs Matter?

Project Tachyon brought in three research teams. Over a month of work, they wrote more than 2,700 machine-checked theorems in the Lean language, a tool previously used mostly by mathematicians to prove theorems rather than by cryptocurrency developers.

That amounts to formal proof that Ironwood's code does exactly what its specification says, nothing more and nothing less. This level of scrutiny is standard in aviation or nuclear engineering, but verifying an entire pool down to 2,700 theorems set a new bar for the crypto industry. Other zero-knowledge projects have started publishing similar independent proofs, though none has released a theorem set this large yet.

The team behind the proof stresses that it covers balance integrity, not the privacy of the transactions themselves. Those are two separate things, and the second one still cannot be formally verified.

What Should ZEC Holders Do Now?

Moving into the new pool has a side effect. While a wallet transfers funds from Orchard to Ironwood, some metadata, such as an IP address or an approximate balance, may become visible to outside observers. Developers recommend using Tor or a VPN during the migration if privacy matters to you.

Exchanges such as Binance are also rolling out their own Ironwood support, so moving ZEC onto an exchange hot wallet during the migration is worth delaying by a few days until the network settles down. Fully migrating all funds from Orchard to Ironwood will take several months by the team's own estimate, since some wallets have not yet added support for the new pool.

For large holdings, it is worth keeping keys in a hardware wallet such as Ledger and splitting the transfer into smaller batches. Bitcoin runs on a transparent ledger where every transaction is visible right away. Zcash was built on the opposite premise, confidentiality by default, and any change to that protocol touches the exact feature people buy the coin for. In the first few hours after activation, ZEC's price barely moved, which traders took as a sign of confidence in the new code.