Bitcoin, on the wrong side of the quantum boundary.
Roughly 4,000,000 BTC sit in outputs whose public keys are already exposed: early coinbases, reused addresses, Satoshi's coins. At today's price that is hundreds of billions of dollars waiting on nothing but hardware, because for those coins there is no harvest-now-decrypt-later. The keys are public now. This gateway moves Bitcoin to the other side of the boundary, where taking it means forging the NIST post-quantum signature below. It is running live on this page.
Exposure estimate: Deloitte, "Quantum computers and the Bitcoin blockchain" (~25% of circulating BTC in quantum-exposed outputs). Price: loading. Methodology notes in what is trusted.
LIVE The operations terminal is running right now. Every five minutes it pays a machine to think over post-quantum Lightning, in front of whoever is watching. This page is the evidence; the terminal is the show. Open the terminal →Below are two real signatures from this gateway's own history, byte for byte. The left one guarded the Bitcoin deposit before it crossed. The right one is what guards gateway events after. Both are shown in full.
Crossing the boundary is not the destination. On the far side there is an economy: a consensus-enforced stablecoin, a post-quantum Lightning network, and machines that pay each other for work. The line is being extended station by station, and each station lights up on this page only when its connection is real.
Stations marked ● are live now. Stations marked ○ run on infrastructure that is already deployed: USDSOQ enforcement is in Soqucoin consensus, and the Lightning stack and the paying machines run on this same server. The gateway's connection to them ships next, and this page will light them up when it does.
Every money event this gateway performs is signed with ML-DSA-44 and published: deposit confirmed, receipt minted, receipt returned, Bitcoin released. The rows below verify themselves in your browser as they load. Nothing here asks for trust; the code that reproduces each checkmark is printed under the table and runs anywhere.
A signature that verifies here verifies anywhere, forever.
Get your fortress payout address
- Get the wallet. Install SoquShield, free for iPhone and Android. Open it, tap Receive, and copy the address it shows you. It starts with ssq1. That is where your receipts will land.
- Paste that address below and press the button. You get back a Bitcoin address that belongs to you alone.
- Point Bitcoin at it. Paste it into your mining pool's payout settings, or send to it from any Bitcoin wallet. Every coin that arrives becomes a quantum-safe receipt in your SoquShield, automatically. No terminal, no code.
This pilot runs on test Bitcoin (the testnet4 network), so nothing you try here risks real coins.
Bring it back home
Your coins are never captured. Tell the gateway which Bitcoin address is yours, then send your receipt coin (the exact coin the mint delivered to your SoquShield) to the redemption address it shows you. The gateway releases your Bitcoin back to you.
The invariant this gateway must never break: Bitcoin in the vault covers every receipt outstanding. Both numbers come from chain data, and the receipt ledger is rebuildable by anyone from the on-chain mint tags, without our database.
Books notarized by Bitcoin itself: the ledger's merkle root is written into a Bitcoin transaction on a schedule. Last anchor: · . Recompute the root from the public attestation feed and compare; the recipe is in the gateway API response.
This is a custodial pilot on test networks. The Bitcoin is testnet4 coin with no monetary value, and the gateway operator holds the Bitcoin-side keys, the same trust shape as the Bitcoin leg of every bridge in production today. What you are evaluating is the post-quantum shield around it.
The receipt is an overlay asset. Receipt accounting is tracked by the gateway and tagged on-chain so anyone can rebuild the ledger; it is not yet enforced by Soqucoin consensus. The consensus-native stablecoin it connects to, USDSOQ, already is. Shipping untested consensus code days before a demo is how networks get bricked, so the consensus-native BTCSOQ asset is the roadmap, stated plainly.
The Bitcoin leg signs with classical cryptography, because Bitcoin's consensus accepts nothing else. Everything on our side of the boundary, receipt custody, redemption authorization, and the signed ledger above, is ML-DSA-44.
The USDSOQ hop is a treasury swap. When a loop completes, the gateway sends a fixed slice of its own SOQ float to the convert treasury and receives USDSOQ from existing inventory at the market price, spread disclosed in the quote. Supply does not change; only authority keys can change supply, and they are nowhere in this path. USDSOQ itself is enforced by Soqucoin consensus at the block level.
The Lightning hop rides a hosted channel. The gateway's payer channel on the L2SOQ LSP is custodial bookkeeping, the same posture as the rest of this pilot, and every payment is an eLTOO state update signed into the LSP's ledger. The proof that matters is the seller's ML-DSA-44 receipt, which verifies in your browser and binds the invoice, the question, and the answer.
The exposure figure is an estimate. The ~4M BTC number comes from published analyses of pay-to-public-key outputs and address reuse (Deloitte and subsequent studies). The dollar figure uses a live market price and moves with it. One more honest detail: taproot addresses, including this gateway's own deposit addresses, expose their public key from the moment they are funded. On Bitcoin that is unavoidable by design, which is exactly the point of moving value behind post-quantum custody.
Confirmation policy is disclosed: one confirmation on testnet4 for this pilot. A mainnet deployment would hold at six.