BTC2Scan
—Supply audit
BTC2 supply audit, explained.
A public, evidence-first view of BTC2 nominal supply, launch supply, moved launch outputs and the estimated accessible supply.
Current audit view
BTC2Scan separates the live nominal supply from the launch outputs that still have no spend evidence at the audited height.
The result is an explorer-side analytical view. It helps users review supply transparency without making unsupported claims about coins being burned, lost forever or personally inaccessible.
Main formula
accessible estimate = launch supply moved on-chain + post-launch reward supply
Live chain dataNominal supply follows the current BTC2 chain.
Launch auditUnspent launch outputs are tied to an audited block height.
Careful wordingUnspent means no spend evidence, not an absolute loss claim.
Verification manifest
Public audit manifest
Open the read-only JSON manifest with the current audited height, accessible indexed supply and stable SHA256 result hash.
Launch-output movement monitor
Audited launch-output movement tracker
BTC2Scan compares the public baseline against the latest audited unspent launch-output snapshot. This is explorer-level analysis, not a consensus rule or identity claim.
Checking monitor…
Movement history0
No post-baseline launch-output movement recorded, including coinstake spends.
How the audit works
BTC2Scan separates the audit method from the reference heights, so users can see what is measured and why.
Identify launch outputs
BTC2Scan builds an inventory of the original launch outputs, including their txid:vout IDs, amounts and address context.
Track exact spends
Later transaction inputs are matched against those saved txid:vout IDs. Any chain-accepted match is treated as public movement evidence, including coinstake spends if observed.
Separate supply sources
The accessible-supply estimate combines launch supply that has moved on-chain, including coinstake movement if observed, with BTC2 created later by normal network rewards.
Publish careful categories
Still-unspent launch outputs remain in a separate audit category. The category is not a personal wallet check; it reflects that BTC2Scan has not seen a valid chain-accepted movement for those outputs.
How BTC2Scan defines the supply audit.
- The audit separates indexed UTXO supply, unspent launch outputs and the resulting accessible indexed supply estimate.
- A launch output is reclassified only when BTC2Scan observes a valid chain-accepted spend of the exact txid:vout through the audited height, including coinstake movement if observed.
- BTC2Scan does not identify ownership, does not prove permanent loss and does not turn the accessible estimate into a consensus rule.
- The public manifest exposes the audited height, audited block hash, result fields and a stable SHA256 hash for the audit snapshot.
accessible indexed supply = indexed UTXO supply − unspent launch outputs
Audit reference points
These reference points explain why BTC2Scan treats untouched launch outputs conservatively. They are context for the audit, not a user claim guide.
BTCBitcoin Block #507,850
The Bitcoin snapshot block used to determine which Bitcoin balances were eligible for the original BTC2 launch distribution.
BTC2BTC2 Blocks #102–#1,390
The BTC2 block range where the original launch outputs were recorded. BTC2Scan tracks these exact outputs through later chain history.
BTC2BTC2 Block #628,729
Claim/import hardening reference: after this point, the old Bitcoin-key import path is no longer treated as a normal way to access untouched launch balances. BTC2Scan keeps those outputs in the unspent launch category unless the chain later accepts a movement.
BTC2BTC2 Block #654,929
Protocol/staking reference: a later network-rule context point. It does not reopen normal launch claiming. BTC2Scan treats old untouched launch outputs as not normally claimable and only reclassifies an output if valid on-chain movement is observed.
NOWAudit height
The most recent BTC2 block included in the current supply-audit snapshot. Public figures should be read as evidence through this height.
FAQ
A simpler explanation for users who are new to Bitcoin 2 or to BTC2Scan’s supply audit.
What is Bitcoin 2 (BTC2)?
Bitcoin 2, or BTC2, is an independent Bitcoin-based blockchain and cryptocurrency. The original project describes it as a community-centric network focused on speed, scalability, decentralization and privacy-oriented features, using a custom Proof of Stake design and masternodes. BTC2 initially mirrored eligible Bitcoin balances at Bitcoin block #507,850 on a 1:1 basis, and later supply is created through normal BTC2 network rewards until the 21 million BTC2 cap. For the original project’s official website, visit bitc2.org.
What is BTC2Scan’s supply audit?
It is an explorer-side analysis that separates live nominal supply from launch outputs that still have no spend evidence. The goal is to make BTC2 supply easier to review with public blockchain evidence.
What was the BTC2 launch supply?
BTC2 launch supply refers to the initial BTC2 recorded from the Bitcoin snapshot distribution. BTC2Scan tracks those original launch outputs separately from BTC2 created later by normal network rewards.
What does “launch supply already moved” mean?
It means a launch output was later used as an input in a chain-accepted BTC2 transaction. That includes coinstake if observed, so BTC2Scan treats that part of launch supply as moved for the accessible-supply view.
What does “unspent / potentially inaccessible launch supply” mean?
It means BTC2Scan has not found spend evidence for those launch outputs through the audited block height. The wording is careful because BTC2Scan is reporting an audit category: old untouched launch outputs are not treated as normally accessible, but BTC2Scan still classifies them by chain evidence rather than by personal wallet assumptions.
Can an old untouched launch address still claim or spend BTC2?
For ordinary user claiming, no. The official Bitcoin 2 FAQ says unclaimed fork balances can no longer be spent through the old Bitcoin-key import path. BTC2Scan therefore keeps still-unspent launch outputs outside the accessible estimate unless the exact launch txid:vout is later observed moving in a valid chain-accepted transaction, including coinstake if observed.
Does unspent mean burned or lost forever?
No. Unspent means no spend evidence at the audited height. BTC2Scan avoids stronger labels such as burned or lost forever unless the public chain evidence can support them.
Why can accessible supply increase over time?
Accessible supply can increase because new BTC2 is created by normal network rewards. It can also change if an old launch output that was previously unspent later moves on-chain and is reclassified by the audit.
Is this a consensus rule?
BTC2Scan does not create consensus rules. It publishes an explorer-side classification based on the rules and evidence visible on the BTC2 chain. The accessible view reflects that by excluding still-unspent launch outputs until valid on-chain movement is observed.
What does “audited through block X” mean?
It means the supply-audit snapshot includes chain data up to that BTC2 block. Later blocks may change live nominal supply, and future audit refreshes may update the launch-output classification.
Does BTC2Scan track staking and masternode rewards?
Yes. BTC2Scan’s rewards analysis is based on the original project’s official block reward schedule, published in the official Bitcoin 2 block rewards table. BTC2Scan identifies detected staking and masternode reward events from indexed on-chain data and presents them separately from normal transfer activity.
This is an explorer-level analysis. It does not change consensus rules, wallet balances, or the launch-supply audit. Reward records are shown as transparent on-chain evidence so users can review detected staking and masternode activity by block, transaction, or address.
Historical reward notes
During the historical rewards audit, BTC2Scan kept two early-chain records visible with schedule notes instead of manually forcing them to match the expected schedule view:
- Block 18,730: the official schedule view expects 0.80000000 BTC2 total reward for this epoch, split as 0.60000000 BTC2 staking and 0.20000000 BTC2 masternode. The decoded on-chain reward for this block is 0.85000000 BTC2, split as 0.65000000 BTC2 staking and 0.20000000 BTC2 masternode.
- Block 624,035: the official schedule view expects 0.80000000 BTC2 total reward, normally shown as 0.60000000 BTC2 staking and 0.20000000 BTC2 masternode. BTC2Scan detects the reward as a same-address staking return and does not identify a separate masternode payout, so it keeps the record visible with a schedule note instead of assigning a masternode reward that is not separately identified in the decoded on-chain data.
These notes are included for auditability. They do not indicate a wallet-balance issue, and BTC2Scan does not hide or manually adjust historical records to make them appear cleaner than the underlying chain data.
Is BTC2Scan affiliated with bitc2.org or the original Bitcoin 2 creators?
No. BTC2Scan is an independent community-built explorer for the Bitcoin 2 blockchain. It is not affiliated with bitc2.org or the original Bitcoin 2 creators. References to Bitcoin 2, BTC2 or bitc2.org are used only to identify the network that BTC2Scan indexes.
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 indexed supply, moved launch outputs, unspent launch outputs and accessible-supply estimates.
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 override BTC2 network rules or present the accessible-balance view as a new consensus rule.