ZEC Ironwood Migration Tracker
What is happening to Zcash?
NU6.3 "Ironwood" opens a new shielded pool designed for quantum recoverability and closes the old Orchard pool to new user-to-user payments. Every shielded ZEC balance is expected to migrate across a turnstile that — for the first time — makes cross-pool migration amounts publicly countable without weakening anyone's privacy inside the pools.
This page counts it. Testnet activated 3 July 2026 (height 4,134,000); mainnet is targeted around 21 July 2026 (final height to be announced — Shielded Labs has floated a short delay while exchanges and mining pools finish migrating off zcashd). The moment the pool goes live, the migration percentage below starts moving.
Ironwood status
Migration progress
Ironwood pool
Orchard pool
Shielded share
Chain height
Value pools right now
Where every ZEC sits, as reported by getblockchaininfo on our node.
| Pool | ZEC | % of supply |
|---|---|---|
| loading… | ||
Migration over time
Orchard vs Ironwood balances from our 15-minute recorder. We started the series on 4 July 2026 — before mainnet activation — so the whole migration curve is captured from block one. It cannot be backfilled later.
What the turnstile means
Funds leaving Orchard pass an accounting checkpoint that stops more ZEC exiting than ever entered — the response to the 2025 Orchard counterfeiting-risk disclosure. Two consequences worth understanding:
- Supply auditability — for the first time since Orchard launched, the chain proves the shielded supply is intact as value crosses. The migration percentage above is that proof, in one number.
- Migration amounts are public — individual transfers stay private inside each pool, but the pool totals move visibly. If you migrate a distinctive amount in one go, timing correlation is possible: wallets are expected to split and randomise. (Our number tracks the aggregate, which is exactly what the turnstile makes public anyway.)
- 3 July 2026
- Testnet activation (height 4,134,000) — validated against our own testnet rig.
- ~21 July 2026
- Mainnet target. Height TBA in a zebra release; possible short delay under discussion.
- Spec
- ZIP-229 (v6 transaction format) · upgrade hub
For agents & builders — same data, API-shaped
Everything charted here is free JSON. If you are an AI agent, skip the pixels and take the endpoints; they are also listed in llms.txt and the Gopher-over-HTTPS directory.
# live snapshot (free, cached 60s)
curl https://api.seneschal.space/v1/zec/ironwood
# 15-min history for charts (free)
curl 'https://api.seneschal.space/v1/zec/ironwood/history?window_ms=604800000&max_points=500'
# agent-priced atomic fact — $0.001 via x402, no account
GET https://api.seneschal.space/v1/q/zec/pools
# MCP (Claude / Cursor): https://mcp.seneschal.space/mcp
tool: seneschal_q { "question": "zec/pools" }
Watching for a payment instead? Our view-key payment webhooks are being validated on the Ironwood testnet so ZEC detection keeps working through activation.
Who watches this number
- Traders & analysts — migration velocity is a live confidence gauge: a fast, orderly migration signals holders re-committing to the shielded pool; a stall signals friction or wallet unreadiness. This series is quotable per-hour.
- Press & researchers — "how far along is the Zcash migration?" has exactly one honest answer and it's the migration percentage above, with history you can chart from before activation.
- Wallet & exchange engineers — the activation status and pool balances are canary signals for your own rollout (deposits paused? scanner blind?). Poll the free endpoint; it costs you nothing.
- Agent builders — need it inside a loop? The $0.001 penny fact returns in ~50 ms with no key and no account, paid per-call over x402.
Want per-block turnstile granularity (every migration crossing, as it happens)? We are gauging demand for a premium feed — say so on the board and it gets built.