Supply audit method

BTC2 launch-supply audit.

BTC2Scan is building a reproducible audit of the launch/snapshot outputs. The page currently explains the method and status; final figures will be published only after the scanner, catch-up pass and API endpoints are connected.

Current audit status

Final figures are pending. The audit will report what was created at launch, what later moved on-chain, what remains unspent at the audited height, and which parts still need technical classification.

This page intentionally avoids final numbers until the launch-spend scanner, catch-up pass, address indexer and supply-audit API are connected.

Working formula estimated accessible supply = nominal supply − audited unspent launch-output estimate

FiguresPending connection

WordingEvidence-first, not absolute

Audit ruleEvery result must name its audit height

Audit height—Last block checked by the audit run.

Nominal supply—Total money supply reported by the node. This is not the final BTC2Scan audit result.

Accessible estimate—Will be calculated after the launch-output audit and address index are connected.

Unspent / potentially inaccessible launch supply—Placeholder: launch outputs still unspent at the audited height, pending final classification.

Audit scope

The audit follows launch/snapshot outputs, not every later reward or normal transaction.

BTC2 #102–#1,390 is the launch-output creation window. It is not a sample and it is not the whole audit. Those blocks are used to build the initial inventory; later blocks are scanned only to see whether those saved outputs were spent.

Professional audit sequence

The process is linear: define the source, build the inventory, scan spends, then classify the result.

Snapshot source

Eligibility snapshot: defines which Bitcoin balances were eligible for BTC2 at launch.

Build the launch inventory

BTC2Scan reads BTC2 #102–#1,390 and stores every original launch output as txid:vout plus amount and address context.

Scan later blocks

From the launch range onward, BTC2Scan checks transaction inputs. If an input references one of the saved txid:vout IDs, that launch output has been spent, even if the spend appears after the claim-hardening reference block.

Classify the evidence

A spent launch output is on-chain movement evidence. An unspent launch output is absence of spend evidence at the audited height. The explorer will not label outputs as permanently lost or burned without stronger proof.

Reference heights

These checkpoints have different meanings. BTC2Scan keeps them separate to avoid turning one technical reference into an unsupported conclusion.

BTCBitcoin Block #507,850

Eligibility snapshot: defines which Bitcoin balances were eligible for BTC2 at launch.

BTC2BTC2 Blocks #102–#1,390

Launch-output window: where the original BTC2 distribution outputs were written on the BTC2 chain.

BTC2BTC2 Block #628,729

Claim/import hardening reference: the old wallet path for using a Bitcoin private key to access snapshot BTC2 was restricted after this point. This is not automatically the same as proving every untouched output became unspendable by consensus.

BTC2BTC2 Block #654,929

Protocol reference: a later staking/protocol enforcement height visible in the public BTC2 code. Post-hardening spends must be classified against this context, especially if they are staking-related.

NOWAudit height

The last BTC2 block scanned in the current audit run. Final public numbers should always name this height.

What the final report will show

The public result will be presented as separated categories, not as one overloaded headline number.

Total launch/snapshot outputs and BTC2 amount.
Launch outputs moved before the claim-hardening reference.
Launch outputs moved after the claim-hardening and protocol-reference heights.
Launch outputs still unspent as of the audited height.

Why BTC2Scan uses careful wording

Unspent is evidence. “Lost forever” requires more proof.

The official claim path was hardened, but the blockchain audit must still follow evidence. Some launch outputs may move after the claim-hardening reference block, so BTC2Scan reports spend evidence, unspent status and audit height before using stronger labels like inaccessible.

BTC2Scan does

Find the original launch outputs in their real creation window.
Track those exact txid:vout IDs through later blocks.
Classify launch outputs by on-chain spend evidence and audit height.
Separate nominal supply, moved launch outputs, unspent launch outputs and pending classifications.

BTC2Scan does not

It does not use a small sample.
It does not assume the audit ends at BTC2 #628,729 or BTC2 #1,390.
It does not mix staking rewards with launch distribution.
It does not claim outputs are burned, lost forever or personally inaccessible without enough evidence.
It does not publish final accessible-rich-list figures until the address indexer and supply-audit endpoints are connected.