TURNSTILECheck my walletCheckThis board tracks public statements about the Ironwood upgrade — not our guesses about them. A row says ready only when someone has published something we can link to.
No wallet or exchange has publicly declared itself ready. Every confirmed-ready row below is infrastructure — a node or an indexer, not something you hold funds in.
15 of 25 have said nothing we could find. That is not a criticism and not a warning — it means we do not know, and we would rather say so than colour a square green. Ask them, and send us the answer.
Held to the same standard as every other row. Scanning runs on zingolib, whose current pin of zcash_protocol (0.9.0) predates NU6.3; the newest zcash_protocol release ships the Ironwood consensus rules and zingolib is integrating them. Everything here is verified against mainnet pre-activation; post-activation scanning depends on that upstream work landing.
zcashd will not support NU6.3 and halts itself at block 3,417,100 (est. 18 July), about 11,000 blocks before Orchard stops taking deposits. A node that will not start cannot move your funds — migrate to Zebra or Zallet before then.
Zebra v6.0.0 is the first stable release that activates Ironwood on mainnet at block 3,428,143. All node operators must upgrade before activation.
Zaino 0.6.0 adds full support for Ironwood, including the v6 transaction format and the Orchard-to-Ironwood pool transition, with an automatic database migration.
The latest upstream release (v0.4.19, 30 March) predates Ironwood, and the only Ironwood work is an unmerged draft pull request opened on 12 July. Most light wallets read the chain through lightwalletd.
Ironwood is live on testnet.zec.rocks via a patched lightwalletd branch. No public statement exists yet about mainnet Ironwood support.
Zallet v0.1.0-beta.1 ships Ironwood wallet support, but it is still a beta and the Orchard-to-Ironwood migration tool is an open issue. It cannot export a unified full viewing key, so Turnstile cannot check a Zallet wallet — read your balance in the wallet instead.
Zodl (Zashi's publisher) states it is updating the wallet and SDKs to support Ironwood, and migration screens exist in its repositories, but the latest shipped release does not mention Ironwood. Zashi shields to Orchard by default, so Zashi balances are the most likely to be affected.
Ironwood support is tracked in an open issue filed on 30 June. No shipped Zingo release mentions Ironwood. Zingo PC exports a unified full viewing key and its birthday, so Turnstile can check it.
Nighthawk's own App Store listing says it no longer supports outgoing ZEC transactions and tells users to import their seed into another wallet. It never shipped NU6.2, let alone Ironwood.
No public statement about Ironwood. The latest release (June) predates the upgrade. It does export a unified viewing key, so Turnstile can check it — the key carries Sapling and Orchard but no transparent component.
Edge holds shielded ZEC, but we found no public statement from Edge about Ironwood or the Orchard closure.
Unstoppable advertises shielded ZEC support, but we found no public statement from it about Ironwood or the Orchard closure.
No public statement about Ironwood. Ledger Live handles transparent ZEC addresses only, so funds held through Ledger Live are not in the Orchard pool.
No public statement about Ironwood. Trezor supports transparent t-addresses only, so no Trezor-held funds sit in the Orchard pool.
Gemini routes ZEC withdrawals directly to Orchard and is the only exchange known to offer shielded withdrawals at all, but it has published nothing about Ironwood. That withdrawal path has to change by activation and Gemini has not said how.
No public statement about Ironwood. Coinbase withdraws ZEC to transparent addresses only.
No public statement about Ironwood or the Orchard closure.
No public statement about Ironwood. Binance's published ZEC network-upgrade notices all predate this upgrade.
No public statement about Ironwood or the Orchard closure.
No public statement about Ironwood. KuCoin has published explanatory commentary on the upgrade but made no operational commitment.
No public statement about Ironwood or the Orchard closure.
No public statement about Ironwood or the Orchard closure.
No major Zcash explorer has published anything about Ironwood. mainnet.zcashexplorer.app still shows an Orchard pool balance with no upgrade notice.
No 2026 Flexa post mentions Zcash, ZEC or Ironwood. Its only Zcash post is the 2024 Zashi integration.
Last reviewed 2026-07-15. Every row carries the source we read and the date we read it. If a status is wrong or out of date, open a pull request againstcontent/readiness.json— no code required.