> For the complete documentation index, see [llms.txt](https://docs.bvm.network/bvm/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.bvm.network/bvm/bitcoin-heartbeats/chain-heartbeats/bitcoins-5-levels-of-scalability.md).

# Bitcoin's 5 levels of scalability

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.

<figure><img src="/files/14bjIoOn2GJaPQju5U9i" alt=""><figcaption></figcaption></figure>

## 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.&#x20;

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&#x20;

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&#x20;

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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.bvm.network/bvm/bitcoin-heartbeats/chain-heartbeats/bitcoins-5-levels-of-scalability.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.