Ironwood quantum recoverability: what ZIP 2005 means

ZECStats tracks NU6.3 activation on July 28, 2026, at block 3,428,143, introducing the Ironwood shielded pool. ZIP 258 specifies that same mainnet activation height, but its document status is Draft. The activation date here comes from the site's tracked deployment record, not from treating a draft specification as deployment confirmation.

ZIP 2005, titled Ironwood Quantum Recoverability, is marked Proposed. It describes changes to the construction of Ironwood notes intended to support a future transition. Its central limitation is explicit: the change does not by itself make Zcash secure against quantum computers.

Sources: ZECStats Ironwood Migration Tracker · ZIP 258: Deployment of the NU6.3 Network Upgrade — Draft · ZIP 2005: Ironwood Quantum Recoverability — Proposed

ZIP 2005 describes a threat to the cryptography used by existing shielded protocols: an adversary able to solve the relevant discrete-logarithm problems could steal or forge funds. Quantum recoverability addresses how legitimate funds could be recovered if those protocols had to be disabled to prevent such attacks.

The proposal changes how notes are constructed for Ironwood so that a potential future Recovery Protocol could recover their funds into another shielded pool. That Recovery Protocol is outlined, not fully specified; many design decisions remain open. Preparing notes for recovery is therefore different from having a completed quantum-secure protocol available today.

The distinction matters because replacing the proof system alone would not solve every problem. ZIP 2005 explains that existing Sapling and Orchard note commitments are not post-quantum binding: a sufficiently capable adversary could forge spendable notes. The proposed note changes prepare for that problem before a later transition.

Sources: ZIP 2005: Ironwood Quantum Recoverability — Proposed

Under the scenario described in ZIP 2005, funds still in Sprout, Sapling or Orchard would not be recoverable after their respective protocols were disabled. This is a conditional statement about a future security transition, not a claim that those funds are already inaccessible.

The proposal says those funds should be migrated to Ironwood to take advantage of the recoverability changes. Moving value to Ironwood and recovering it through a future Recovery Protocol are separate steps: the first prepares funds for the second. This explanation does not establish a migration deadline or wallet-specific procedure.

Sources: ZIP 2005: Ironwood Quantum Recoverability — Proposed

Recoverability concerns whether funds could survive a future cryptographic transition. Transaction privacy concerns what a transaction reveals. The word recoverable does not mean that balances identify their owners, nor does it justify describing every Ironwood transaction as quantum-proof.

ZIP 2005 discusses privacy under specific adversary assumptions, including whether an adversary knows a note's address. Those qualifications should not be replaced with an unconditional quantum-privacy claim. For migration itself, the ZECStats tracker separately explains that amounts crossing the Orchard-to-Ironwood boundary are public. That boundary disclosure and future fund recoverability answer different questions.

Use the Ironwood migration tracker for migration progress and the Orchard pool page for the remaining balance. Those live quantities describe value in and between pools; they do not demonstrate that a future Recovery Protocol is complete.

Sources: ZIP 2005: Ironwood Quantum Recoverability — Proposed · ZECStats Ironwood Migration Tracker

• ironwood
• orchard pool

All ZecStats insights