BVM
  • About bvm
    • Development infrastructure for Bitcoin
    • Follow our progress
  • getting started
    • Build a Bitcoin L2 with BVM Studio
    • Level up with Bitcoin dapps
    • Deploy your own Bitcoin dapp
  • L1 Scaling solutions
    • What are Bitcoin Shards? [WIP]
    • Compute sharding [WIP]
    • Data sharding [WIP]
    • Case studies [WIP]
      • SHARD_BVM
        • Bitcoin Virtual Machine #0
      • SHARD_DA [WIP]
      • SHARD_AI [WIP]
  • L2 Scaling solutions
    • What are Bitcoin rollups?
    • Optimistic rollups
    • ZK rollups
  • l3 scaling solutions
    • What are Bitcoin appchains?
    • Rollups from appchains to L2s
  • Bitcoin decentralized bridges
    • Bitcoin <> BVM bridge
    • Bitcoin <> Ethereum bridge [WIP]
    • Bitcoin <> Solana bridge [WIP]
  • bvm studio
    • Overview
    • Build a Bitcoin L2
    • Monitor a Bitcoin L2
    • Scale a Bitcoin L2
    • Building blocks
  • bitcoin heartbeats
    • Overview
    • Chain heartbeats
      • Key metrics
      • Bitcoin's 5 levels of scalability
    • Wallet heartbeats [WIP]
    • Dapp heartbeats [WIP]
  • bitcoin api
    • RaaS API
    • Chain API [WIP]
  • bitcoin dapps
    • Overview
    • EVM code tutorials
      • Build a Bitcoin Name System
      • Build an Ordinals alternative
      • BFS: Build an IPFS alternative
      • Decentralized AI
      • Auction
      • Decentralized Discord
      • Fully onchain Tic-Tac-Toe
      • BRC-721: NFTs
      • Operate your project using a DAO
      • Raise funds through a Crowdsale
      • Issue your own governance token
    • SVM code tutorials [WIP]
Powered by GitBook
On this page
  • LEVEL 1
  • LEVEL 2
  • LEVEL 3
  • LEVEL 4
  • LEVEL 5
  1. bitcoin heartbeats
  2. Chain heartbeats

Bitcoin's 5 levels of scalability

PreviousKey metricsNextWallet heartbeats [WIP]

Last updated 8 months ago

With the growing number of Bitcoin L2s, it’s crucial to have a framework to track their progress.

As part of the Bitcoin Heartbeats project, we propose the following standard to classify them.

LEVEL 1

Bitcoin L2s at Level 1 do not utilize Bitcoin as the base layer, do not use Bitcoin for data availability (DA), and lack state verification.

Examples: Most Bitcoin sidechains fall into this category. They operate their own consensus mechanisms, store data independently, and establish bridges to Bitcoin without leveraging Bitcoin’s infrastructure for state or data.

LEVEL 2

Bitcoin L2s at Level 2 use Bitcoin as the base layer for storing proofs while relying on external DAs (such as Celestia, Avail DA, or Filecoin) for transaction data storage.

They do not perform state verification. Current Bitcoin rollups predominantly fit into this level. Due to their relatively low user base, these solutions often choose external DAs to minimize costs—a practical approach at this stage.

LEVEL 3

Bitcoin L2s at Level 3 use Bitcoin for storing all data, but do not include state verification.

Trustless Computer and perhaps Ordinals serve as examples here.

LEVEL 4

Bitcoin L2s at Level 4 store all data on Bitcoin and include state verification performed by external light clients.

Supersonic, a ZK rollup on Bitcoin, is an example of this level.

LEVEL 5

Bitcoin L2s at Level 5 store everything on Bitcoin and incorporate native state verification directly on Bitcoin, like with BitVM or OP_CAT in the future.