Bitcoin Quantum Exposure: 5.1M BTC at risk · ChainQuery.com
Bitcoin quantum exposure
Total BTC currently held at addresses whose pubkey has been revealed<br>on-chain. This is the supply that a sufficiently powerful quantum<br>attacker could steal by inverting ECDSA/Schnorr signatures. Updated<br>weekly from a full UTXO-set walk joined against our<br>revealed_addresses registry.
On this page
Summary
The breakdown
Balance distribution
Concentration
Aged exposure
Weekly change
History
Threat model
Why our number is honest
Methodology
BTC at risk
5,071,264
~25.3% of 20,041,145 BTC circulating
Always-exposed
1,063,006
P2PK + bare multisig + P2TR; pubkey is the output script
Reuse-exposed
4,008,258
P2PKH/P2WPKH/P2SH/P2WSH where a prior spend revealed the pubkey
Snapshot date: 2026-06-07<br>at block 952,694.<br>Updates every Sunday at 06:00 UTC from the weekly UTXO walk.
Baseline 2026 Q2 · quarterly PDF report
Cobranded with LearnBitcoin. Snapshot block 952,694,<br>2026-06-07. Methodology version v1.0.
Open PDF →
New to this? Read the plain-English explainer first.
This page is the live-data view for advanced readers. Read our<br>companion rabbit hole on LearnBitcoin.com for the layman's<br>walkthrough of quantum computing and Bitcoin :<br>what it actually threatens, why P2PK and P2TR are exposed by<br>design, and what you can do today.
Quantum and Bitcoin (LearnBitcoin rabbit hole) →
The breakdown
Six buckets, ordered by BTC at risk.<br>Where the BTC lives on the left (each wedge is that script<br>type's share of the at-risk BTC).<br>Where the addresses are on the right (each wedge is that<br>script type's share of the at-risk address count). When the same script type<br>makes a big slice in one wheel but a sliver in the other, concentration is<br>at work.
Where the BTC lives
P2WPKH reuse-exposed: 1,896,840 BTC (37.4% of BTC) · 3,534,421 addresses (27.7% of addresses)
P2PKH reuse-exposed: 1,196,717 BTC (23.6% of BTC) · 3,927,012 addresses (30.8% of addresses)
P2PK always-exposed: 853,246 BTC (16.8% of BTC) · 22,223 addresses (0.2% of addresses)
P2WSH reuse-exposed: 675,992 BTC (13.3% of BTC) · 88,940 addresses (0.7% of addresses)
P2SH reuse-exposed: 238,709 BTC (4.7% of BTC) · 279,102 addresses (2.2% of addresses)
P2TR always-exposed: 209,759 BTC (4.1% of BTC) · 4,897,349 addresses (38.4% of addresses)
5,071,264<br>BTC at risk
Where the addresses are
P2WPKH reuse-exposed: 1,896,840 BTC (37.4% of BTC) · 3,534,421 addresses (27.7% of addresses)
P2PKH reuse-exposed: 1,196,717 BTC (23.6% of BTC) · 3,927,012 addresses (30.8% of addresses)
P2PK always-exposed: 853,246 BTC (16.8% of BTC) · 22,223 addresses (0.2% of addresses)
P2WSH reuse-exposed: 675,992 BTC (13.3% of BTC) · 88,940 addresses (0.7% of addresses)
P2SH reuse-exposed: 238,709 BTC (4.7% of BTC) · 279,102 addresses (2.2% of addresses)
P2TR always-exposed: 209,759 BTC (4.1% of BTC) · 4,897,349 addresses (38.4% of addresses)
12,749,047<br>at-risk addresses
Same numbers, as horizontal stacked bars:
BTC
addrs
P2WPKH<br>reuse-exposed
P2PKH<br>reuse-exposed
P2PK<br>always-exposed
P2WSH<br>reuse-exposed
P2SH<br>reuse-exposed
P2TR<br>always-exposed
The largest single bucket is not Satoshi.<br>1,896,840 BTC is currently held at<br>P2WPKH addresses that have been reused at least once.<br>That is 37.4% of the at-risk pool, the<br>editorial pivot of the entire dataset. Reuse-exposed legacy and segwit<br>hashed types together dwarf the ancient P2PK supply: this is users today,<br>not a museum piece.
Every new taproot output is exposed at creation time, by design.<br>P2TR (BIP-341) uses the x-only tweaked pubkey directly as the bech32m<br>address. There is no hash layer in front. Every new P2TR output adds to<br>always-exposed supply the moment it lands on chain. Coins leave that pool<br>only when they're spent to a non-always-exposed script type.
P2PK: tiny by entries, huge by BTC.<br>22,223 addresses<br>(0.17% of at-risk) hold<br>853,246 BTC:<br>16.8% of at-risk supply.<br>Average ≈38 BTC per address;<br>≈896× P2TR's average in the same always-exposed category, and ≈97× the pool-wide average.
Raw figures by script type
Script type<br>Exposure<br>Addresses<br>BTC at risk<br>% of at-risk<br>Share
witness_v0_keyhash<br>reuse<br>3,534,421<br>1,896,840.38<br>37.40%
pubkeyhash<br>reuse<br>3,927,012<br>1,196,717.12<br>23.60%
pubkey<br>always<br>22,223<br>853,246.50<br>16.83%
witness_v0_scripthash<br>reuse<br>88,940<br>675,991.52<br>13.33%
scripthash<br>reuse<br>279,102<br>238,709.23<br>4.71%
witness_v1_taproot<br>always<br>4,897,349<br>209,759.13<br>4.14%
Balance distribution
At-risk addresses grouped by current balance. BTC share runs leftward from<br>the bucket label; address-count share runs rightward; both at the same<br>0-100% scale. The crossover row (highlighted) is where the two are<br>balanced: above it addresses dominate, below it BTC dominates.
Of the 12,749,047 at-risk addresses,<br>277,394<br>currently hold exactly 1 satoshi,<br>2,694,209 hold under 1,000 sats,<br>and 11,484,229 hold under 1M sats.<br>Dust dominates by count; whales dominate by value.
Share of BTC
bucket
Share of...