Orchard to Ironwood: how to migrate your shielded ZEC
Only self-custody holders with funds in the old Orchard pool need to act: update an Ironwood-ready wallet and follow its migration prompt. There is no deadline, your u1 address stays the same, and each transfer pays a normal network fee, but amounts passing through the turnstile are public.
Quick steps
- Check your pools. Open your wallet and see whether any balance is in Orchard. Sapling, transparent and exchange balances need no migration.
- Update your wallet. Install the latest Ironwood-ready version, for example Zodl 3.9.0 or later or Cake Wallet 6.4.1 or later.
- Turn on Tor. Enable Tor or use a trusted VPN so your IP address is not linked to the public migration amounts.
- Start the private migration. In Zodl tap Migrate, choose Migrate with privacy and Start migration. In Cake, keep the app open and synced.
- Keep the app available. On iOS keep the app open; on Android allow background activity. Track progress on the main screen.
- Check the result. Confirm the Orchard balance is zero or near zero and decide whether to sweep or lock any remainder.
On 28 July 2026 the Zcash network activated NU6.3 at block 3,428,143 and opened a new shielded pool, Ironwood. The old Orchard pool became withdraw-only (The Block, 28 Jul 2026). If you hold shielded ZEC from before that date, this guide tells you whether you need to do anything and how to do it without giving away more than necessary.
Why the migration exists
On 29 May 2026 a researcher found an under-constrained check in the Orchard circuit that in theory allowed counterfeit ZEC. An emergency soft fork halted Orchard in early June, a hard fork (NU6.2) fixed the circuit on 3 June 2026, and no evidence of exploitation was found (Decrypt, June 2026). To prove total supply was never inflated, developers moved new shielded activity to Ironwood and put a turnstile on Orchard: the pool can never release more ZEC than entered it, and nodes reject any transaction that breaks this rule. Any counterfeit coins would be stranded. Details: the Orchard vulnerability and what Ironwood is.
Do you need to act?
| Where your ZEC is | Action needed? |
|---|---|
| Orchard balance in a self-custody wallet (most shielded ZEC received before 28 July 2026 in Zashi/Zodl, Zingo!, YWallet and similar) | Yes. Migrate to Ironwood with an updated wallet. |
| Sapling (zs1) shielded funds | No. Sapling still works. Some wallets, such as Cake, auto-shield it into Ironwood anyway. |
| Transparent (t1/t3) funds | No migration. Shielding them sends them straight to Ironwood. |
| On an exchange or custodian | No. Your balance is a record in the exchange's books; the provider handles its own wallets (KuCoin, 2 Aug 2026). Check that your exchange's withdrawals reach Ironwood before you withdraw to a shielded address. |
| In a hardware wallet | Depends on firmware and companion app. Keystone works through Zodl; see below. |
| Sprout (zc) funds | Not part of this migration, but urgent: NU7 (planned around 5 November 2026) is reported to make Sprout funds unspendable. |
Not sure which pool your funds are in? In Zodl, tap your balance on the main screen to see a breakdown by pool.
What happens to your u1 address
Nothing changes. Ironwood uses the same receiver structure as Orchard, so existing unified addresses keep working and wallets route new funds sent to them into Ironwood (Zodl, 28 Jul 2026). You do not need a new wallet or a new seed. Cake Wallet's receive screen simply changed its label from "Default (Orchard)" to "Default (Ironwood)". Addresses you shared before July 2026 can still receive.
Is there a deadline?
No. The protocol sets no fixed deadline, and Orchard funds do not expire (KuCoin, 2 Aug 2026; Zodl support). Zodl expects the migration never to reach 100%, because some coins sit behind lost keys. By 10 September 2026 about 88% of the Orchard balance had moved (KuCoin, Sep 2026).
Waiting has costs, though. Many wallets treat unmigrated Orchard funds as not yet spendable, and you stay dependent on wallet developers continuing to support a retired pool. None of the NU7 coverage we reviewed mentions a change to Orchard withdrawals; the pool NU7 does affect is Sprout. That could change, so migrating when your wallet prompts you is the safer choice.
Which wallets migrate automatically?
| Wallet | How it migrates (October 2026) |
|---|---|
| Zodl | Guided: you start it once. Choose private (several smaller, spaced transfers), immediate (one transfer) or manual. Needs version 3.9.0 for the tools; versions before 3.8.0 no longer sync. |
| Cake Wallet | Fully automatic since 6.4.0; no button and no way to turn it off. Runs only while the app is open and synced, about one transaction per block. |
| Keystone | Through Zodl 3.9.0 or later with Keystone firmware 3.0.2 or later. You sign each batch by QR. |
| Zingo!, Zkool, Edge, Unstoppable | Listed as Ironwood-ready by ZecHub. We could not confirm whether each migrates automatically; update and follow the app's own notice, or send to your own shielded address. |
| Ledger | Ledger Wallet Desktop added native shielded ZEC with Ironwood on 23 Sep 2026; mobile was "coming soon". Ledger's announcement does not describe Orchard migration, so check its help pages. |
| YWallet | Retired and not Ironwood-ready. Restore your seed in Zkool and migrate there: see YWallet to Zkool. |
| zcashd | End of life (18 July 2026) and no Ironwood support. Move to Zallet (beta) with a Zebra node, or import the seed into an Ironwood-ready wallet. See Zallet. |
Migrating in Zodl, step by step
- Update to the latest Zodl from the official app store, GitHub or F-Droid.
- When the prompt appears, tap Migrate. If you dismiss it, it returns next time you open the app.
- Choose Migrate with privacy (recommended). The alternative moves everything in one transaction and shows your full balance on-chain.
- Turn on Tor when asked. Zodl strongly recommends it; without it the server sees your IP address next to the public amounts.
- Android: allow background activity and notifications. iOS: keep Zodl open and active; if it closes, a notification tells you when the next transfer is ready.
- Review the transfer plan and timing, tap Start migration and authenticate.
- Zodl first sends a transaction to yourself that splits your balance into standard pieces, then sends them over time. A widget on the main screen shows progress; tap More for each transfer.
- When finished, a small Orchard remainder may be left because amounts are standardised. You can sweep it (the odd amount may be identifiable) or lock it in the app to avoid spending it by accident. The lock does not carry over to another device.
Smaller balances can finish in a couple of hours; larger ones are spread out on purpose (Zodl support, checked October 2026). If a transfer shows "delayed", tap Send now or let Zodl retry. If one "couldn't be sent", reopen the app and follow the prompt to rebuild the plan.
Keystone users follow the same flow, then scan a QR code with the Keystone, approve on the device and tap Get Signature in Zodl for each batch.
Migrating in Cake Wallet
Open your Zcash wallet, let it sync fully and keep the app open. Cake splits the Orchard balance into round amounts such as 10, 1 and 0.1 ZEC and sends each to yourself as a "Migration" transaction. A "migrating to Ironwood" row under your balance disappears when it is done. Closing the app pauses migration; it resumes where it stopped (Cake Wallet docs).
What it costs
Each transfer pays an ordinary Zcash network fee under ZIP-317 (minimum 0.0001 ZEC). Cake estimates about 0.0002 ZEC per migrated amount. A private, multi-step migration costs more in total than one immediate transfer, which matters most for small balances. No wallet we checked charges a separate migration fee. Estimate it with the fee calculator.
Privacy: what the turnstile reveals
When ZEC crosses from Orchard to Ironwood, the amount becomes public. Sender and receiver stay shielded. A single transfer of an unusual amount, for example one matching an exchange withdrawal, can be linked to you.
- Prefer your wallet's privacy option, which uses standard amounts and spacing shared by many users.
- If migrating manually, use round amounts, spread transfers over days, and in Zodl make each one larger than your current Ironwood balance, because Zodl spends Ironwood funds first.
- Use Tor or a trusted VPN so your IP address is not linked to the amounts.
Migration scams
No one needs your seed to migrate. Ignore messages, memos or websites offering to "migrate your ZEC for you", "claim Ironwood tokens" or "verify your wallet". Migration happens inside your own wallet app. See Zcash scams.
After migrating: get ready for NU7
The next upgrade, NU7, is planned for block 3,543,405, around 5 November 2026 (height agreed 21 Oct 2026, Cointelegraph). It brings 25-second blocks and disables v4 transactions. As of 24 October 2026 it had not activated and a delay was possible. Keep your wallet updated before then.
Frequently asked questions
Is there a deadline to migrate from Orchard to Ironwood?
No. The protocol sets no fixed deadline and Orchard funds do not expire. Migrating when your wallet prompts you is still recommended, so your funds sit in the supported pool.
Will my Zcash u1 address change?
No. Ironwood uses the same receiver structure as Orchard, so existing unified addresses keep working and new shielded funds sent to them arrive in Ironwood.
Do I need to migrate ZEC held on an exchange?
No. An exchange balance is the exchange's record. It handles its own wallets. Check its withdrawal support before sending to a shielded address.
How much does the migration cost?
Each transfer pays a normal network fee, at least 0.0001 ZEC under ZIP-317. Cake estimates about 0.0002 ZEC per migrated amount. Private multi-step migration costs a little more in total.
Is migration private?
Sender and receiver stay shielded, but the amount crossing the turnstile is public. Use your wallet's private option with standard amounts and Tor to reduce linkability.