Zcash Orchard Pool: How to Check Whether Your ZEC Balance Still Needs Migrating

If you keep Zcash in a shielded address, there is a fair chance that since late July your balance has been sitting in a part of the blockchain the network has decommissioned. Checking takes a few minutes: bring the wallet up to the current version, let it sync fully, and see whether the app reports a migration in progress. While one is running, do not send your full balance anywhere.

The background is unusual. On July 28, 2026, Zcash brought a new shielded pool into service and sealed the old one at the same moment. Around 3.66 million ZEC were sitting in it at that point, the equivalent of about 1.7 billion US dollars according to CoinDesk. The network does not move that money on its own; every owner triggers the transfer in their own wallet. Anyone who has not opened their wallet since then has simply not triggered it.

Zcash Migration: What Has Happened to Your ZEC Since the Ironwood Upgrade

The network upgrade goes by the name Ironwood and took effect at block height 3,428,143. We retrieved that block ourselves on September 13, 2026 through the public interface of Blockchair: it carries the timestamp July 28, 2026, 14:07:23 UTC. Since then the chain has been running with two shielded areas side by side, the old Orchard pool and the new Ironwood pool.

For you, none of this changes anything about your keys. You need no new address, no new seed phrase and no token swap. According to the technical specification, the key material you have been using to access shielded amounts applies equally to both pools. What changes is where your balance sits, and the route by which it gets there.

That route is called the turnstile. Every amount has to pass through it individually, and every passage is triggered by the wallet holding the funds. There is no switch in the protocol that moves all balances across at once.

Orchard, Sapling and Ironwood: An Overview of the Zcash Shielded Pools

A shielded pool is the part of the Zcash money supply whose amounts and participants sit encrypted in the blockchain and are readable only with the matching key. Its counterpart is the transparent area, where addresses and amounts lie open as they do with Bitcoin.

In practice you come across two kinds of address. A transparent address begins with a t and behaves like an ordinary crypto account. A shielded address begins with a z and conceals both amount and counterparty. Only the second case is affected by this migration.

Zcash has renewed its shielded technology several times over the years. Sprout from 2016 was followed by Sapling in 2018, Orchard was added in 2022, and Ironwood has existed since July 2026. Each of these stages is a pool of its own with its own bookkeeping, and balances do not move between them by themselves.

For everyday use that means your wallet can hold amounts in several pools at once without you noticing. The balance shown adds them together. Only when a pool is decommissioned does it become apparent that the total is made up of parts.

The Orchard Bug: Why Zcash Needed a New Shielded Pool

The trigger was a discovery by security researcher Taylor Hornby. As CoinDesk reported it, the proving circuit of Orchard contained a flaw that would have allowed counterfeit ZEC to be created without leaving any trace of it in the blockchain. On that account the flaw had been in the code since Orchard launched in May 2022, so for around four years.

The gap was found before it was demonstrably exploited. No damage has been evidenced so far. That, though, is exactly the problem with a weakness of this kind: a counterfeiting operation that leaves no trace also cannot be ruled out after the fact. So matters did not stop at fixing the flaw. The project rebuilt the entire bookkeeping of the shielded area from scratch.

The reasoning is set out in the specification of the upgrade. The purpose of NU6.3, it says there, is to strengthen confidence in the integrity of the Zcash money supply following the remediation of the Orchard vulnerability. The turnstile, it continues, ensures that the total supply remains bounded. Since a substantial share of all ZEC was sitting in the Orchard pool at the time of the fix, the move into a new pool was necessary.

At the core of the procedure is a reversal of the burden of proof. Everything that crosses into Ironwood through the turnstile is recorded openly and can therefore be reconciled. Whatever potentially counterfeit holdings may have arisen in Orchard stay there and do not come across.

Ironwood additionally brings a property that reaches beyond the present occasion: the specification names the recoverability of balances in the event that powerful quantum computers break today's cryptography. For holdings in the old pools, that protection expressly does not apply.

The Turnstile Explained: How the Crossing Between the Pools Works

A turnstile is a crossing between two pools in which the amount being moved sits openly in the blockchain, so that anyone can reconcile the total supply. Inside a pool, amounts stay hidden. When crossing between two pools, they become visible.

How a wallet is to carry out this crossing is governed by the document ZIP 318, titled "Orchard to Ironwood Migration". It describes no button for you to press, but a schedule your wallet works through. That distinction explains most of the confusion that has grown up around the migration.

At the level of the consensus rules, something has shifted in parallel that barely shows up in everyday use but explains why the old pool is described as sealed. Since the upgrade, outputs into the Orchard pool may only go to addresses for which the creator of the transaction can authorise the spend themselves. Translated: the old pool no longer accepts payments from third parties. It can only be emptied.

Is Your ZEC Still in the Orchard Pool? How to Check in Your Wallet

The check works much the same way in every serious Zcash wallet. It costs you a few minutes and a look at the version display.

Step 1: Bring the Wallet Up to the Current Version

A wallet that does not know the new pool cannot move to it either. Cake Wallet, for one, introduced support for Ironwood in version 6.4.0 according to its own documentation. Check your app's version number before you do anything else. Which software is suited to which purpose at all is broken down in our comparison of software wallets.

Step 2: Let It Sync Fully

Shielded balances are detected locally, by the wallet scanning through the blockchain. Before that sync is complete, your app does not reliably know which pool your money is in. After a longer break, this can take quite a while.

Step 3: Look for the Migration Notice

Wallets that support the transfer display it, usually as a progress indicator or as a notice in the account area. If you find nothing there and your balance is fully available, it is already in the new pool. If the app reports an operation in progress, you are one of the people who still has something in transit.

Two things should be made clear at this point, because scams form around every migration. There is no official website on which you have to enter your seed phrase to rescue your balance. And there is no support agent who will ask you to do so. The entire process runs in your wallet and without outside involvement. If you hold larger amounts, the question of custody is the more important one anyway. Our hardware wallet comparison shows which devices keep the key away from the computer.

How Long the Zcash Migration Takes and Why Your Wallet Deliberately Stretches It

Anyone expecting one click to be enough and the matter to be settled after two confirmations will be disappointed. The transfer drags on for hours or days, and that is by design.

The reason lies in the visibility of the turnstile. A single crossing with an odd amount would be a fingerprint by which a wallet could be recognised again over time. ZIP 318 counters that with three precautions your app implements in the background.

First, the wallet breaks your balance into fixed denominations. Permitted are amounts of the form one, two or five times a power of ten, so 100, 50, 20, 10, 5, 2, 1 or 0.5 ZEC for example. Each of these partial amounts goes through the turnstile as its own transaction and thereby merges with the partial amounts of many other users.

Then it spreads those transactions over time and draws the cryptographic anchors from network-wide uniform boundary heights. This creates groups of users whose crossings blend together. Finally, the specification separates syncing from sending: a wallet may not do both in the same background session, because otherwise an observer could connect the two.

In practical terms, that means your balance appears split for a while. Part of it is already in the new pool, part still in the old one. This is neither an error nor a loss, but the normal state during the transfer.

Three Mistakes That Slow Down the Migration of Your ZEC Balance

The App Stays Closed

The transfer only makes progress while the wallet is open and synced. Close it and the transfer pauses. The specification is explicitly reserved on this point: background execution is to be attempted on a best-effort basis at most, and wallets are not obliged to send a crossing without user involvement. Anyone who opens their app once a month extends the process accordingly.

The Entire Holding Is Sent Mid-Transfer

Cake Wallet's documentation expressly advises waiting with a payment until the migration is complete, and that applies particularly to any attempt to send the whole balance at once. During the transfer, parts of your balance are tied up in prepared transactions. A payment for the full amount can therefore fail or throw the schedule out of order.

The Wallet Is Restored on a New Device

This point is the one most likely to be overlooked. Under ZIP 318, a running migration need not be resumable on another device, nor after a restore from the seed phrase. A wallet that discovers unspent Orchard holdings after such a restore may treat the situation as a new migration and start over. If you want to change devices anyway, let the transfer finish first.

How Far the Zcash Migration Has Come: The Figures From Late June to Late August

How much is still outstanding can be quantified. The following values come from the third-quarter 2026 report by Pine Analytics, which shows the pool holdings week by week.

• June 30, 2026: the Orchard pool holds 3.77 million ZEC. Shielded holdings total 4.42 million ZEC, which corresponds to 26.3 percent of the circulating supply.
• July 28, 2026: Ironwood goes live. The Orchard pool holds around 3.66 million ZEC.
• August 17, 2026: a cumulative 3.08 million ZEC have flowed out of the old pool.
• August 24, 2026: the cumulative outflow reaches 3.73 million ZEC.
• August 31, 2026: the Orchard pool still holds 470,000 ZEC, the Ironwood pool 3.84 million. Total shielded holdings have risen to 4.86 million ZEC, up 9.9 percent on the end of June.

In five weeks, then, around 87 percent of the old pool has taken the route through the turnstile. In the final week of August, however, only 46,000 ZEC were added. What is left is evidently not a backlog that clears itself, but a residue of wallets nobody opens.

A comparison with earlier pool changes shows how unusually quickly the field was cleared. When Sapling launched in 2018, 8 percent of the predecessor pool had moved after five weeks and 54 percent after a year. With Orchard in 2022 it was 1.2 percent after five weeks. Anyone still in the old pool today belongs to a small minority, and nobody builds tools for small minorities any more.

The price gives a sense of the magnitude. We retrieved it on September 13, 2026 via the public price interface of CoinGecko: 1,093.69 US dollars or 941.86 euros per ZEC. The 470,000 ZEC remaining at month-end therefore correspond to around 443 million euros. For context: at the time of that retrieval, Zcash stood ninth among the largest crypto-assets with a market capitalisation of a good 18 billion US dollars, after a rise of 124.6 percent over 30 days and a fall of 7.9 percent over the last seven days.

What the Turnstile Reveals About You: The Privacy Downside of the Migration

The specification names the price of the procedure openly. The turnstile, it says, discloses the amounts moving between the pools, including the amounts migrated to Ironwood. So anyone bringing their shielded holdings across publishes their size in the blockchain.

Hence the denominations. If your balance goes through the turnstile in portions of 10 or 50 ZEC and thousands of other wallets use the same portion sizes, the individual crossing says little about you. A one-off crossing of 137.42 ZEC, by contrast, is a marker that can be found again later.

From this follows a recommendation that runs against the first impulse: do not take the process into your own hands. Anyone who grows impatient and pushes their holding across in a single large transaction saves a few days and gives up in exchange the amount concealment that is the whole reason for using a shielded address.

An important point of context: the vulnerability that was found concerned the bookkeeping, not the confidentiality. According to the specification there is no reason to assume that key material of existing addresses could have been compromised by it. Your old addresses have therefore not become insecure.

ZEC on an Exchange: Why the Pool Migration Mostly Does Not Concern You There

If you hold your ZEC at a trading venue, you have no access to the pool in any case. There, the provider decides in what form it holds customer balances, and it carries out its own transfer if it is affected. For you that is a question of provider quality, not a task.

Two points are still worth a look. Check on your provider's status page whether deposits and withdrawals for ZEC are open before you plan a withdrawal. And check whether your provider is still listing the coin at all. Privacy coins are under regulatory pressure in the EU, which we have broken down in our overview of the planned trading ban on privacy coins. Anyone who needs a second point of access just in case will find the regulated alternatives in our comparison of crypto exchanges.

When you bring holdings from a trading venue into your own wallet, they land there transparent or shielded depending on the type of address. Shielded incoming amounts go into the new pool today. Under the changed consensus rule, the old one no longer accepts payments from others.

What Happens If You Leave Your Orchard Balance Where It Is

In the short term, nothing happens. There is no deadline in the calendar on which Orchard holdings expire, and by all accounts the transfer is voluntary and user-initiated. Nor had the project named an announced shutdown date for the old pool as at September 13, 2026.

The direction is nonetheless unambiguous, and it is stated in the specification itself. It says there that recovery would not be possible for funds still located in the Sprout, Sapling or Orchard pools; all such funds would be inaccessible once the respective protocols are shut down. They should be migrated into the Ironwood pool in order to benefit from the new property. That is the phrasing of a technical document, and it describes a state that arises if the network one day switches off the old protocols.

On top of that comes a practical point that bites sooner than any shutdown. Tools, wallets and help pages follow the majority. With a residual holding of under three percent of the shielded supply, support for the old pool does not get better but worse. Anyone who can get the transfer done today with a progress bar might have to rebuild it by hand in two years.

In passing, because it coincides in time: a coin holder vote on the shape of the next network upgrade, NU7, is currently running, with a deadline of September 14, 2026 at 19:00 UTC. How to take part in it we have described in a separate article on the NU7 vote. That process has nothing to do with the pool migration; it merely lands on the same calendar.

Checking the Zcash Migration: What to Take Away

1. Open your Zcash wallet and check the version. Only a wallet that knows the Ironwood pool can carry out the transfer. Which software manages it and where its limits lie is set out in our comparison of software wallets.
2. Leave the app open until the process has run through. The migration only makes progress while the wallet is open and synced, and it deliberately spreads itself over hours or days. Do not send your full balance during that time. Anyone wanting to keep the key on a separate device while doing so will find the devices in the hardware wallet comparison.
3. Check your trading venue separately. Holdings at a provider are not something you migrate yourself. What counts there is whether deposits and withdrawals are open and whether ZEC is still listed. An overview of the regulated providers is given by our comparison of crypto exchanges.

The technical basis of this transfer is open to inspection. The rules for wallets are in ZIP 318, the changed consensus rules and the rationale for the upgrade in the ZIP 229 document on the version 6 transaction format. Both texts are technical, but they are the source every wallet relies on.

(As of September 13, 2026. This article is not investment advice. Prices and fee structures change; check the terms with the provider before you buy.)