Zcash hard forks to retire a broken privacy pool with the Ironwood upgrade

Zcash is pulling off one of the hardest maneuvers in crypto: a scheduled hard fork to retire a broken privacy pool.

What happens at block 3,428,143

On July 28, around 13:00 UTC at block 3,428,143, Zcash activates the Ironwood upgrade, also known as NU6.3. The fork does two things at once:

• It retires the current Orchard shielded pool, after a critical bug was found in its circuit
• It introduces a new shielded pool built on the corrected circuit, delivered through a new v6 transaction format

The Zcash Foundation’s Zebra 6.0.0 node shipped ready for the switch, so the infrastructure side is prepared ahead of activation.

Why this is hard

Privacy pools are the core of what Zcash is. A critical bug in the shielded circuit is close to the worst-case scenario for a privacy coin, and the response options are all painful. Quietly patching is not enough when the flaw sits in the cryptographic circuit itself; the pool has to be replaced.

Doing that through a scheduled, coordinated hard fork, with a new transaction format and node software shipped in advance, is the orderly version of a very messy problem. Every wallet, exchange and service that touches shielded Zcash has to move to the new format, and the network has to agree on the switch at a single block height.

A heavy week for crypto

The upgrade lands in a loaded stretch for the market: the Fed’s rate decision and earnings from Coinbase and Strategy are due in the same window. A protocol-level surgery on a major privacy coin will compete for attention with macro headlines.

Privacy coins rarely get second chances. Whether Ironwood activates cleanly, and whether users migrate to the corrected pool without incident, will decide if this fork is remembered as a crisis handled well or the start of a longer trust problem.