What a rollup is and why Bitcoin needed one
Bitcoin is the most secure network in the world, yet it settles only about seven transactions per second. Rollups offer a way to scale it without compromising the security of the base layer.
Educational purposes. the content of this article is provided for information and explanation only. It is not financial advice. Full disclaimer.
Bitcoin's scalability problem
Bitcoin was built to be slow. That is not a flaw but a deliberate decision. Every node on the network has to verify every transaction, and that takes time. The result is a network that settles roughly seven transactions per second (TPS), while Visa can handle thousands and Solana claims tens of thousands.
For years the debate came down to a single question: how do you scale Bitcoin without breaking the very thing that makes it distinctive?
The routes taken so far
The first answer was the Lightning Network (2018): a system of bidirectional payment channels that makes fast, all but free transactions possible between two parties. It is elegant and works well for micro-payments, but it has structural limits: it needs liquidity allocated in advance, it does not support complex smart contracts, and routing becomes difficult at scale.
Stacks took a different approach: a separate blockchain that “anchors” its blocks to Bitcoin and has its own smart contract language (Clarity). It is an interesting solution, but its finality ultimately depends on Stacks' own fork-choice rule.
Rootstock (RSK) chose EVM compatibility and merge-mining with Bitcoin. It has been around since 2018, but its ecosystem has remained limited.
Why a rollup is different
A rollup is not a sidechain. The technical distinction matters a great deal here:
- - Sidechain secures itself (its own validators, its own consensus). If a sidechain is attacked, the loss is real.
- - Rollup executes transactions off-chain, but publishes a compressed state to the Bitcoin network. Its security is inherited from the base chain.
The process runs as follows:
- Users submit their transactions to the rollup's sequencer
- The sequencer orders them and executes them in batches
- At regular intervals, the state commitment (a Merkle root of the updated state) is published to the Bitcoin network via OP_RETURN or Taproot
Being anchored to Bitcoin means that rewriting the rollup's history would mean rewriting Bitcoin's transaction history — impossible in any practical sense.
Data availability: the unresolved question
The decisive point is this: where does the transaction data actually live? If only the commitment is on Bitcoin while the full data stays with the sequencer, then technically the rollup is closer to a validium than to a genuine rollup. The distinction is not merely academic: if the sequencer disappears along with the data, users may be unable to prove their balances at all.
Bitcoin Hyper is candid on the point: the final data availability solution is still under study (as noted in the update of 27 March 2026). The options being considered include external DA layers (Celestia, for example), erasure coding and distributed nodes.
Conclusion
A rollup built on Bitcoin offers: security inherited from Bitcoin for finality and immutability; higher throughput thanks to off-chain execution; Programmability through smart contracts (which L1 does not allow); and lower costs for the end user.
The price is architectural complexity and a number of trade-offs that remain open (the sequencer, data availability, the bridge). Bitcoin Hyper's bet is that those trade-offs are acceptable — and manageable over time.