What Is a Rollup — and Why Bitcoin Needed One
Bitcoin is the most secure network in the world, yet it processes roughly 7 transactions per second. Rollups offer a way to scale it without sacrificing the security of the base layer.
For educational purposes. The content of this article is intended solely to inform and explain. It does not constitute financial advice. Full disclaimer.
Bitcoin's scalability problem
Bitcoin is designed to be slow. This is not a flaw but a deliberate choice. Every node on the network has to validate every transaction, and that process takes time. The result is a network that handles around 7 transactions per second (TPS), against the thousands Visa can process or the tens of thousands Solana claims.
For years the debate came down to a single question: how can Bitcoin be scaled without breaking what makes it unique?
The roads already taken
The first answer was the Lightning Network (2018): a system of bidirectional payment channels that enable instant, near-free transactions between two parties. It is elegant and works well for micropayments, but it carries structural limitations: it requires pre-allocated liquidity, it does not support complex smart contracts, and it suffers from the routing problem at scale.
Stacks attempted a different approach: a separate blockchain that "anchors" its blocks to Bitcoin, with its own smart-contract language (Clarity). It is an interesting design, but its finality ultimately depends on the fork-choice rule of Stacks itself.
Rootstock (RSK) opted for EVM compatibility and merge-mining with Bitcoin. It has existed since 2018, yet its ecosystem has remained limited.
Why a rollup is different
A rollup is not a sidechain. The technical distinction is crucial:
- - A sidechain provides its own security (its own validators, its own consensus). If the sidechain is attacked, the losses are real.
- - A rollup executes transactions off-chain but publishes the compressed state to Bitcoin. Its security is inherited from the base chain.
The process works as follows:
- Users submit transactions to the rollup's sequencer
- The sequencer orders them and executes them in batches
- Periodically, the state commitment (a Merkle root of the updated state) is published to Bitcoin via OP_RETURN or Taproot
- Anyone can verify the state transition
Anchoring to Bitcoin means that rewriting the rollup's history would require rewriting Bitcoin's transaction history — for all practical purposes, impossible.
Data availability: the unresolved question
The critical point is this: where do the transaction data actually live? If only the commitment sits on Bitcoin while the full data remain in the hands of the sequencer, the rollup is technically a validium rather than a true rollup. The distinction is not academic: if the sequencer disappears with the data, users may be unable to prove their own balance.
Bitcoin Hyper is candid on this point: the final data-availability solution is still the subject of ongoing research (as stated in an update dated 27 March 2026). The options being explored include external DA layers (such as Celestia), erasure coding and distributed nodes.
In summary
A rollup on Bitcoin offers: security inherited from Bitcoin for finality and immutability; higher throughput thanks to off-chain execution; programmability through smart contracts (which is not possible on L1); and lower costs for end users.
The price is architectural complexity and several trade-offs that remain open (the sequencer, data availability, the bridge). Bitcoin Hyper is betting that these trade-offs are acceptable — and manageable over time.