Exposed bitcoin over time
Selected classes, stacked by month. The headline remains at the snapshot.
Hover or drag across the chart; arrow keys move one month. Home and End select the first and last months.
A count at a stated date
The public ledger records where keys have appeared. This tracker totals balances under a stated definition; it does not predict when a quantum attack becomes possible.
Monthly values · accessible table
Every recorded month end, in BTC, for the selected classes, with all unspent bitcoin.
Where the exposure sits
Every class remains visible when the selection changes.
Against Project Eleven
The definitions and dates matter as much as the difference between totals.
By output type, February 2026
How a key becomes visible
A visible public key gives a sufficiently capable quantum computer the input needed to recover a private key.
-
An address receives bitcoin
Only a hash of the public key appears in a key-hash output.
-
The address spends
A spending input reveals the public key.
-
A balance remains or returns
Any coins left at the address, or received later, now sit behind a visible key.
-
Some outputs start with a key
P2PK, bare multisig and Taproot show public keys from creation.
A coin behind a never-spent hash reveals its key when it is spent, before the spend is confirmed. The guide infers that a fast enough attack could fit inside Bitcoin’s roughly 10-minute block interval. This is the guide’s inference, not a result of this tracker; this count excludes that “on-spend” exposure.
Method notes
One recorded snapshot, with the counting rules and their limits kept beside the result.
Sources and dates
Downloads
The notebook contains stored outputs from the run. Running it again needs the project folder.