Zcash Ironwood Upgrade Is Live: What the Orchard Pool Migration Means for ZEC

At block 3,428,143 on July 28, 2026, Zcash pulled the lever. Orchard was sealed and Ironwood took the stage. If your ZEC lived in Orchard, you now have homework.

Within hours, the new pool barely held a dent of the total shielded supply. Wallets scrambled to ship updates, node operators compared notes, and users asked the same question: am I moving funds today or waiting a week?

Here is what changed, what did not, and how to move without tripping over the details.

Zcash’s Ironwood upgrade (NU6.3) is live on mainnet. The network sealed the legacy Orchard pool and introduced a fresh pool under the Ironwood ruleset. Practically, that means new shielded funds should land in the Ironwood pool, and the community now begins a long, careful migration out of Orchard.

The point is not change for its own sake but reducing technical debt and improving long-term privacy. Sealing an old pool narrows the attack surface and moves everyone toward the same, better circuit.

Activation did not come out of nowhere. The Zcash Foundation’s Zebra 6.0.0 release locked in the parameters and is the stable client line for the upgrade. Mainnet activated at height 3,428,143 with Consensus Branch ID 0x37A5165B, and testnet at 4,134,000. Those are the anchors the ecosystem is building around now (Zcash Foundation). The community announcement on activation day confirmed the Orchard seal and urged users to update wallets and libraries promptly (Zcash Community Forum).

How We Got Here: Orchard to Ironwood

Zcash has rotated privacy pools before. Sprout gave way to Sapling. Sapling yielded to Orchard. Each step tightened security assumptions, improved performance, and tried to keep privacy practical for real users.

Orchard’s dominance before the switch

By mid-July, Orchard had become the center of gravity for shielded ZEC. Community stats for the week of July 8–12 estimated roughly 3,766,859 ZEC in Orchard and a total shielded supply of about 4,435,157 ZEC. In plain English, most shielded ZEC sat in Orchard heading into Ironwood (ZecHub).

Why seal such a big pool? Because security and maintainability age. New circuits, better proving systems, clarified consensus rules, and more predictable development paths are easier to deliver when there is one main pool, not a patchwork of legacy options.

What Actually Changed at Activation

Ironwood did three big things at go time: sealed Orchard from new inflows, defined a new pool under NU6.3, and advanced consensus to a new branch ID.

What your wallet sees

Wallets that support Ironwood should present new receive options tied to the Ironwood pool. Orchard addresses remain for viewing old notes and spending them out, but you will not be pushing new funds into Orchard. Expect your wallet to label this clearly, once updated.

What your node needs

Nodes need to understand NU6.3 rules and the new branch ID. If you run infrastructure, lock in Zebra 6.0.0 or another client line that explicitly states Ironwood support. Mixing pre-upgrade and post-upgrade software is how people create headaches for themselves.

A simple migration checklist

1. Update your wallet or node to an Ironwood-ready release. Read the release notes.
2. Verify new receive options point at the Ironwood pool. Stop receiving into Orchard.
3. Test a small spend from Orchard to Ironwood. Confirm it settles and is recognized by your wallet.
4. Check viewing keys and backups. Make sure you can see both Orchard and Ironwood balances.
5. Stagger larger moves over time. Watch fees and network conditions.

Some users will migrate in one shot. Others will wait for their favorite wallet or exchange to green light Ironwood and then move gradually. There is no one-size path here.

Early Flows and What They Say

On day one, migration moved slower than the hype. Community trackers and node output a few hours after activation suggested the new Ironwood pool held around 104,035 ZEC while roughly 3.56 million ZEC still sat in Orchard. That is roughly 3 percent moved on the first day (BSCN).

Why slow is normal

Users do not migrate at the flip of a switch. Wallets and custodians batch upgrades, proof systems reindex, exchanges reopen shielded withdrawals in stages, and everyone kicks the tires before moving size. Given that the July 12 snapshot showed Orchard holding the lion’s share of shielded ZEC, a multi-week migration was always the base case (ZecHub).

Reading the numbers carefully

Early pool balances are only a mood check. They do not capture planned custodial migrations, exchange hot wallet moves, or delayed wallet releases. Treat them as direction, not destiny. The key milestone is when major wallets default to Ironwood receive addresses by design, not user choice.

What This Means for Users and Businesses

For everyday users

If your funds are in Orchard, they remain yours. The pool is sealed to new inflows, not destroyed. Your task is to spend or migrate those notes into Ironwood when your tools are ready. Plan to move in chunks, keep viewing keys safe, and confirm that your recipient supports Ironwood before you hit send.

For wallets

Wallet teams carry the heavy load: updating proof libraries, adjusting address formats and UI, fixing note scanning, and making sure users cannot accidentally send new funds into Orchard. The Zebra 6.0.0 baseline gives clear network parameters to target (Zcash Foundation), but each wallet has its own backlog.

For exchanges and custodians

Expect staged rollouts. Some will enable deposits to Ironwood first, then open withdrawals, then allow internal migrations of legacy balances. There may be brief pauses in shielded operations while audits run. The safe approach is to check the status page of your venue before you attempt a large transfer.

For explorers and indexers

Analytics will span two pools for a while. That influences metrics like anonymity set size, average note age, and spend patterns. Labeling must be crystal clear so users can tell which pool a transaction belongs to.

Privacy, Fees, and the Anonymity Set

Short term, privacy dynamics are awkward. A brand new pool starts small, which reduces the size of the crowd you hide in. Orchard still contains a large majority of shielded ZEC for now, which means many users will sit tight until Ironwood fills out.

Practical privacy tips

• Avoid merging multiple doxed sources into a single move while migration is young. Break it up.
• Coordinate with recipients. If they are still Orchard only, do not force a cross-pool hop that reveals relationships.
• Give the new pool time to grow. If your threat model is strict, wait until liquidity and usage widen.

About fees and throughput

Fee markets on Zcash are typically stable, but short bursts can happen around upgrades. Watch your wallet’s fee recommendations and do not race the mempool if you do not need to.

Forum screenshot showing migration / turnstile UI (labels include Turnstile / Shielded / Ironwood) — illustrates the user-facing migration flow and that cross-pool (turnstile) activity is visible on-chain. — Source: Zcash Community Forum

What to Watch Next

The next couple of weeks will set the tone for the rest of the quarter. A few milestones to track:

• Top wallet releases that default to Ironwood addresses and clearly flag Orchard as legacy.
• Major exchanges reopening shielded deposits and withdrawals under Ironwood.
• Visible growth in Ironwood pool balance relative to Orchard, ideally on a steady slope rather than spikes.
• Updated documentation across libraries and SDKs signaling stable support.
• Any bugfix releases for Zebra or related tooling after broader usage kicks in.

Activation is the start line, not the finish line. The finish is when users stop thinking about pools entirely and just use ZEC privately without friction.

Risks & What Could Go Wrong

• Wallet lag: If your wallet lags the upgrade, you could misroute new funds or fail to see balances properly until it updates.
• Reduced short-term privacy: A small Ironwood anonymity set can make patterns stand out if you move size too early.
• Exchange delays: Custodians may take weeks to enable full Ironwood support, causing stuck deposits or paused withdrawals.
• Phishing and fake tools: Upgrades attract scammers promising instant migrations or “fee-free” transfers. Do not touch them.
• Operational mistakes: Incorrect backups or missing viewing keys could complicate recovery when moving between pools.
• Unexpected client bugs: Edge cases in libraries or indexing could require hotfixes. Stay near official channels.

Move deliberately. The biggest risk in migrations is not market volatility, it is hurried ops.

Frequently Asked Questions

Do I have to move my ZEC out of Orchard right now?

No. Orchard is sealed to new inflows, not erased. Your funds remain spendable. Migrate when your wallet supports Ironwood and you have verified backups. Many users will stage moves over several transactions.

How do I know my wallet is Ironwood ready?

Look for a release note that references NU6.3 or the new Consensus Branch ID 0x37A5165B and clearly offers an Ironwood receive option. When in doubt, ask the wallet team or check official channels. Node operators should target Zebra 6.0.0 as the stable baseline (Zcash Foundation).

What happens if I send to an Orchard address now?

You should avoid creating new Orchard outputs. Updated wallets will steer you to Ironwood by default. If you try to send to an Orchard address with a wallet that has not updated, you risk misbehavior or failed sends. Update first.

Is privacy worse during the migration window?

Briefly, it can be. A brand new pool has a smaller crowd to blend with. If privacy is your top priority, consider waiting until the Ironwood pool grows or splitting large moves into smaller spends over time.

Are exchanges supporting Ironwood yet?

Support will roll out in stages and varies by venue. Some will accept deposits first and enable withdrawals later. Check your exchange’s status page before initiating a transfer.

What exactly did block 3,428,143 do?

That is the mainnet activation height for Ironwood. At that block, the network shifted to NU6.3 rules, sealed the legacy Orchard pool to new inflows, and began operating under the new branch ID. See the activation notes on the community forum for details (Zcash Community Forum).

How long will the migration take?

There is no fixed timeline. As of activation day, early community readings suggested only a few percent had moved into the new pool, which is normal for day one (BSCN). Expect weeks, not hours, for the ecosystem to fully settle.

Disclaimer: This article is provided for informational purposes only. It is not offered or intended to be used as legal, tax, investment, financial, or other advice.

Share With Others