7.16M BTC already sit behind a public key anyone can read. Is yours one of them?
Quantum computers could one day break the signatures that protect crypto wallets, but only when the public key is visible. Paste an address to see whether yours already is, since when, and what to do about it.
Check several addresses at once (up to 20)
We never store or log the address. It is sent once to a public blockchain data source and then forgotten. It is never sent in a URL, so the site's own cookie-free visit counter never sees it, and no third-party analytics run here. (The optional share link puts it after a # in your own browser bar; that part is never sent to any server.) Only paste addresses: never a recovery phrase or private key.
What "exposed" means
Most addresses hide the key until you spend
Bitcoin addresses starting with 1, 3 or bc1q are a hash of your public key. Spending reveals the key, so an address that has never spent is not exposed. On Ethereum your first sent transaction reveals it.
Some show the key from day one
Bitcoin Taproot (bc1p…) and early pay-to-public-key coins put the key on-chain directly. On Solana the address is the public key. These are exposed by design, not by anything you did.
No quantum computer can do this today
Google Quantum AI estimated in March 2026 that breaking Bitcoin's curve would need fewer than 500,000 physical qubits; today's largest machines have around a thousand noisy ones. Experts surveyed by the Global Risk Institute put the chance of such a machine within 10 years at 28–49%.
Exposed coins on the move
Coins whose public key has been visible for years are the first a quantum attacker could take, and the ones whose movement makes news. We check every new Bitcoin block for them.
| When | Amount | Oldest coin | What moved | Transaction |
|---|---|---|---|---|
| 15 Nov 2026, 21:49 UTC block 976,017 | 0 BTC ≈ $0 | 14 Jul 2011 untouched 15.3 years | Pre-2013 legacy 2 inputs | d473459ee2… |
| 15 Nov 2026, 21:49 UTC block 976,017 | 0 BTC ≈ $0 | 14 Jul 2011 untouched 15.3 years | Pre-2013 legacy 1 input | bc66092846… |
| 15 Nov 2026, 19:58 UTC block 976,008 | 5 BTC ≈ $324K | 15 Nov 2012 untouched 14.0 years | Pre-2013 legacy 1 input | 5a8b0f0c89… |
| 15 Nov 2026, 19:01 UTC block 976,003 | 0.03 BTC ≈ $1.9K | 5 Jun 2011 untouched 15.4 years | Pre-2013 legacy 2 inputs | 8365f617b6… |
| 15 Nov 2026, 10:52 UTC block 975,947 | 0.0002 BTC ≈ $9.72 | 3 Oct 2012 untouched 14.1 years | Pre-2013 legacy 2 inputs | 702b9b195f… |
How much is already exposed
Bitcoin is the only chain where the exposed amount can be measured, because its addresses normally hide the key. On Ethereum every account that has sent a transaction is exposed; on Solana every account is.
Weekly total since 14 Aug 2025: from 6.36M BTC to 7.16M BTC. Third-party estimate by Project Eleven's Bitcoin Risq List (a company that sells post-quantum security); its query is open source. Exchange cold wallets that reuse addresses move this number week to week.
Where the exposed coins sit
| Address type | BTC held | Exposed | Share exposed |
|---|---|---|---|
| P2PK (raw public key) | 1.71M BTC | 1.71M BTC | |
| P2PKH (1…) | 4.51M BTC | 1.16M BTC | |
| P2SH (3…) | 3.66M BTC | 1.18M BTC | |
| P2WPKH (bc1q…) | 8.31M BTC | 2.14M BTC | |
| P2WSH (bc1q…, long) | 1.69M BTC | 746K BTC | |
| P2TR Taproot (bc1p…) | 224K BTC | 224K BTC |
BTC held per type: Bitview (open-source chain indexer), 4.5 h ago. Exposed by reuse: Project Eleven, 9 Nov 2026. The two sources are a few days apart, so shares are approximate.
Measured by us: new Bitcoin outputs, last 144 blocks
5.4% of new outputs go to address types that show the public key straight away (mostly Taproot), carrying 36.4% of the value. And of the transactions that spend from a key-hash address (1… or bc1q…), 85.4% send coins back to the same key, keeping a key that has just been revealed in use. Batches of self-transfers push this up in some blocks.
SegWit bc1q 79.6%Other 6.0%Taproot 5.4%Legacy 1… 4.0%P2SH 3… 3.4%P2WSH 1.7%Raw key 0.0%- Average
- 10.2%
- Range
- 3.0% – 16.4%
- Latest full day
- 5.6%
3 days counted from every output in every block; 27 earlier days estimated from about 1,200 sampled transactions each, so day-to-day swings there are partly noise.
Every transaction (816,469) and every output (1,164,554) in the last 144 blocks, 975,911–976,054, read from the raw blocks. Share by number of outputs; data outputs (OP_RETURN) excluded. Updated 5 min ago.
Other published estimates
| Figure | What it measures | Source | Date |
|---|---|---|---|
| ≈1,720,747 BTC (~8.68% of value, ~0.025% of UTXOs) | BTC in P2PK outputs | Chaincode Labs | 28 May 2025 |
| ≈1.1M BTC (originally ~1M) | BTC mined by the 'Patoshi' miner presumed to be Satoshi, nearly all in P2PK and unmoved | Sergio Demian Lerner | 17 Apr 2013 |
| 6,909,255 BTC (~33% of supply) | Exposed BTC at block 936,882: reuse 4,994,044 (72.3%); P2PK 1,716,814 (24.8%); P2TR 198,106 (2.9%); P2MS 291 | Project Eleven | 6 May 2026 |
| ≈2.3M BTC dormant & quantum-vulnerable; >1.7M BTC (nearly 9%) in P2PK | BTC in exposed-key addresses inactive ≥5 years (top 100,000 addresses) plus P2PK | Google Quantum AI | 30 Mar 2026 |
| >4M BTC (~25% of supply): ~2M in P2PK + ~2.5M in reused P2PKH | BTC potentially vulnerable to a quantum attack | Deloitte Netherlands | Dec 2019 |
| ≈1.6M BTC (~8% of supply); only ≈10,200 BTC in UTXOs large enough to move markets | BTC in legacy P2PK; rest spread over 32,607 UTXOs of ~50 BTC each | CoinShares | 6 Feb 2026 |
| >65% of all ETH | Share of Ether in addresses whose public key has been published on-chain (accounts that have sent a tx) | Deloitte Netherlands | Feb 2022 |
| ≈20.5M ETH | ETH held by the 1,000 richest Ethereum accounts that have already sent a transaction (public key exposed) | Google Quantum AI et al. | 30 Mar 2026 |
Third-party estimates, quoted as published. Methods differ: some count only dormant coins, some include exchange wallets, and older figures predate Taproot. The Satoshi figure is an attribution by researcher Sergio Demian Lerner, not a fact on the chain.
Post-quantum readiness by chain
Where each network stands, from primary sources. Checked 12 Nov 2026. Not a ranking and nobody paid to be listed.
| Chain | Signatures today | Post-quantum plan | Next milestone |
|---|---|---|---|
| Algorand | Ed25519 (default accounts); Falcon-1024 native PQ accounts (opt-in) | Live | v5.1.0-beta (2026-11-06) adds Falcon-512, hybrid accounts and an AVM mldsa_verify opcode, with no protocol upgrade yet. PQ multisig is planned for end-2026, and a PQ VRF research paper for early 2027. |
| QRL | XMSS (hash-based) on mainnet; ML-DSA-87 on QRL 2.0 testnet | Live | Testnet V3 and QRL 2.0 mainnet: no date announced (roadmap says TBD). |
| NEAR | Ed25519, secp256k1; ML-DSA-65 (opt-in) | Live | Wallet support is rolling out. NEAR says PQ consensus will be ready by end-2027. |
| Mochimo | WOTS+ (hash-based one-time signatures) | Live | No date announced. |
| Solana | Ed25519 | Testnet | No date announced. Jump/Firedancer calls a Falcon verify syscall the 'immediate next step' (Apr 2026), but there is no open SIMD for it. |
| XRP Ledger | ECDSA secp256k1 and Ed25519 | Testnet | Phase 3: candidate PQ schemes on Devnet in H2 2026 (not confirmed as done). Phase 4: a native PQ amendment, targeting 2028. |
| Tezos | Ed25519 (tz1), secp256k1 (tz2), P-256 (tz3), BLS (tz4) | Testnet | Enabling tz5 on mainnet needs a future protocol amendment and vote; no date announced. |
| Sui | Ed25519, ECDSA secp256k1, ECDSA secp256r1, zkLogin, passkey | Testnet | Testnet for native ML-DSA-65 accounts by end-2026; mainnet Q1 2027; SLH-DSA vaults on mainnet targeted for 2026. |
| Aptos | Ed25519 (default), secp256k1, secp256r1/WebAuthn, Keyless | Testnet | Enable the feature flag on testnet, then mainnet via governance; no date announced. |
| Stellar | Ed25519 | Testnet | Protocol 30 mainnet vote on 2026-11-23 17:00 UTC (date from news coverage, not confirmed on stellar.org). Stage 2 in 2027: a CAP for PQ signers on classic accounts. |
| Cosmos Hub | secp256k1 (accounts), Ed25519 (validators); eth_secp256k1 on EVM chains | Testnet | Adoption depends on each chain's upgrade; no Cosmos Hub date announced. PQ consensus needs at least two-thirds of voting power on ML-DSA keys and IBC counterparties on CometBFT v0.40 or later. |
| TRON | ECDSA secp256k1 | Testnet | No mainnet date announced. |
| Asentum | ML-DSA-65 / Dilithium3 (claimed PQ from genesis) | Testnet | Mainnet and $ASE token launch announced; no confirmed mainnet date. |
| Bitcoin | ECDSA secp256k1 (legacy/SegWit v0) + Schnorr BIP-340 (Taproot) | Proposal | No activation path or date announced; a separate PQ-signature BIP is still "TBD" (BIP-361 lists it as a requirement). |
| Ethereum | ECDSA secp256k1 (EOAs); BLS12-381 for validators | Proposal | Hegotá hard fork, which includes EIP-8141; no activation date set yet (the EIP-8081 activation table is empty). Lean Ethereum, with hash-based (XMSS-style) validator signatures, is a longer-term roadmap. |
| Cardano | Ed25519 (BIP32-Ed25519 HD wallets); KES/VRF for stake pools | Proposal | No date announced; both CIPs are still open PRs. |
| Polkadot | sr25519 (Schnorrkel), Ed25519, ECDSA secp256k1 | Proposal | No date announced; the RFC is an open draft (last updated 2026-07-22). |
| Zcash | ECDSA secp256k1 (transparent); RedJubjub (Sapling); RedPallas (Orchard/Ironwood) | Research | Full PQ transition: leadership targets 2027 (May 2026 statement). The recovery protocol and PQ proof system are not yet specified. |
| Hedera | Ed25519, ECDSA secp256k1 | Research | PQ user keys targeted for 2027, after FIPS 206 (Falcon) is final; ML-DSA is the fallback if FIPS 206 slips. |
Questions people ask
Is my Bitcoin quantum safe?
Today, yes: no quantum computer can break Bitcoin's signatures. The long-term risk depends on whether your public key is visible. Addresses starting with 1, 3 or bc1q hide the key until they spend, so coins in a never-spent address are in the safest position Bitcoin offers. Coins in an address that has already spent, in Taproot (bc1p) addresses or in early pay-to-public-key outputs have a visible key. Project Eleven counts about 7.16M BTC in addresses whose key is already public (9 Nov 2026).
Does Taproot expose the public key?
Yes. A Taproot (bc1p…) address is built from a public key, so that key is visible on the blockchain as soon as the address holds coins, whether or not it has ever spent. This was a known trade-off when Taproot was designed. BIP-360 proposes a new output type without this key-path exposure.
Is Ethereum quantum resistant?
Not yet. Ethereum accounts use ECDSA signatures, and an account's public key becomes visible with its first sent transaction, so most active accounts are exposed. The plan: The EF formed a dedicated post-quantum team (announced 2026-01-23, led by Thomas Coratger; site pq.ethereum.org). EIP-8141 "Frame Transaction" (Draft) gives accounts a native way off ECDSA and is Scheduled for Inclusion in the Hegotá fork (EIP-8081). EIP-8288 "In-mempool signature and proof aggregation" (Draft, Buterin and…
Is Solana quantum resistant?
Not yet. A Solana address is its Ed25519 public key, so every account's key is visible from the start. Project Eleven and the Solana Foundation deployed PQ signatures on a Solana testnet (announced 2025-12-16; algorithm not publicly specified). The opt-in Winternitz one-time-signature vault program (Blueshift) exists as community code. SIMD-0461, a Falcon-512 verification syscall, was closed without merging on…
Should I move my coins because of quantum computers?
There is no emergency. If your Bitcoin sits in an address that has already spent, moving it to a fresh, never-used address of your wallet hides the key again at the cost of one normal fee. Stop reusing addresses. On Ethereum and Solana moving does not help much, because the key shows again the next time you send; there the fix has to come from protocol upgrades.
When could a quantum computer break Bitcoin?
Nobody knows. In March 2026 Google Quantum AI estimated that breaking Bitcoin's curve would need fewer than 500,000 physical qubits; the largest machines today have around a thousand noisy qubits. In a 2026 survey for the Global Risk Institute, experts put the chance of a cryptographically relevant quantum computer within 10 years at 28–49%.
Is it safe to paste my address here?
An address is public information, but it can link your coins together. We never store or log it: it is sent once in the request body to a public blockchain data source and then discarded. Never paste a recovery phrase or private key into any website.
How this works and where the data comes from
Bitcoin. We read the address type from its format (checked locally, including the checksum). For hash-based types (1…, 3…, bc1q…) the public key appears on-chain only when the address spends, so we look up its history on mempool.space (Blockstream Esplora as fallback): if it has spent, the key is public, and we find the oldest spend in its latest transactions (up to 100). Taproot (bc1p…) addresses contain the key itself, so they are exposed as soon as they hold coins.
Ethereum and EVM chains. Every transaction an account sends carries a signature from which the public key can be computed, so a nonce above zero on any chain means the key is public on all of them. We ask public RPC nodes (PublicNode, and zkSync's own endpoint) for the nonce, code and balance on Ethereum, Base, Arbitrum One, OP Mainnet, BNB Chain, Polygon PoS, Avalanche C-Chain, Linea, Scroll, zkSync Era, Gnosis. For Ethereum mainnet we date the first sent transaction with the Blockscout explorer API. For a Safe multisig we read its signers and threshold and check each signer the same way. Off-chain signatures (logins, permits) can also reveal the key and are not visible to us.
Solana. A Solana address is the Ed25519 public key itself. We check whether it is a valid curve point: program-derived addresses are not, and have no private key.
Privacy. The address goes from your browser to our server in the request body (never in a URL), is sent once to the data source above and is then discarded. We do not save it in a database, cache or log file. The optional share link puts the address after a # sign, which browsers never send to any server. The site counts page visits with its own cookie-free, self-hosted counter, which records the page path only; there are no third-party analytics.
Balance at risk counts the native coin only (BTC, ETH, BNB, POL, SOL), priced with CoinGecko. Tokens are not counted.
Sources: mempool.space; Blockstream Esplora; PublicNode; Blockscout; Project Eleven Risq List; Bitview; CoinGecko; bitcoin/bips
Information only, not financial advice. Data comes from public sources and can be delayed or wrong; check the primary source before acting.