← All insights
RESEARCHZcash Forum · zooko

Ironwood: proposal to verify the soundness of supply

After the Orchard forgery vulnerability, it introduces the Ironwood proposal, which lets users directly check that the circulating supply is correct by summing the balances of active pools.

Zooko Wilcox, Jason McGee and Taylor Hornby of Shielded Labs, together with the Zcash Foundation, Tachyon Group, Valar Group and ZODL, posted the Ironwood proposal on the forum. Last week a critical forgery vulnerability was found in the Orchard pool, and it was resolved on June 2 by an emergency network upgrade coordinated by ZODL and others. Exploitation is considered unlikely, but because of Orchard's privacy properties users cannot check for themselves. Ironwood is a proposal to restore users' ability to verify the soundness of the circulating supply.

Ironwood creates a new shielded pool with the Orchard circuit that fixes the forgery vulnerability, rejects as invalid any transaction creating new outputs in the old Orchard pool, and raises assurance that no further forgery bugs exist through AI-assisted security audits, formal verification and other means. After activation, Orchard funds can leave the pool only through the turnstile, which tracks each pool's inflows and outflows and rejects transactions that try to take out more than legitimately entered. So the moment it activates, simply summing the balances of the active pools lets anyone verify the circulating supply is correct, without waiting for migration.

Ironwood can also produce evidence on whether the vulnerability was exploited, but achieving the goal does not depend on that evidence. A forger, if there is one, faces a choice at migration: move the counterfeit funds and reveal their existence, or leave them and lose the ability to spend them later. If no excess ZEC attempts to leave, that is strong evidence that there was no exploitation, and if there is an attempt, those funds cannot leave the pool and are effectively destroyed, which is public evidence that forgery occurred. The latter is a result needed to preserve the circulating supply, and they consider it unlikely.

Every wallet that supports Orchard must support the new pool, and until activation it should keep supporting Orchard normally and then move funds to the new pool. Migration reveals the transfer amount and timing, but they see the impact as small and further reducible through wallet behavior. Existing Orchard addresses remain valid. The schedule depends on development, testing and coordination and could be affected by progress on retiring zcashd, so they speak conservatively. They thank Kris Nuttycombe, whose proposal to block output creation in the old pool was the key.

This summary is based on the original; check the original for exact details.