Bitcoin Supply Quantum Risk Hits 35% as Public Keys Sit Exposed
Glassnode data shows 7.12 million Bitcoin face quantum computing exposure because their public keys sit visible on the blockchain, including Satoshi Nakamoto holdings.

Sofia Marquez
Regulation & Tech Editor, RefreshCoin
More than 35% of all circulating Bitcoin currently sits in addresses that expose public keys to potential future quantum attacks, according to on-chain research from Glassnode. The data shows roughly 7.12 million BTC, representing 35.4% of existing supply, resides in address formats where cryptographic safeguards have already been partially uncovered on the public ledger.
The vulnerability stems from standard public-key cryptography. When an address reveals its raw public key, quantum algorithms could theoretically calculate the private key once sufficiently powerful hardware emerges.
Modern Bitcoin addresses shield the public key behind cryptographic hash functions until a transaction is signed. Older formats, such as Pay-to-Public-Key (p2pk) used in Bitcoin's earliest days, published raw public keys directly to the chain. Reused addresses also expose public keys as soon as a single outbound transaction occurs, leaving any residual or subsequent balances unprotected by hash pre-images.
How does public key exposure create quantum vulnerability?
Public key exposure creates quantum vulnerability because quantum computers running Shor's algorithm can derive an underlying private key directly from an unhashed public key.
Standard elliptic curve cryptography relies on the mathematical difficulty of solving discrete logarithms. Classical supercomputers cannot crack secp256k1 within any practical timeframe. Shor's algorithm, however, breaks discrete logarithm assumptions if executed on a quantum system with several thousand stable logical qubits.
When a user keeps Bitcoin in a standard Pay-to-Public-Key-Hash (p2pkh) address and never spends from it, the public key remains hidden behind SHA-256 and RIPEMD-160 hashes. Quantum computers cannot reverse secure hash functions via Shor's algorithm. Grover's algorithm only cuts hash security in half, leaving SHA-256 well beyond theoretical brute-force thresholds.
Once an address spends funds, the public key enters the blockchain ledger permanently. If that address still holds coins or receives new payments, those funds no longer benefit from the hash shield.
The risk is concentrated in legacy practices.
The 7.12 Million Coin Breakdown
Glassnode isolated the 7.12 million coins by filtering every unspent transaction output (UTXO) where the full public key is readable on the ledger. This total equals more than a third of the roughly 19.8 million Bitcoin mined to date.
Early miners received block rewards paid directly to public keys. This legacy structure dominated network activity throughout 2009 and 2010.
Satoshi Nakamoto accumulated an estimated 1.1 million Bitcoin during this initial era. Those coins sit across thousands of early p2pk outputs that display their public keys in plain view. Because Nakamoto ceased public communication in 2011 and has never moved these balances, those coins cannot update to newer script formats unless the founder returns.
The remaining 6 million exposed Bitcoin belong to early adopters, long-dormant wallets, and entities that routinely reuse addresses.
Address reuse remains widespread among retail users and certain automated exchange services, despite years of developer warnings.
Can Bitcoin holders fix this vulnerability?
Bitcoin holders can fix this vulnerability within minutes by broadcasting a standard transaction that transfers their entire balance to a modern, unused address.
Moving assets from a compromised or legacy script to a fresh native SegWit (p2wpkh) or Taproot (p2tr) address restores the hash protection layer. The new address exposes only a hash digest until the owner decides to spend the funds in the future.
The migration requires paying standard network transaction fees.
For active users, the fix is trivial. Anyone with working custody of their private keys can generate a new wallet descriptor and sweep their funds in a single transaction. Hardware wallet software and major custody providers already generate single-use addresses by default to prevent key reuse.
The real complication lies in dormant capital. Millions of exposed coins belong to lost wallets, deceased holders, or long-term cold storage setups where owners have deliberately avoided touching keys for over a decade. Those coins will sit exposed indefinitely.
Market Implications and Historical Parallels
Crypto markets have treated quantum computing as a theoretical problem relegated to distant decades, but hardware milestones keep shortening estimated timelines. Tech firms and research institutions continue to expand physical qubit counts and error-correction protocols.
Financial markets abhor unquantifiable systemic tail risks.
If an adversary developed a cryptographically relevant quantum computer in secret, the 7.12 million exposed Bitcoin would represent an enormous pool of potential liquidity that could be drained without warning. At prevailing valuations, that sum represents hundreds of billions of dollars in market capitalization.
A sudden, unauthorized sweep of Satoshi Nakamoto's addresses would trigger severe price volatility across every digital asset market. Traders have historically monitored early 2009-era addresses with extreme scrutiny. False alarms involving early wallets moving small amounts have repeatedly caused immediate, sharp drawdowns on spot exchanges.
Bitcoin core developers have addressed cryptographic transitions before. The network successfully upgraded from early script templates to p2pkh, activated Segregated Witness in 2017, and deployed Taproot in 2021 through consensus soft forks.
Upgrading the consensus layer to post-quantum signatures is technically feasible.
What comes next for Bitcoin security?
Bitcoin developer communities must eventually standardize and soft-fork a post-quantum signature scheme into the core consensus rules before quantum hardware reaches production scale.
The primary technical bottleneck is signature size. Quantum-resistant algorithms, such as lattice-based cryptography approved by standards bodies like NIST, require significantly larger signatures than the 64-byte Schnorr or ECDSA signatures used by Bitcoin today. Expanding signature sizes increases block bandwidth requirements and raises validation overhead for full nodes.
A contentious governance debate also looms over dormant addresses. If quantum computing arrives before inactive coins are moved, the community would face a stark dilemma: execute a soft fork that freezes unmigrated legacy outputs to protect the circulating economy, or allow those balances to be claimed by whoever constructs a quantum machine first.
Freezing balances contradicts Bitcoin's fundamental immutability ethos, creating an ideological conflict between preserving ledger history and defending market stability.
For now, security remains an operational choice for individual holders.
Wallets that retire legacy scripts and eliminate address reuse face zero immediate exposure. Network participants will monitor development mailing lists and research updates from analytics teams like Glassnode to track whether exposed balances decline as users modernize their storage architecture.
Mentioned in this article
Frequently asked questions
How does quantum computing threaten Bitcoin?
Quantum computers running Shor's algorithm can theoretically calculate private keys from known public keys. Addresses that have already published their public keys on the blockchain lose the security layer provided by elliptic curve cryptography.
Why can most Bitcoin holders fix this easily?
Active holders simply need to send their funds to a brand-new, modern address type like native SegWit or Taproot. This single transaction moves the assets behind a secure hash function, concealing the new public key until the next spend.
Why are Satoshi Nakamoto's coins uniquely vulnerable?
Nakamoto's estimated 1.1 million coins were mined in 2009 and 2010 using Pay-to-Public-Key scripts, which recorded raw public keys directly on-chain. Because the creator has been inactive since 2011, these balances cannot be migrated unless the private keys are used.
Comments(0)
No comments yet. Be the first to weigh in.