Loading prices…
🩸BEARISH

Bitcoin Census Flags 7.16M BTC in Quantum Risk Study

The tally identifies visible keys and script matches, but assessing quantum exposure requires checking individual spending paths.

Bitcoin Census Flags 7.16M BTC in Quantum Risk Study
Bitcoin Census Flags 7.16M BTC in Quantum Risk Study

A Bitcoin census published Nov. 18 linked 7.16 million BTC to public keys or scripts already visible on-chain, representing 35.6% of bitcoin in unspent outputs at block 975,019. Researcher duncan0k counted 7,164,754 BTC out of 20,109,207 BTC in those outputs, combining directly visible key data with matches to historical blockchain records.

Why it matters

About 1.94 million BTC qualified because their output formats contain key data by design, including pay-to-public-key, Taproot and bare multisig outputs. The remaining 5.23 million BTC, roughly 73% of the tally, came from matching hashes to older on-chain data.

That second group included about 1.93 million BTC in script-hash formats. A script match can reveal spending instructions, but it does not by itself establish that a usable public key is exposed: some spending paths require no signature. The distinction matters if future quantum computers become capable of breaking Bitcoin's current signatures.

Market impact

The census is a starting point for assessing a future quantum migration, not a count of coins proven vulnerable to an existing attack. Researchers would need to examine matched outputs and determine which spending paths depend on visible, usable keys.

A May Glassnode study counted 6.04 million BTC using a different test and denominator: visibility of the public key needed for a spend, measured against issued supply. The two results cannot be used directly to measure a change over time.

Related tokens
$BTC

Frequently asked questions

  1. What share of unspent bitcoin did the census identify?

    The census linked 7,164,754 BTC to visible keys or scripts, representing 35.6% of the 20,109,207 BTC in unspent outputs at block 975,019.

  2. How did historical blockchain matches affect the tally?

    About 5.23 million BTC, roughly 73% of the total, came from matching hashes in unspent outputs to older on-chain data.

  3. Does a script-hash match prove that bitcoin is vulnerable?

    No. A script match can reveal spending instructions, but researchers must check whether a spending path depends on a visible, usable public key. Some paths require no signature.

  4. Which output formats expose key data by design?

    The census counted pay-to-public-key, Taproot and bare multisig outputs among formats that contain key data in the output itself. About 1.94 million BTC qualified by format alone.

  5. Why can't the census be directly compared with Glassnode's May study?

    Glassnode used visibility of the public key needed for a spend and measured against issued supply. The November census also includes script matches and uses bitcoin in unspent outputs as its denominator.

Source attribution
Aggregated from CryptoSlate · Verified · Last refreshed 7h ago
Open original →