Glassnode Flags 7.12 Million Bitcoin With Exposed Public Keys: What Quantum Risk Means

Bitcoin quantum risk is back in focus after Glassnode reported that 7.12 million BTC, or 35.4% of issued supply, sits behind public keys already visible on-chain. The number is striking. What it measures is more specific than a claim that a third of Bitcoin has been hacked or can be stolen with today’s machines.

The fresh November 10 data puts a measurable scale on a future cryptographic concern. It also highlights a practical difference between exposure built into an address type and exposure created by how wallets reuse addresses.

In its November 10 update, Glassnode said 25.8% of supply was exposed through address reuse, including 11.6% on exchanges. The exchange figure sits within the reuse category. Adding those percentages together would double-count coins.

“Moving those coins to a fresh address ends this exposure,” the firm wrote, referring to the reuse-related problem. That statement is not a guarantee that any new address format protects against every future quantum attack.

Glassnode’s original methodology, published in May, put visible-key exposure at 30.2% of issued supply, or 6.04 million BTC. The November reading is 5.2 percentage points higher. That comparison describes a change in measured exposure, not a demonstrated increase in the capabilities of quantum computers.

A private key authorises a Bitcoin transaction. Its corresponding public key lets the network verify a signature. Under the cryptographic assumptions used today, knowing a public key does not make deriving its private key computationally practical.

The concern is a sufficiently capable quantum computer applying a different mathematical approach to recover private keys from public keys. Glassnode’s framework asks which coins already have the necessary public information visible while they remain unspent.

Its methodology calls this exposure at rest. That is different from a public key becoming visible when the owner broadcasts a spending transaction. The latter creates a shorter window in which an attacker would have to act.

The distinction explains why a large exposed balance does not establish an attack timeline. A map of potential targets and proof of a machine able to attack them are different kinds of evidence. The latest dataset supplies the former, not the latter.

Glassnode separates structural exposure from operational exposure. Some output types reveal keys by design; others can conceal them until spending. Reusing a key after it has been revealed can leave remaining or future funds associated with information already recorded on the blockchain.

For a custodian, that makes the topic partly about wallet management. An organisation can have strong controls against password theft and unauthorised withdrawals while still wanting a separate inventory of which outputs have visible public keys.

Those controls address different threats. A public-key exposure metric should not be used on its own to declare an exchange insolvent, compromised or unsafe in every respect. Nor should a low measured exposure be treated as a complete security audit.

The useful question for a service provider is whether it understands its address types and transaction history, and can explain how it plans to manage future cryptographic changes. This is a more concrete discussion than asking whether a company is simply for or against quantum preparedness.

One approach appears in BIP 360, a draft Bitcoin Improvement Proposal for Pay-to-Merkle-Root outputs. It aims to reduce long-duration public-key exposure while preserving script-tree functionality. It is not an activated network upgrade.

The authors separate long-exposure attacks from faster attacks attempted while a transaction waits for confirmation. They say fuller protection against the latter may require post-quantum signatures. A mechanism that hides a public key for longer should therefore not be described as a complete replacement for quantum-resistant signing.

That distinction matters when evaluating claims that Bitcoin has already fixed the problem. Publishing a proposal is one step. Reviewing the design, reaching agreement, implementing it and persuading holders to use any eventual change are separate challenges.

The draft itself acknowledges uncertainty about when or whether cryptographically relevant quantum computers will become viable. It offers a possible way to prepare without providing a countdown to a proven attack.

Changes affecting widely held digital money involve coordination as well as cryptography. Wallet developers, custodians and holders need compatible tools and clear information. Dormant holdings raise additional questions because an inactive owner cannot be assumed to participate in a future migration.

BNC’s coverage of Strategy’s Bitcoin treasury and capital allocation shows how material BTC balances have become for corporate investors. For such holders, long-term custody planning belongs alongside financing and asset-management decisions.

The new Glassnode figures give that planning a more precise starting point. They identify a large stock of coins with visible keys and show why address reuse deserves attention. They do not establish that those coins have been stolen, that an attack is imminent or that Bitcoin’s price must move in a particular direction.

The next meaningful evidence would be improved exposure reporting, progress on reviewed technical proposals and independently demonstrated advances in relevant quantum capabilities. Until then, the strongest interpretation is preparedness: a clearer map of the potential problem, with substantial work still ahead.