Bitcoin (BTC): The Original Proof-of-Work Settlement Layer
Bitcoin is not a smart-contract platform — it is a SHA-256 proof-of-work settlement network with a non-Turing-complete Script VM, ~600-second blocks, and ~3,600-second (6-confirmation) economic finality. Launched 2009-01-03 by Satoshi Nakamoto, it carries a $4,031,417,793 on-chain TVL today, anchored not in DeFi yields but in a hard 21M supply cap and the most-secured PoW chain in existence. Every other chain on AllSwap is, in some sense, defined against Bitcoin's design choices.
This page is the chain-level view of Bitcoin — the network itself, not a swap tutorial. Bitcoin's defining trade-off is intentional minimalism: 7 typical TPS (theoretical max ~15), 10-minute average block time, and 60-minute (6-block) finality buys you the highest hash-rate security and the longest uninterrupted chain in crypto. That trade-off is why Bitcoin has had zero protocol-bug-driven consensus rollbacks since 2010 (the only notable exception being the March 2013 v0.7/v0.8 LevelDB chain split, resolved by miner coordination within hours), while peers in our 'Bitcoin 系' category (DOGE, LTC, BCH, DASH) all chose to relax block-time or block-size parameters for higher throughput. The ecosystem around BTC has migrated upward: $6.99B sits in WBTC (multi-sig custodied wrapper, post-2024 joint custody) and $4.17B in Binance Bitcoin (BTCB) — meaning more BTC is productive off-chain in DeFi wrappers than on Bitcoin L1 itself. The native L1 hosts Lightning Network ($298M TVL) for payments, Babylon Protocol ($3.14B) for BTC restaking, and the post-Taproot Ordinals/Runes/BRC-20 layer for asset issuance. If you are a developer evaluating Bitcoin, a researcher comparing PoW vs PoS finality, or a user wanting to acquire native BTC via non-custodial cross-chain swap from another network, this page gives you the chain-level facts — consensus, throughput, top protocols by TVL, peer comparison, and 17 years of upgrade and incident history.
About Bitcoin
Bitcoin's genesis block was mined by Satoshi Nakamoto on 2009-01-03, embedding the now-famous Times headline 'Chancellor on brink of second bailout for banks' into the coinbase transaction. That timestamp is the start date for every chain on AllSwap's comparison table — Ethereum launched 6.5 years later, Solana 11 years later, Monad 16+ years later. Bitcoin is the longest continuously-operating blockchain in production, and its 17-year uptime record (with the 2010 value-overflow patch and the brief March 2013 v0.7/v0.8 chain split as the only consensus-layer exceptions, both resolved within hours) is the empirical baseline against which every newer chain's stability claims are measured. The network has no foundation, no CEO, no on-chain governance — protocol changes ship through BIPs adopted by miner signaling and node-operator consensus.
Consensus is SHA-256 proof-of-work under the Nakamoto longest-chain rule, with a difficulty adjustment every 2,016 blocks (~2 weeks) targeting the 600-second block interval. The VM is Bitcoin Script — deliberately non-Turing-complete, with no loops, no general-purpose state, and a strict witness-stack model. That design choice is the reason Bitcoin cannot host Uniswap-style AMMs or Aave-style lending natively, and it is also the reason Bitcoin has zero smart-contract exploit history at the L1 layer. Asset issuance on Bitcoin today happens through three non-native protocols layered on top of Script: Ordinals (inscriptions on individual satoshis), BRC-20 (a JSON-encoded token standard via inscriptions), and Runes (a UTXO-native fungible token protocol launched alongside the 2024 halving).
Technical anchor points: 10-minute average block time, 7 transactions per second typical throughput, ~15 TPS theoretical maximum, and 6-block (~3,600-second) probabilistic finality — the threshold at which a reorg becomes economically irrational given current hash rate. These numbers are an order of magnitude slower than every other category on AllSwap (high-speed L1s post sub-second finality; EVM L2s post sub-second block times) and that is the explicit design intent. The 21M-coin hard cap, enforced by a halving schedule that cut block rewards from 50 BTC (2009) to 25 (2012) to 12.5 (2016) to 6.25 (2020) to 3.125 BTC after 2024-04-19, makes BTC the only major asset on AllSwap with a mathematically provable terminal supply.
Address formats reflect upgrade history: legacy Base58Check P2PKH addresses begin with '1', P2SH multisig with '3', SegWit Bech32 with 'bc1q', and Taproot Bech32m with 'bc1p'. Wallet support is broader than any other chain in our index — Electrum and Sparrow for desktop, BlueWallet and Xverse for mobile, Ledger and Trezor for hardware, and Unisat for Ordinals/Runes/BRC-20 management. The economic design is unique: there is no foundation treasury, no pre-mine, no validator token rewards — miner revenue comes entirely from block subsidy plus transaction fees, with the subsidy programmatically trending toward zero by approximately 2140.
Bitcoin technical parameters
Bitcoin's technical profile is unlike anything else in our chain index. Where Ethereum runs a Turing-complete EVM with Gasper finality at 768 seconds, and Solana runs PoH + Tower BFT at 12.8-second finality, Bitcoin runs the original Nakamoto consensus: SHA-256 proof-of-work with no validator set, no slashing, and no signed finality gadget. Security comes from cumulative work, not staked capital. The deliberate constraints — non-Turing-complete VM, 10-minute blocks, 1MB base block weight (4MB with witness data post-SegWit) — are features, not bugs.
| Consensus | PoW (SHA-256, Nakamoto consensus) |
|---|---|
| VM | Bitcoin Script (non-Turing complete) |
| Block time | 10 min |
| Finality | 1 h |
| TPS | 7 typical / 15 max |
| Gas token | BTC |
| Launched | 2009-01-03 |
| Token standard | UTXO (BRC-20 / Runes / Ordinals — non-native) |
| Address | Base58Check (P2PKH/P2SH) / Bech32 (SegWit) / Bech32m (Taproot) |
Consensus mechanism
Proof-of-work means miners burn real-world energy to solve a SHA-256 hash puzzle below a network-set difficulty target. The first miner to find a valid block broadcasts it; nodes verify and extend the chain. There is no committee vote, no leader election, no BFT round — just whichever chain has the most accumulated proof-of-work wins. This is called Nakamoto consensus, and its security model is economic: to reverse a 6-block-deep transaction, an attacker must out-hash the honest network for the duration of the reorg. With Bitcoin's current hash rate, that cost is in the hundreds of millions of dollars per hour, making 6-confirmation transactions effectively final. The trade-off: no instant finality. A block is only probabilistically final — 1 confirmation is ~99% safe for small amounts, 6 confirmations (~60 minutes) is the conventional threshold for large settlement. Compared to Avalanche Snowman (1.5s finality) or Hyperliquid L1 (0.07s), Bitcoin is three to four orders of magnitude slower — but it requires no validator set you have to trust, no slashing logic that could brick under edge cases, and no liveness assumption beyond honest miners holding majority hash rate.
Performance context
7 TPS sounds catastrophically low next to Solana's 3,000 typical or Hyperliquid's 200,000 max — and at the L1 base layer, it is. But Bitcoin's throughput strategy was never to win base-layer TPS races; it was to keep base-layer state minimal and push throughput to L2. Lightning Network ($298M TVL in our data) offloads micropayments to off-chain payment channels with on-chain settlement only at channel open/close, theoretically supporting millions of TPS in aggregate. Babylon Protocol ($3.14B) extends BTC's security to PoS chains via BTC staking. The mental model: Bitcoin L1 is a settlement layer for high-value, high-finality transactions — comparable not to a payment rail but to Fedwire or CHIPS. For 7 TPS sustained over 17 years with effectively zero protocol-bug-driven consensus rollbacks, the throughput-to-security ratio is, by design, the most conservative in our index.
Bitcoin ecosystem map
Bitcoin's $4.03B on-chain TVL is dwarfed by what sits in BTC-denominated wrappers on other chains — and that asymmetry is the single most important fact about its ecosystem. The largest 'Bitcoin protocol' by TVL is not on Bitcoin: WBTC holds $6.99B on Ethereum, and Binance's BTCB holds $4.17B on BSC. Below those wrappers sit Babylon's $3.14B restaking layer, Lightning Network for payments, and a growing set of BTC-backed yield protocols. Stablecoin presence on Bitcoin L1 is effectively zero in our data — there is no native USDT or USDC issuance on Bitcoin, which fundamentally shapes what the chain is used for.
Bridge
WBTC (1:1 BTC wrapper on Ethereum) is the largest BTC-denominated protocol by TVL at $6,985,228,174 — more than the entire on-chain Bitcoin DeFi TVL combined. It is the de facto on-ramp for BTC into EVM DeFi; custody transitioned in August 2024 from BitGo-only to a BitGo / BiT Global joint multi-sig, a change that triggered protocols like MakerDAO/Sky to vote on offboarding WBTC collateral — a key trust-model consideration for current users.
Bridge
Binance Bitcoin (BTCB) holds $4,173,777,786 of BTC backing on BSC, making BSC the second-largest venue for productive BTC after Ethereum. Custody is fully centralized by Binance, which is the key trust trade-off versus tBTC (Threshold Network decentralized) or Babylon (non-custodial timelock).
Restaking
Babylon Protocol ($3,143,379,447 TVL) is Bitcoin's native restaking layer — BTC holders timelock coins on Bitcoin L1 to provide cryptoeconomic security to PoS chains, without giving up custody. It is the largest non-wrapper protocol in the Bitcoin ecosystem and the cleanest example of using Bitcoin L1 as a security primitive for external chains.
Bridge
Function FBTC ($660,396,321) and Lorenzo enzoBTC ($367,637,058) are newer-generation cross-chain BTC representations targeting DeFi composability, with different custody and minting architectures from WBTC's multi-sig model — part of the post-2024 wave of BTC wrappers competing on transparency and chain coverage.
Payments
Lightning Network ($298,007,624 TVL) is Bitcoin's L2 payment channel network — instant, sub-cent-fee BTC payments via routed off-chain channels, settled to L1 only on open/close. The largest non-custodial Bitcoin payment infrastructure, with the published TVL reflecting only public-channel capacity (private-channel capacity is unmeasured).
Restaked BTC
GTBTC ($211,765,961) is Gate's restaked BTC product, part of the broader BTCfi category enabled by Babylon-style timelocks and post-Taproot script flexibility unlocking richer BTC-backed yield strategies for users who do not want to wrap BTC into a custodial ERC-20.
| # | Protocol | Category | TVL |
|---|---|---|---|
| 1 | WBTC | Bridge | $6.99B |
| 2 | Binance Bitcoin | Bridge | $4.17B |
| 3 | Babylon Protocol | Restaking | $3.14B |
| 4 | Function FBTC | Bridge | $660.40M |
| 5 | Lorenzo enzoBTC | Bridge | $367.64M |
| 6 | Kraken Bitcoin | Bridge | $330.68M |
| 7 | Lightning Network | Payments | $298.01M |
| 8 | GTBTC | Restaked BTC | $211.77M |
Bitcoin vs peers
Bitcoin's category in our index is 'Bitcoin 系' — chains using Nakamoto-style PoW with Script-derivative VMs. The peers are Dogecoin, Litecoin, Bitcoin Cash, and Dash. Each is a deliberate trade-off relative to Bitcoin: faster blocks, different hash algorithms, larger block sizes, or hybrid consensus. The comparison is instructive because it isolates the cost of Bitcoin's conservatism.
| Chain | Block | Finality | TPS | TVL |
|---|---|---|---|---|
| Bitcoincurrent | 10 min | 1 h | 7 | $4.03B |
| doge | 1 min | 6 min | 30 | $0.00 |
| ltc | 2.5 min | 15 min | 30 | $0.00 |
| bch | 10 min | 1 h | 30 | $0.00 |
| dash | 2.5 min | 2 s | 10 | $0.00 |
Comparison insights
- Block time: Bitcoin's 600-second blocks are the slowest in the category. Litecoin runs 150s (4x faster), Dogecoin 60s (10x faster), Dash 150s with InstantSend (~2-second effective finality via masternode LLMQ ChainLocks). Bitcoin paid throughput for the most-vetted block interval; peers paid security margins for UX.
- Hash algorithm: Bitcoin and Bitcoin Cash share SHA-256 (and thus the same ASIC miner pool, so BCH security depends on miners choosing to point hash rate at it). Litecoin and Dogecoin use Scrypt with merged mining (AuxPoW) since 2014 — Dogecoin inherits Litecoin's hash rate without competing for it. Dash uses X11 (chained 11-algorithm hash) explicitly to resist SHA-256 ASIC concentration.
- Finality model: Bitcoin's 3,600-second 6-confirmation finality is conservative. Dash's masternode ChainLocks gives 2-second effective finality on confirmed transactions — but requires trusting the masternode quorum, a hybrid PoW+Masternode model Bitcoin explicitly rejected. Bitcoin Cash inherits Bitcoin's 6-confirmation model (finality_s=3600) but with larger blocks raising typical throughput to 30 TPS versus Bitcoin's 7.
- Economic data: Bitcoin's $4,031,417,793 on-chain TVL is the only meaningful figure in the category — DOGE, LTC, BCH, and DASH all show $0 in our DeFiLlama-tracked TVL. The Bitcoin-system peers are pure payment/store-of-value chains; only Bitcoin has accumulated meaningful programmable BTC infrastructure (Babylon, Lightning, Ordinals/Runes).
- Smart contract surface: All five chains run Bitcoin Script or a derivative — none are Turing-complete. Bitcoin Cash extended its opcode set and added CashTokens for richer scripting. Dash added a separate Layer-2 (Dash Platform) for app-like functionality. Bitcoin's choice was the opposite: keep L1 Script minimal, push expressiveness to Taproot-enabled L2s and inscription layers.
Bitcoin timeline
Bitcoin's history divides into four eras anchored by our notable_events data. Era one: genesis. 2009-01-03 — Satoshi Nakamoto mines block 0, embedding the Times headline 'Chancellor on brink of second bailout for banks' in the coinbase. The 2010 value-overflow incident (CVE-2010-5139) — an integer overflow allowing creation of 184 billion BTC — was patched within hours and remains the only protocol-bug-driven consensus exception of the early era; a March 2013 chain split caused by a LevelDB inconsistency between v0.7 and v0.8 nodes (BIP-50) was resolved by miners coordinating to downgrade, not a protocol design flaw. Era two: the scaling debate. 2015-2017 was dominated by the block-size war between small-blockers (preserve full-node decentralization) and big-blockers (raise throughput). It resolved on 2017-08-24 with SegWit activation via BIP-141, which fixed transaction malleability, effectively raised block weight to 4MB, and enabled Lightning Network. Bitcoin Cash hard-forked on 2017-08-01 over the same dispute. Era three: maturation. 2021-11-14 — Taproot soft fork activated, bundling BIP-340 (Schnorr signatures), BIP-341 (Taproot script paths), and BIP-342 (Tapscript), unlocking more private and complex scripts. This upgrade laid the technical groundwork for Ordinals (January 2023) and Runes (2024). Era four: institutional Bitcoin. 2024-04-19 — the fourth halving cut block subsidy to 3.125 BTC, coinciding with U.S. spot BTC ETF approvals earlier that year. Honest assessment: Bitcoin's L1 has had effectively zero major protocol-bug-driven consensus incidents since 2010 — but the wrapped-BTC ecosystem has had several. The 2022 RenBTC shutdown stranded user funds during the Alameda collapse, the August 2024 WBTC custody transition (BitGo to BitGo/BiT Global joint venture) triggered MakerDAO/Sky offboarding votes, and various smaller BTC bridges have suffered exploits — none of which were Bitcoin protocol failures, but they are part of the practical BTC-cross-chain risk surface users should understand.
- 2009-01-03launchGenesis block mined by Satoshi Nakamoto
- 2017-08-24upgradeSegWit activation (BIP-141)
- 2021-11-14upgradeTaproot soft fork activation
- 2024-04-19milestoneFourth halving — block reward to 3.125 BTC
Developer reference
Developer surface: official documentation lives at developer.bitcoin.org. There is no canonical public RPC URL — Bitcoin Core nodes expose JSON-RPC locally by default, and you either run your own (bitcoind) or use a provider (QuickNode, GetBlock, Blockstream Esplora API, mempool.space API). Primary block explorer: mempool.space, which exposes a free REST API for transactions, blocks, fee estimation, and mempool inspection. Address formats span four eras: Base58Check P2PKH (legacy, prefix '1'), Base58Check P2SH (prefix '3'), Bech32 SegWit (prefix 'bc1q', BIP-173), and Bech32m Taproot (prefix 'bc1p', BIP-350) — your wallet logic must handle all four. Wallet integrations supported by major Bitcoin software include Electrum, Sparrow, BlueWallet, Ledger, Trezor, Xverse (Ordinals-aware), and Unisat (BRC-20/Runes). Language stack: Bitcoin Core is C++; common SDKs include BDK (Bitcoin Dev Kit, Rust), bitcoinjs-lib (JavaScript/TypeScript), and python-bitcoinlib. For Lightning, LDK (Rust) and LND (Go) are the dominant node implementations.
Assets swappable on Bitcoin
Grouped by category. Click any asset to open its swap page for a live quote.
Majors
2 assets
Bitcoin settle-time comparison
Shorter bars mean faster confirmations. Real settle time also depends on network congestion — figures are indicative.
Bitcoin asset coverage comparison
Longer bars mean more assets are swappable on that chain.
Popular swap routes involving Bitcoin
Routes below reflect actual user preference. Click to jump straight to the swap page.
Bitcoin FAQ
01Is Bitcoin truly decentralized today?
By validator-set decentralization metrics, yes — Bitcoin has no validator set at all. Anyone can mine with sufficient hardware, anyone can run a full node to validate. Mining hash rate has concentrated into pools (Foundry USA, Antpool, ViaBTC), which is a real centralization vector, but pool members can switch pools by changing their stratum endpoint, and the protocol has no formal governance, foundation, or upgrade authority. There is no equivalent to a Solana Foundation, Ethereum Foundation, or BNB Chain operator that can unilaterally upgrade the network — changes happen via BIPs adopted through miner signaling and node-operator consensus.
02What's Bitcoin's actual finality time?
Bitcoin has no instant finality — it is probabilistic. 1 confirmation (~10 minutes) is ~99% safe against accidental reorgs and acceptable for small transactions. 6 confirmations (~60 minutes, our finality_seconds=3600 figure) is the industry-standard threshold for large settlements — at that depth, reversing a transaction would require out-hashing the entire honest network for an hour, an attack costing hundreds of millions of dollars at current hash rates. There is no signed finality gadget (unlike Ethereum's Gasper or Avalanche Snowman); finality is purely economic.
03Can Bitcoin run smart contracts like Ethereum?
No, and that is intentional. Bitcoin Script is non-Turing-complete — no loops, no general state, no recursive calls. You can write multisig, timelock, hashlock (the building blocks of Lightning), and post-Taproot more complex script trees (Tapscript), but you cannot run a Uniswap, an Aave, or an arbitrary contract on L1. Smart-contract use cases for BTC happen via wrappers (WBTC on Ethereum), Bitcoin-pegged sidechains and L2s (Liquid, Stacks, RSK), or restaking layers (Babylon).
04What is Bitcoin's real throughput?
7 transactions per second typical, ~15 TPS theoretical maximum at the L1 base layer. This is fixed by the 10-minute block interval and 4MB max block weight (post-SegWit). It is multiple orders of magnitude below high-speed L1s (Solana 3,000 typical, Hyperliquid L1 200,000 max). Bitcoin's throughput strategy is to push transaction volume to L2 — Lightning Network theoretically supports millions of payments per second aggregated across channels, settled to L1 only at open/close.
05Has Bitcoin ever been hacked or rolled back?
The Bitcoin protocol itself has had exactly one rollback from a protocol bug: the 2010 value-overflow incident (CVE-2010-5139), patched within hours when the network was tiny. A March 2013 chain split caused by a LevelDB inconsistency between v0.7 and v0.8 was resolved by miner coordination without a protocol-level flaw. Since 2013, zero protocol-bug-driven consensus rollbacks. However, exchanges holding BTC (Mt. Gox 2014, FTX 2022) and wrapped-BTC custodians (RenBTC shutdown 2022) have suffered massive losses — these are custody and bridge failures, not Bitcoin protocol failures. The distinction matters when assessing self-custodied versus wrapped BTC risk.