Same process,
use : version: 3.0.2-CYPHERPUNK
released : 2026-07-27
4 Likes
Cake Wallet was ready for the hard-fork, with version 6.4.0 going live this morning on all app stores!
Out now and automatically migrating users through a privacy-preserving path as soon as they open their Zcash wallets.
More info in our docs: Ironwood migration | Crypto | Cake Wallet - Docs
5 Likes
Ironwood is live and working in Cake Wallet with auto-migration. Can be seen in my tweet!
6 Likes
Ironwood is active!!
Important privacy note for all Zcash users:
Not every wallet supports the privacy-optimized Ironwood migration process yet, be careful right now.
The Zodl app does not yet support the safest migration path.
If you send funds in an Ironwood wallet which does not have a migration feature, the funds will send just fine. But, you are broadcasting the amount that you sent between the Orchard and Ironwood pools publicly on the blockchain forever. Sender and recipient remain private, but your amount is public.
Wallets supporting the safest fund migration path take a specific approach to moving your funds between pools. Please wait for Zodl to add support for this if you absolutely need the highest level of privacy.
Cake Wallet and Vizor are two wallets that I have tested that support safer migration, I believe Zkool also supports it but I have not yet tested.
I’m sure Zodl will update here as soon as they release support, they are working tirelessly over there.
8 Likes
Quick Gem Wallet status update:
We successfully completed a transparent ZEC transaction after Ironwood activation. Our public Zcash backend is synchronized past the activation height and reports the Ironwood consensus branch ID (37a5165b).
Public node status: https://gemnodes.com/zcash/api/
{
"blockbook": {
"initialSync": false,
"inSync": true,
"bestHeight": 3428921,
"inSyncMempool": true
},
"backend": {
"chain": "main",
"blocks": 3428921,
"headers": 3428921,
"version": "zebra",
"consensus": {
"chaintip": "37a5165b",
"nextblock": "37a5165b"
}
}
}
Block height shown is a snapshot and will increase over time.
Gem currently supports transparent ZEC only. Shielded transactions and Orchard-to-Ironwood migration are not yet supported.
We are still confirming the exact Zebra build used by our managed node providers, so this update confirms post-activation transparent transaction compatibility rather than a specific Zebra version.
2 Likes
The android appstore version of Zkool is updated, ios still pending.
2 Likes
Zkool migration support added! I have confirmed Orchard to Ironwood txids working.
Click three dots:
Then last option below,
3 Likes
I recommend using Tor (embedded arti or external socks proxy) to hide your IP for the lightwalletd server
3 Likes
Realized I posted on X, but not here.
Vizor supports both the Ironwood pool as well as the Orchard → Ironwood migration. All products provide both the private (ZIP-318) migration path as well as an immediate migration path, but Android currently only has the ‘immediate’ feature and not the private path (hoping to push an update soon, but no specific dates).
Based on our testing, we highly recommend that you use our desktop wallet client.
This is due to the nature of private migrations taking anywhere from 12 hours to many days. Our mobile wallet will provide notifications for when you need to enter the app to continue the migration process, but it’s fundamentally takes more effort compared to the desktop migration, which allows the migration to happen seamlessly in the background as long as the wallet is open and running.
Vizor provides the option to easily export desktop wallets to the mobile wallet, so you can always re-import the accounts after the migration has completed.
3 Likes
July 30 Update: Migration is flowing
Migrated so far: Over 419,293 ZEC
Two days in and the story has shifted from “is your software ready” to “migration works on mainnet.” The top post is updated in this thread. Here’s what changed since the 28th.
Migration confirmed working on mainnet
- @VikCake reports Cake Wallet’s auto-migration is live and working.
- @dismad confirmed Orchard-to-Ironwood transaction ids on Zkool 6.25.1, with screenshots.
- Vizor shipped two iOS updates since launch, now at 0.0.20 (July 30) with migration stability improvements.
For developers
- librustzcash: the wallet crates hit rc.6 on July 30 (
zcash_client_backend0.24.0-rc.6,zcash_client_sqlite0.22.0-rc.6), andzcash_keysis final at 0.16.1. Finals for the wallet crates look close.
Mobile App Releases
- Zkool on Google Play is now current at 6.25.1, which includes migration. The iOS App Store is still on 6.23.0, which cannot migrate. Thanks @Autotunafish for tracking this.
- Zingo! iOS is still on 2.0.20 (309) from June, which predates Ironwood. Android got a 2.0.21 (312) release on July 30.
New on the list
- Gem Wallet: transparent ZEC works past activation with the correct Ironwood branch ID. Shielded transactions and migration are not supported yet.
Server side
- zecd v0.5.0 is final, out of RC as of July 28.
- zallet v0.1.0-beta.2 (July 28) is a substantial release for operators leaving zcashd: a migration guide, an RPC status matrix, operations and backup guides,
z_exportviewingkey, and verification of security-relevant wallet.db records before use. - z:kv v0.0.1-rc5 (July 29).
Other version bumps
- Zingo-PC 2.0.22 (163) (July 30), bug fixes. The private migration path still ships deactivated.
- Zkool 6.25.1 (July 28) restores Ledger build compatibility and moves to production librustzcash; 6.26.0 release candidates are landing.
- NozyWallet 2.4.2 (July 30). The release is explicit that only the CLI is production-ready; desktop, extension, and API companion are still in development. I’ve marked the extension accordingly.
Guidance from the Vizor team
Vizor posted useful operational detail: all Vizor products support Ironwood and migration, and they recommend desktop for private migrations, which run anywhere from 12 hours to multiple days. You can export the wallet to mobile once migration completes. Vizor’s Android app lacks the private path for now, with an update planned.
Zodl published their migration plan
Their support article describes the private flow in development: balances worked into standard sizes like cash note denominations, transfers staggered on randomized schedules, network checks separated from broadcasts, and the full schedule shown up front before you consent. No release date yet, and they’re targeting iOS and Android simultaneously.
I cannot help to think that if the Zodl team believes that all of these migration safeguards are so important, they should be warning their users in their released apps to wait for their safer release. Currently Zodl users are crossing the turnstile without any migration process or privacy enhancements.
My warning at the top of the post stands until it ships: basic fund movement works in 3.8.0 today, but amounts crossing the turnstile are still way more revealing on Zodl. A 3.8.1 Android release is staged in the repo but not yet published.
Cipherscan reports that 82.5% of all Ironwood migrations are failing to follow the ZIP-318 migration standards for privacy over the past 7 days, with over 24% failing to even try.
It’s hard not to blame ZODL for this, I fully expect this to improve once they fix their apps to follow the standard that they helped define.
Anything else that shipped and isn’t on the list, reply here or DM me and I’ll add it.
8 Likes
Is there a way to set the migration amount per transaction in Zkool? Trying to do it per the auto button seems to prefer sub 1 Zec amounts which (in my case) will take a very long time to migrate.
cc @hanh
1 Like
You should be able to just do it manually and have control over your input notes as well.
It is not gonna be all sub ZEC amounts as it is broken into standard denominations of powers of 10, but it can take a long time still. You can always do a orchard to ironwood tx of any amount.
3 Likes
Nozy supports ZIP 318 Orchard to Ironwood migration (CLI/desktop), so users aren’t forced into a naive cross-pool send. We also treat IP submit as part of safer migration prefer a local Zebrad, or opt-in Nym mixnet smolmix for remote sendrawtransaction / migrate-broadcast so the submit host isn’t your clearnet IP. Tor/I2P and an explicit private-network attestation are other accepted paths. Turnstile amounts are still public by design, mixnet doesn’t hide the amount, it breaks the IP link.
3 Likes
August 1 Update
Migrated so far: >702,861 ZEC
The top post is updated in this thread. Here’s what changed since the 30th.
Zingo! iOS shipped
Zingo! iOS updated on July 31 to 2.0.21 (311) on the App Store, with 2.0.22 (313) tagged the same day carrying Ironwood support. Thanks @dismad for confirming with a screenshot.
Update lightwalletd again
v0.5.2 (July 30) is the third security release in a week. It narrows the GetMempoolTx mutex to the cache it protects (GHSA-f9pw-q493-7qvh, GHSA-9p9r-mggr-8q9g). v0.5.1 bounded oversized client input, v0.5.0 was the Ironwood release. If you are on 0.5.0 or 0.5.1, update.
Wallet updates
- Zodl 3.8.1 shipped to both stores on July 30. It fixes balance and transaction display issues. It does not add the private migration flow, so the warning at the top of the post stands.
- Zkool 6.26.0 (July 31) is a substantial migration release: streaming with progress tracking, cancellation support, a one-shot option, and migration transactions labelled in history, plus dust filtering and per-pool note locking.
- Vizor is on Android too, at 0.0.21 on Google Play, though the private ZIP 318 path is iOS and desktop only for now with an Android update planned. iOS is at 0.0.21 as of July 30.
- NozyWallet, per @Lowo is conformant with ZIP 318, across CLI and desktop. I had it listed as a wallet-specific private flow; it aims to be spec-conformant but I have not had time to personally confirm this yet.
Controlling your own migration amounts
Most wallets are allowing manual control of migration amounts, via regular Zcash sends. Manual control is there if you want it. But the defaults exist because a hand-picked amount is exactly the kind of thing that makes your crossing identifiable, so unless you know specifically why you’re overriding, don’t.
Server side
- zecd v0.5.1 (August 1) adds coinbase spending.
- Zakura v1.1.0-rc0 tagged August 1. Latest stable is still v1.0.5.
- zallet unchanged at v0.1.0-beta.2, Zaino at 0.6.0, Zebra at v6.2.3.
For developers
- librustzcash wallet crates remain at rc.6 (
zcash_client_backend0.24.0-rc.6,zcash_client_sqlite0.22.0-rc.6). Everything else in the cohort is final.
Anything else that shipped and isn’t on the list, reply here or DM me and I’ll add it.
Ironward.
10 Likes