Bitcoin 2 ranks #237 of 484 cryptocurrencies. On a list that also counts tokens, memecoins, wrapped coins, staked derivatives and stablecoins it appears at #1860: 1623 of the 1859 assets ahead of it are not native coins but tokens or claims. A token is issued on a host blockchain rather than running its own; a claim stands for an asset already counted. Of the 2143 non-native assets CoinSpectrum lists above it by market cap, about 61% are tokens, 33% are claims on other assets, 5% are memecoins and 1% are NFT collections.
| CoinSpectrum Grade | pending — launch under review |
|---|---|
| Rank among cryptocurrencies | #237 |
| Rank counting claims | #1860 |
| Market capitalisation | $1M |
| Price | $0.0587 |
| Circulating supply | 18,488,779 BTC2 |
| Maximum supply | 21,000,000 BTC2 |
| Consensus family | Proof of Work |
| Consensus mechanism | SHA-256 (Bitcoin fork) |
| Own hashrate | — |
| Network purpose | Payments |
| Ledger type | Single-asset ledger |
| Launch distribution | No premine |
Market figures from the 10 November 2026 build. Open the live view for every exchange's price, and charts.
Grade pending. Fewer than six of Bitcoin 2's nine network-security points are measured yet. A grade is not given until it is, so that a coin is never rated higher for what is not yet known.
| Section and criteria | Score | Basis |
|---|---|---|
| Consensus | 10 | average of 2 criteria |
| By leader (its largest chain's market cap) (Source) | 10 | Proof of work: 10 of 10 on the ladder of consensus families ranked by their largest chain's market cap |
| By family (all its chains' market cap) (Source) | 10 | Proof of work: 10 of 10 on the ladder of families ranked by the combined market cap of their chains |
| Supply | 10 | fixed maximum supply of 21 million |
| Distribution | 10 | average of 3 parts |
| Holder concentration (Source) | – | Not yet measured |
| Active addresses | – | Not yet measured |
| Premine (allocated at launch) | 10 | 0% of today's supply allocated at launch to founders, a company, a foundation or investors. No developer allocation is documented: the chain started (mainnet early 2018) from a 1:1 snapshot of Bitcoin balances at BTC block 507,850, 16,848,064.795 BTC2, and everything since has been minted by stakers and masternodes. The snapshot is a fork airdrop to all BTC holders, not an insider grant. source |
| Fundraising (share sold) (Source) | 10 | No sale of the coin source |
| Developer share (after launch) | 10 | No developer share: every new coin goes to the miners or validators who produce blocks. Each block's 0.2 BTC2 goes 3/4 to the staker and 1/4 to a masternode; no developer or treasury share. source |
| Decentralisation | 3.3 | average of 3 parts |
| Governance (Source) | 0 | An authority can halt the chain or freeze funds: From June 2019 the team made unclaimed snapshot balances unspendable ('the unclaimed balances cannot be spent'), a protocol-level freeze of coins belonging to BTC holders who had not yet claimed. source |
| No central team (Source) | 0 | A central team directs it: An anonymous 'Bitcoin 2 Team' controls the BITC2/bitcoin2 repository (MIT licence), the spork keys and the protocol changes, including the 2019 rule that froze unclaimed snapshot balances. source |
| Who can mint (Source) | 10 | Open to anyone with hardware: anyone can produce blocks by mining, no permission needed |
| Nodes (Source) | – | Not yet counted |
| Security | — | 2.3 of 3 points, 5 not yet measured source |
| Pool diversity (Largest pool 50% 0 to 20% 10, largest three 90% 0 to 50% 10; 2 points) | – | |
| Network activity (Transactions a day, 250 0, 500,000 or more 10; 2 points) | – | |
| Hashrate (Own work 5, its power 1 kW 0 to 10 GW 5; 1 point) | – | |
| Clients (Separate code and teams 10, separate code or teams 9, a fork by the same team or a stale second 8; one client: a new version within 12 months 7, 24 months 6, none in 24 months 5, none in 48 months 3; a second in development +0.5, a second seen running +1, 8 at most with one client; chain ended 0; 1 point) | 3 | one client, no new version in 48 months (latest Jun 2021) |
| Open source (Node software) | ✓ | |
| No 51% attack (Nor a deep reorganisation, five years) | ✓ | |
| Scalability | — | too few measures yet source |
| Fees ($0.001 or less 10, $1 or more 0) | – | not yet measured |
| Throughput (2,478 a second, the busiest network's peak day, 10; 121, the median of the ten busiest, 5) | – | not yet measured |
| Block time (10 minutes 10, less either side) | 10 | a block every 10 minutes |
| Block space per 10 minutes (24 MB or more 10: the ten busiest networks' median demand, 16.4 MB, and half again for growth) | – | not yet measured |
| Features (3 checks) | 3.3 | 1 of 3 passed |
| Fast payments (Safe to accept within seconds · Whitepaper abstract, §1, §2 and §11) | ✓ | SwiftTX masternode transaction locks (PIVX/Dash InstantSend design) are documented as live; the PIVX-era node also relays first-seen with no replace-by-fee. Whether SwiftTX is still enabled by spork could not be verified. |
| Pruned nodes (Old history dropped, every rule checked · Whitepaper §7) | ✗ | Bitcoin 2 2.3.1b has no -prune option. |
| Light clients (Payments verified from headers · Whitepaper §8) | ✗ | Bitcoin 2 (PIVX-derived) is proof of stake, so Bitcoin-style SPV cannot check the stake behind its headers, and no shipped light client verifies it; light wallets trust a server. |
| Privacy | 7 | 7 of 10: whitepaper privacy 7 of 7, extra features 0 of 3, 1 not yet researched source |
| Protocol level privacy (Keys not tied to an identity · Whitepaper §10) | 10 | Addresses are hashes of keys users generate themselves; the node checks scripts and signatures, with no identity condition in its consensus rules. |
| UTXO ledger (Separate outputs, change to a new address · Whitepaper §2, §9) | 10 | Coins are separate unspent outputs: a payment spends whole outputs and sends the change to a new address, so the coins in one wallet need not share a history. |
| HD addresses (A new address for each payment, unlinked · Whitepaper §10) | – | |
| Hidden amounts (Amounts confidential) | 0 | zBTC2 (Zerocoin) is disabled; ordinary transfers are transparent. |
| Hidden parties (Sender and receiver hidden) | 0 | zBTC2 is disabled "while a new privacy protocol is being worked on". |
| Network privacy (Origin hidden by default) | 0 | Bitcoin-derived node relays its own transactions over clearnet by default; Tor (-proxy/-onion) needs user setup and there is no Dandelion. |
| Programmability | 1.1 | 1 of 9 points source |
| Token issuance | 0 | No token issuance on the chain itself |
| Smart contracts (Scripting for spending conditions) | 1 | Bitcoin-derived Script (PIVX-style zerocoin codebase) with spending conditions only. |
| Multisig and time locks (Without a third party) | ✗ | OP_CHECKMULTISIG is present, but OP_NOP2/OP_NOP3 stay no-ops in its interpreter (no CHECKLOCKTIMEVERIFY or CHECKSEQUENCEVERIFY), so outputs cannot carry time-locked spending conditions. |
| Atomic swaps (With other chains) | ✗ | Without CLTV/CSV no script refund path can be time-locked, so an HTLC cannot be expressed in an output. |
| Native DEX (Trades the coin itself, not a claim) | ✗ | No DEX found trading the coin itself: none on its own chain (DefiLlama), and not on THORChain, Maya, Chainflip, Komodo DeFi, BasicSwap, Bisq or Haveno (checked 2026-11-04). |
| Cross-chain messaging (Verified by the chain itself) | ✗ | No cross-chain feature in the protocol. |
| NFTs (Carried by the chain's rules) | ✗ | No token or NFT type in the protocol. |
| Demand | 1.8 | average of 4 measures |
| Exchanges (10 or more: 10) | – | exchanges not yet counted |
| Daily volume ($10K 0, $1B or more 10) | 0 | $10,195 traded in 24 hours; #2505 by volume |
| Turnover (volume ÷ market cap, 5% a day: 10) | 6.2 | 0.94% of its market cap a day |
| Order-book depth (±2% of the price ÷ market cap, 1%: 10) | – | no order book on the nine exchanges read |
| Market cap ($1M 0, $10B or more 10) | 0.1 | $1.1M, 0.1 on a scale of 2.5 points per tenfold |
| Paper trading (futures, options and margin ÷ market cap, 0%: 10, 100%: 0) | – | not measured |
| Wallet support (wallets that hold it, 10 or more: 10) | 1 | its own node and wallet, counted as 1: no wallet in the site's directory lists it yet |
| Record | 5.7 | average of 3 criteria |
| Age (years since genesis) (Source) | 7 | 7 full years since 2019-05-28, the first day with a recorded price (genesis not yet researched, so the age can only be understated). |
| Development (work, fixes, vulnerabilities) | 0 | 1 positive, 2 negative, 4 not yet researched source |
| Positive | ||
| Steady work, 0.5 of 6 | ✓ | 1 commit in 1 of the last 12 months (github.com/BITC2/bitcoin2); Last release 2.3.1b, 2021-06-29; no release in the last 24 months. |
| Negative | ||
| Unfixed vulnerability, disclosed 2024-07-03, −1 | ✗ | CVE-2020-14198: misbehaving peers are auto-banned into an unbounded ban list, so many attacker addresses can exhaust CPU and memory; still in Bitcoin 2 2.3.1b. bitcoincore.org github.com github.com |
| Unfixed vulnerability, disclosed 2024-07-31, −1 | ✗ | CVE-2024-52919: addr-message spam can overflow the address manager's 32-bit id counter and crash the node, with no addr rate limit; still in Bitcoin 2 2.3.1b. bitcoincore.org github.com |
| Not yet researched | ||
| Shipped a security fix in two years | – | |
| Shipped a privacy improvement in two years | – | |
| Shipped a scaling upgrade in two years | – | |
| Shipped a new capability for users in two years | – | |
| Conduct (origin, claims, halts) | 10 | 3 positive, 0 negative source |
| Positive record | ||
| Launched with a stated purpose, not as a joke | ✓ | |
| No claims by its founders that contradict its own design | ✓ | |
| No halt, freeze or reversal in five years | ✓ | |
Ten sections, weighted equally, each 0 to 10: consensus (the two ladders), supply (the supply scale and a fixed cap that holds), distribution (premine, fundraising, developer share, holders), decentralisation (governance, no central team, who can mint, nodes), security, scalability, privacy, programmability (what the scripting layer can do beyond the whitepaper's payment system), demand, and record (age, development, conduct). They are built from the criteria in the second table: privacy, scalability, security and decentralisation are the Cryptocurrency Standards among them, as follows: privacy (the whitepaper's three checks a base of 7 of 10, three extra features up to 3 more), scalability (four measures and three features), security (pool diversity, network activity, hashrate, clients and two checks) and decentralisation (governance, no central team, who can mint, nodes, holders, premine, fundraising and developer share); programmability (token issuance, smart contracts and five checks) follows them, and supply and demand are two: the supply, scored against 21 million, and demand, the average of seven measures of the market and the wallets. Provisional: parts marked — are not yet measured and are left out of the average. A rating of structure and market depth, not a price forecast or investment advice. How the grade is built · Highest-graded cryptocurrencies.
18,488,779 of a maximum 21,000,000 BTC2 are in circulation — 88.0% of the total that will ever exist.
| Premine (allocated at launch) | 0% of today's supply |
|---|---|
| Sold by the issuer or insiders | 0% of today's supply |
| Developer share received since launch | 0% of today's supply |
| Developer share of new coins today | 0% |
| Fundraising | No sale and no investor round |
No developer allocation is documented: the chain started (mainnet early 2018) from a 1:1 snapshot of Bitcoin balances at BTC block 507,850, 16,848,064.795 BTC2, and everything since has been minted by stakers and masternodes. The snapshot is a fork airdrop to all BTC holders, not an insider grant.
No ICO or presale is mentioned in the BitcoinTalk ANN or on bitc2.org.
No sale of BTC2 by the team is documented.
Each block's 0.2 BTC2 goes 3/4 to the staker and 1/4 to a masternode; no developer or treasury share.
Bitcoin 2 (bitc2.org, CMC id 3974) is proof of stake with masternodes, not SHA-256 proof of work as the input says; it may not belong in the PoW set. A separate, unrelated 2024 project at btc2.lol also calls itself 'Bitcoin 2' (EVM fork at BTC block 839,999); the data here is for the bitc2.org chain. The snapshot froze unclaimed coins (2019, before the record window). clients is 0 because the only client's last release (2.3.1b, June 2021) is older than 24 months.
Sources: bitc2.org · bitc2.org · bitc2.org · bitc2.org · github.com. Researched 2026-10-26, medium confidence.
No source we can reach publishes a hashrate for Bitcoin 2.
No SEC/CFTC determination — unclassified.
The regulator's position, reported as stated, not CoinSpectrum's. Assets nobody has ruled on are left unclassified rather than sorted by a guess.
Bitcoin 2 is #237 among cryptocurrencies and #1860 in the market ranking, which lists wrapped coins, staked derivatives, stablecoins and tokens alongside them. CoinSpectrum counts an asset once, and counts only cryptocurrencies: assets with their own blockchain and their own consensus. A wrapped coin, a staked derivative or a stablecoin is a claim on something already counted; a token, memecoin or otherwise, runs on another chain's blocks. All of them are listed, each in its own section, and none is added to the total. The 1623 places between Bitcoin 2's two ranks are held by claims and tokens, not by other networks. The methodology sets out the rule and the counting rule argues for it.
The price above is the median of the exchanges the site reads live, checked every minute and cross-checked against a market snapshot (how market data is gathered). The grade is scored on published criteria, each with its source (the method). The site is independent, nothing on it is a paid placement, and its statements are signed (about CoinSpectrum, the manifesto).