On 28 July 2026, the Zcash network activated Ironwood (NU6.3), a mandatory upgrade that replaced the Orchard shielded pool following a critical security flaw discovered in May 2026. For users holding ZEC in shielded addresses, this transition was not optional. Wallets that did not upgrade automatically stopped processing new transactions, leaving funds temporarily inaccessible until migration to an Ironwood-compatible wallet was completed. Understanding what changed and why is essential to moving funds safely without exposing your transaction history.
The practical question facing non-technical users is straightforward: how do I transfer my ZEC from an older wallet to one that supports Ironwood without losing the privacy protections that made Zcash valuable in the first place? The answer requires clarity on three points: what Ironwood replaces, which wallets are compatible, and the exact steps to follow. This guide breaks down the migration process without assuming technical knowledge, and covers the key wallet options available for a ZEC wallet download in 2026.

Why Ironwood replaces Orchard and what you need to know
Zcash uses two types of transactions: transparent (public) and shielded (private). Transparent transactions record sender, recipient, and amount on the public blockchain, visible to anyone. Shielded transactions hide these details using zero-knowledge proofs, a cryptographic method that proves a transaction is valid without revealing its contents. The Orchard shielded pool was the most recent shielded design, deployed in 2022 to replace the older Sapling pool. In May 2026, researchers at the Electric Coin Company discovered a security flaw in Orchard’s implementation that, under specific conditions, could have allowed an attacker to forge shielded transactions. The flaw did not immediately compromise existing funds, but it posed an unacceptable risk to the network’s long-term integrity.
Ironwood (NU6.3) was developed as an urgent replacement. Rather than patching Orchard, the Zcash core team chose to retire the entire pool and introduce a new shielded design with improved security architecture. This is a rare event in blockchain history: a complete consensus-layer replacement of a privacy mechanism across an entire network. The upgrade was mandatory, meaning all nodes and wallets had to update by the activation date. Wallets running Orchard code could not validate Ironwood transactions, so they became non-functional after July 28, 2026.
For users, the key implication is that Orchard-only wallets are now obsolete. If your wallet has not been updated by its developer, or if your wallet project is no longer maintained, your ZEC is trapped until you move it to an Ironwood-compatible wallet. This is not a scam or a loss of funds—the blockchain still holds your balance securely—but access requires migration. The sooner you migrate, the lower the risk that you forget your recovery phrase, lose your device, or encounter other complications. Waiting months or years introduces unnecessary operational risk.
Crucially, the migration process preserves privacy. Moving funds from an Orchard shielded address to an Ironwood shielded address does not expose your transaction history to observers. The details of the move are cryptographically hidden from the public blockchain, just as they were under Orchard. The step-by-step process is straightforward enough for non-technical users to follow without specialized knowledge.
Understanding unified addresses and the new u1 format
Ironwood introduces unified addresses, abbreviated as u1. A unified address is a single address string that can receive both transparent and shielded transactions simultaneously. Before Ironwood, Zcash addresses were split into three categories: transparent (starting with t), Sapling shielded (starting with z), and Orchard shielded (also starting with z but with a different internal structure). This fragmentation was cumbersome. A wallet had to display and manage multiple addresses, and users had to know which type of address to give to a counterparty depending on the privacy level they wanted.
Unified addresses consolidate this. A single u1 address can receive transparent payments, Sapling payments, and Ironwood payments. The blockchain recognizes which pool the sender uses, so the receiver’s choice is simplified: just share one address. This also reduces address reuse confusion. In Zcash, address reuse creates a stronger link between multiple transactions using the same address, which can help an observer infer payment patterns even in shielded transactions. By encouraging users to use new addresses through a cleaner interface, unified addresses encourage better privacy hygiene.
When you migrate to an Ironwood wallet, your new wallet will generate unified addresses by default. Your recovery phrase (also called a seed or mnemonic) remains the same cryptographic basis—the wallet derives multiple addresses from one secret—but the format and the way the wallet presents it changes. This is normal and expected. Your old Orchard address still exists on the blockchain and still holds your funds until you explicitly move them, but the new wallet will show you new unified addresses that you use going forward.
Importantly, migrating to a u1 address does not expose your old transaction history. The blockchain record of your previous shielded transactions remains private. When you send funds from an old Orchard address to a new Ironwood address within the same wallet, that movement is itself a shielded transaction, visible only as a confirmed movement of ZEC without revealing source, destination, or amount to external observers. This is a critical privacy guarantee: migration and privacy are compatible.
Step-by-step migration guide for non-technical users
The migration process has five stages: preparation, wallet selection, installation, fund transfer, and verification. Each stage is designed to be reversible, so if you make a mistake early on, you have the chance to correct it without losing money.
Stage 1: Preparation. Before you touch your wallet, write down your current recovery phrase in a safe place if you have not already done so. Your recovery phrase is the master secret that controls your ZEC; without it, you cannot recover your funds if your device is lost or broken. Store it offline—on paper in a secure location, not in cloud storage or on a screen. Do not send it to anyone, and do not type it into any website or application. If you have already written it down, confirm that your written copy is accurate by comparing it word-by-word to what your current wallet displays. This takes five minutes and prevents catastrophe.
Stage 2: Wallet selection. Choose an Ironwood-compatible wallet. The most widely used options as of 2026 are Zodl (formerly Zashi), Zingo!, Zkool (the successor to YWallet), Edge Wallet, and hardware wallet integrations like Keystone, Ledger, and Trezor. Each has different user experience designs and security models. Zodl is optimized for simplicity on mobile; Zingo! is a desktop-first application with strong privacy defaults; Zkool emphasizes speed and low fees; Edge Wallet integrates multiple cryptocurrencies in one application; hardware wallets offer the highest security for large balances at the cost of slower transaction confirmation. For most users migrating a modest ZEC balance, Zodl or Zingo! are good starting points. For balances above $10,000 equivalent, a hardware wallet is worth considering.
Stage 3: Installation and recovery. Download your chosen wallet from its official source. For Zodl, verify the download URL with official Zcash communication channels. When you open the wallet for the first time, it will ask whether you want to create a new wallet or recover an existing one. Select “recover existing wallet” (or the equivalent option in your chosen wallet). You will then be prompted to enter your recovery phrase. Type or paste it carefully, word-by-word, in the exact order it appears in your written copy. Most wallets will display the recognized words as you type, reducing typos. Do not use auto-correct or paste from a photo. Once you enter all words, the wallet will derive your addresses and scan the blockchain for any ZEC associated with your recovery phrase. This scan may take a few minutes as the wallet downloads transaction history.
Stage 4: Verification before transfer. Once the wallet has recovered your balance, confirm three things. First, check that your wallet shows the correct total ZEC amount. If the amount is lower than expected, stop and investigate before proceeding. Second, ensure your wallet displays at least one unified address (u1 format). Third, make a test transaction by sending a small amount (0.01 ZEC or less) from your recovered wallet to another address you control, such as an exchange wallet or a friend’s address. Wait for this test transaction to confirm—it may take 10-30 seconds—and verify that it arrived. This test serves two purposes: it confirms your wallet can send transactions properly, and it proves your recovery phrase works as expected before you move all your funds.
Stage 5: Full migration transfer. Once your test transaction confirms, you can safely move all remaining ZEC. Check the current network fee by reviewing ZIP-317 fee standards, which specify that normal payments incur 0.0001 ZEC per transaction. Open your new Ironwood wallet, generate a receiving address (it will be a u1 address), and copy it. Return to your old wallet, select “send,” paste the u1 address, enter the amount, and approve the transaction. The blockchain will process the transfer, and within 10-30 seconds, your new wallet should show the updated balance. Leave your old wallet intact until you have confirmed the new wallet shows the full balance; only then should you consider the old wallet decommissioned.
Wallet-by-wallet migration notes
Different wallets have slightly different interfaces, and understanding these differences prevents confusion. zec wallet download, verify the URL with the wallet’s GitHub repository or official website before installing. Zodl, formerly known as Zashi, is maintained by Zcash developers and is the most straightforward for non-technical users. Its interface is intentionally simple: create a wallet or recover one, send or receive, view balance. Migration with Zodl involves opening the app, choosing “restore,” entering your recovery phrase, and waiting for synchronization. Zingo! is a more advanced application with additional privacy controls, such as the ability to view and manage Sapling addresses alongside Ironwood addresses. Zkool (the successor to YWallet) offers rapid blockchain synchronization and low fees, though its interface assumes more technical familiarity.
Edge Wallet is a multi-cryptocurrency wallet that includes ZEC alongside Bitcoin, Ethereum, and other assets. Its advantage is portfolio consolidation; its disadvantage is that ZEC features are sometimes secondary to other coins. Hardware wallets like Ledger, Trezor, and Keystone offer maximum security by keeping your recovery phrase completely offline. When using a hardware wallet, the wallet device itself never connects to the internet; instead, your computer or phone connects to a software companion (like Ledger Live or the Trezor Suite), which handles blockchain communication on behalf of the device. Migration with a hardware wallet is slightly more complex because you must approve each transaction on the device’s screen, but the security benefit is substantial for users with significant ZEC holdings.
Regardless of which wallet you choose, the underlying process is the same: recover your recovery phrase, confirm balance and address format, test with a small amount, and then move all funds. The differences are cosmetic. Choose whichever wallet’s interface you find clearest, and do not let the variety of options paralyze you. All Ironwood-compatible wallets follow the same protocol and have access to the same funds. The choice between Zodl, Zingo!, and Zkool is roughly equivalent to choosing between different web browsers—they all browse the same internet, but their designs and speeds differ slightly.
Privacy, traceability, and what the upgrade does and does not protect
Ironwood strengthens privacy at the protocol level, but it does not make your transactions untraceable if you connect your ZEC to a transparent address, an exchange, or your real identity elsewhere. The shielded design hides transaction details on the blockchain, but it cannot hide your behavior outside the blockchain. If you receive ZEC in a shielded address, keep it in that address, and never move it to a transparent address or a service that knows your identity, then privacy is strong. If you receive ZEC shielded, but then later send it to a Bitcoin address under your name on a regulated exchange, an observer can connect the two by following your behavior, even though the blockchain itself does not record the connection.
This distinction matters because Zcash has faced regulatory scrutiny. The European Union’s Anti-Money Laundering Regulation, effective July 2027, subjects privacy coins to enhanced due diligence requirements under Article 79. Some exchanges may delist ZEC or require additional verification from users depositing shielded funds. This is not a technical flaw in Zcash; it is a regulatory reality. Users should be aware that buying ZEC on a regulated exchange, moving it to a shielded address, and then returning it to an exchange months later creates a visible trail at the exchange layer, even if the on-chain transactions themselves are private.
The May 2026 Orchard flaw that prompted Ironwood did not mean that every Orchard transaction was compromised. The flaw was in the validity-proof system, and exploiting it would have required specific knowledge and access. However, because the flaw was not discovered and closed in real time, the conservative choice was to replace the pool entirely. Ironwood’s new cryptographic design addresses the vulnerability class, but cryptographic designs are never “perfect”—they are only more or less resistant to known attack vectors. Ironwood represents the current best understanding of how to build a scalable shielded transaction system. Future discoveries may prompt further upgrades, but such discoveries are rare and network upgrades have clear governance processes.
For practical purposes, users should understand that migration to Ironwood restores full confidence in the shielded pool’s integrity. If you move your ZEC to an Ironwood wallet and keep it in shielded addresses, your transaction privacy is restored to the level of security intended by the Zcash protocol. The upgrade is not about adding new features; it is about removing a known risk. Once you have migrated, you should not worry about the Orchard flaw—it is in the past.
Common migration mistakes and how to avoid them
The most frequent error is typing or pasting the recovery phrase incorrectly. A single wrong word will result in a different set of addresses and an apparent zero balance. If this happens, do not panic. Stop, exit the wallet, and try again. Compare each word in your written copy to your entry, letter-by-letter if necessary. Wallets typically warn you if a word is not recognized, so pay attention to these warnings rather than ignoring them.
The second common mistake is confusing the old wallet with the new wallet during transfer. Users sometimes send funds from the old wallet to the old wallet’s own address by mistake, creating a pointless transaction that wastes fees. Prevention is simple: when you are ready to transfer, generate a new address in your new wallet, copy it to a text editor or notepad, close the old wallet entirely, re-open the new wallet, confirm that the address you are about to use is still displayed, and only then proceed with the transfer. This deliberate pause eliminates the risk of sending to the wrong destination.
The third mistake is losing the recovery phrase during migration. Some users assume that once they have recovered their wallet in a new application, they no longer need the recovery phrase. This is false. The recovery phrase remains the master key to your funds. If your new wallet is corrupted, deleted, or inaccessible, you will need the recovery phrase to recover your balance again. Keep it in the same secure location where you kept it before. Do not change it, do not delete it, and do not assume you have memorized it. Write it down again if you only have a photograph.
The fourth mistake is not testing transactions before moving the full balance. The test transaction serves a crucial function: it confirms that your recovery phrase works, that the wallet can broadcast transactions, and that the network accepts them. Skipping this step means risking the discovery of a problem after you have already moved all your funds. The test takes 30 seconds and eliminates days of potential troubleshooting.
Buying ZEC and managing fees after migration
Once you have completed migration, you may want to add more ZEC or manage your holdings. ZEC is available on major cryptocurrency exchanges including Coinbase, Kraken, Gemini, and Binance. Buying ZEC on an exchange and withdrawing it to your shielded address is straightforward: create your withdrawal address from your new Ironwood wallet, copy it into the exchange, and process the withdrawal. The exchange will charge a network fee (typically 0.0001 to 0.0005 ZEC) and may charge a processing fee. Once the withdrawal is confirmed, the ZEC will appear in your wallet as shielded funds.
The ZIP-317 fee standard specifies that standard Zcash transactions incur 0.0001 ZEC, regardless of whether the transaction is transparent or shielded. This flat-rate design means your fees are predictable and do not spike during congestion. More complex transactions, such as consolidating multiple inputs or sending to many recipients, may cost more, but the wallet will calculate and display the fee before you approve the transaction.
Mining profitability and fee markets are separate questions. Zcash uses Equihash, a proof-of-work mining algorithm that is memory-intensive, making it resistant to specialized hardware dominance. If you are considering mining ZEC, profitability depends on your electricity costs, hardware efficiency, and current ZEC price. Mining calculators are available through community resources, but they fluctuate frequently. The key point is that miners are incentivized to process transactions by collecting fees, so the network will remain functional regardless of your personal involvement in mining.
Regulatory landscape and privacy-coin status in 2026–2027
The regulatory environment for privacy coins has tightened since 2024. The European Union’s MiCA (Markets in Crypto-Assets) regulation and the updated Anti-Money Laundering Regulation now explicitly address privacy-preserving cryptocurrencies. U.S. Financial Crimes Enforcement Network (FinCEN) guidance classifies privacy coins as higher-risk assets, requiring financial institutions to apply enhanced due diligence. This does not mean ZEC is illegal or that shielded transactions are prohibited, but it does mean that regulated services (exchanges, payment processors, custodians) are more cautious about ZEC involvement.
Practically, this means you should expect that some exchanges may require additional verification before allowing ZEC deposits or withdrawals, and some may delist ZEC entirely if regulatory pressure becomes severe. As of 2026, major exchanges still support ZEC, but users should verify this before planning any transfers. The privacy and regulatory tension is not a technical problem but a social one: jurisdictions are balancing financial crime prevention with privacy rights, and the outcome remains uncertain.
For users in jurisdictions with open regulatory frameworks, migration to an Ironwood wallet and continued use of shielded addresses carries no legal risk. Shielded transactions are not inherently illegal; they are a tool for financial privacy, like using a physical wallet instead of publishing all your cash movements. The regulations are directed at financial institutions, not at individual users. Owning ZEC, using shielded addresses, and conducting private transactions are all lawful in the vast majority of jurisdictions.
That said, users should understand the regulatory trajectory in their own country. If you are in a jurisdiction actively hostile to privacy coins, migrating to Ironwood may be less pressing than for users in jurisdictions with stable regulatory frameworks. However, if you already own ZEC, the Orchard flaw is reason enough to migrate regardless of regulatory considerations. An unfixed security vulnerability is a more immediate risk than regulatory uncertainty.
Frequently asked questions
What happens to my ZEC if I don’t migrate from Orchard to an Ironwood wallet by the deadline?
There was no hard deadline after July 28, 2026—Ironwood-compatible wallets can still access Orchard funds. However, wallets running old Orchard-only code cannot process new transactions after the activation. If your wallet has not been updated, it will stop working for sending transactions, though your balance remains secure on the blockchain. You can migrate at any time by recovering your recovery phrase in a new Ironwood-compatible wallet. The longer you wait, the greater the risk that you misplace your recovery phrase or forget how to recover it.
Do I need a new recovery phrase when I migrate, or can I use the same one?
You use the same recovery phrase. Your recovery phrase is a master secret that derives all your Zcash addresses, regardless of which shielded pool they belong to. When you perform a zec wallet download and recover your existing wallet, you enter the same recovery phrase you have been using all along, and the new wallet generates the same underlying addresses plus new unified addresses (u1 format). You do not create a new phrase unless you want a completely new wallet separate from your current one.
Is migrating to Ironwood a private transaction, or does it expose my balance and history?
Migrating within the shielded pools (Orchard to Ironwood) is a private transaction. The blockchain does not show the amount, sender, or recipient of a shielded-to-shielded transfer. However, if you move ZEC from a shielded address to a transparent address or to an exchange during migration, that movement becomes visible. Best practice is to recover your existing wallet in a new Ironwood-compatible application and allow the wallet to move funds internally through shielded transactions, preserving privacy throughout the migration.