First get out. Then land somewhere verifiable.
These are separate decisions. Exiting zBTC uses Zeus's own redemption or DEX liquidity — infrastructure we do not operate and cannot vouch for. Redemption verified working on 2026-07-22/23, but it is rate-limited, the reserve is 8x smaller than last year, and a bridge whose token has collapsed has no economic engine to maintain those exits forever. Landing on Taifoon is the second move, and it opens proof-gated.
Zeus’s redemption (Unpeg) is working as of 2026-07-23 — we watched a 1.42 BTC withdrawal pay out on Bitcoin in 22 minutes. Burning zBTC for native BTC is the cleanest exit: you end holding keys on Bitcoin itself. Know the constraint: withdrawals are quota-limited to 5 BTC per 24h window per guardian setting, so large exits take days — start early, and verify with a small amount first. If redemption ever stalls, Solana DEX liquidity (zBTC pairs) is the fallback, at whatever discount the market sets. Both paths are Zeus’s infrastructure, not ours.
Hold native BTC, watch it through the live read rail today, and deposit into the write rail when it opens on mainnet — behind multisig custody and on-chain SPV verification, never before. No points, no epochs, no yield promises: a mint happens when a 6-layer proof of your deposit verifies, and that is the entire pitch.
What is live today →The zBTC reserve, recomputed — not attested.
We derived Zeus's 7 Bitcoin cold-reserve addresses from the guardian public keys their own backend publishes, and re-verify them against Bitcoin and the zBTC supply on Solana continuously. No allegation, no trust — just the number, with its sources. At genesis this same decoder points at foonBTC's own custody.
Three steps from stranded to verified.
Verify what you actually hold
zBTC is a claim on a bridge, not Bitcoin. Check your balance and the bridge's reported reserve before deciding anything — the gap between those two numbers is your real risk.
Exit to native BTC
Redeem through APOLLO while it processes, or swap out through Solana DEX liquidity. Test with a small amount first. End state: BTC at an address whose keys you hold.
Reserve your landing
Join the landing list below. When the mainnet write rail opens you get the custody model, the verifier addresses, and the deposit steps — one email, everything checkable.
What changes when you land.
zBTC's mission — permissionless Bitcoin on Solana — was right, and it's the same mission foonBTC continues. What changes is the trust core:
One email when the rail opens.
No newsletter, no token pitch. Your email is stored server-side and never shown publicly; the wallet field is optional and only used to notify you of proofs relevant to your addresses.
What Landfall will never do.
A migration pitch from a bridge that just failed its users has to be held to a higher bar. So hold us to this one.
Mainnet deposits stay closed until BTC custody is multisig — a single admin key is how bridges die, and we will not open on one.
A synthetic mints only when the 6-layer V5 proof of the underlying deposit verifies on-chain. No proof, no mint — including for us.
We do not promise yield on your BTC. If a yield integration ever ships, it will be named, opt-in, and separately risk-labeled.
Devnet is labeled devnet, pending is labeled pending. Statuses on these pages change when reality does, not when marketing wants.