Bitcoin census links 7.16M BTC to public keys or scripts

Bybit
Film negatives fan across a bright yellow-green lightbox with a Bitcoin badge, fading into plum shadow on the left.
Coinmama



A Bitcoin census published Nov. 18 linked 7.16 million unspent BTC to public keys or scripts already visible on-chain. It counted some outputs because they contain key data by design and others because their hashes matched tables built from earlier on-chain data. Together they accounted for 35.6% of the BTC in unspent outputs at block 975,019.

Researcher duncan0k published the census on Delving Bitcoin, tallying 7,164,754 BTC out of 20,109,207 BTC in unspent outputs. About 1.94 million BTC qualified by format alone, across pay-to-public-key, Taproot and bare multisig outputs. Those formats put key data in the output itself. The census counted them in full, including a small amount in outputs that failed its key validity check.

The other 5.23 million BTC, about 73% of the tally, came from matching hashes in unspent outputs to older blockchain data. About 3.30 million BTC of that sat in two formats that use a hash of a public key. Another 1.93 million BTC sat in two script-hash formats, which record a fingerprint of the instructions for spending the coins.

A match in a script-hash format can reflect script or key data. Spending conditions determine which keys and signatures matter.

The tally classifies outputs by format or table membership. The format subtotal includes a small balance that failed the scan’s key validity check.

What the Bitcoin census counts as a script match

A script-hash match is a clue to how the coins can be spent. When it identifies a revealed script, a reviewer can check which signatures a spending path requires and whether the corresponding public keys are already visible. Some paths require no signature at all. Those distinctions matter if future quantum computers become capable of breaking the signatures Bitcoin uses today.

okex

The Catalyst

Know what’s moving crypto.

The extraction rules describe two ways the scan counted script-hash balances. A pay-to-script-hash output can match a previously revealed script or an entry derived from a known public key. The other script-hash format uses a separate table that also includes some hashes derived from Taproot script data.

The researcher compared those rules with draft BIP 362, a proposal to classify exposure in existing Bitcoin outputs. Compared with the draft version reviewed, the scan skipped some revealed scripts and included some broader matches. The net effect is unmeasured. Keys or scripts behind outputs outside the tally could still have been disclosed off-chain or in on-chain locations the scan skipped.

Glassnode’s May study measured a different kind of visibility. It reported 6.04 million BTC, or 30.2% of issued supply, using visibility of the public key needed for a spend as its test. The November census includes script matches and divides by BTC in unspent outputs. Measuring a change over time would require a common definition and denominator.

Related Reading

Bitcoin exchanges can reduce quantum exposure before a network upgrade

To turn the new census into priorities for a future migration, researchers would need to examine the matched outputs and identify where a spending path depends on a visible, usable key.



Source link

fiverr

Be the first to comment

Leave a Reply

Your email address will not be published.


*