A single sequencer: pragmatic choice or structural risk?
Several major rollups, Arbitrum, Optimism and Base among them, launched with a centralised sequencer. Is that an acceptable trade-off or a warning sign?
Educational purposes. the content of this article is provided for information and general understanding only. It is not financial advice. Full disclaimer.
Deciding the order of transactions is power
Every rollup needs someone — or something — to decide the order in which transactions are processed. That is the job of the sequencer.
Ordering is not neutral. Whoever controls the sequencer can: extract MEV (Maximal Extractable Value) by inserting transactions or reordering them for profit; censor transactions by ignoring the ones it does not want; and front-running by getting ahead of other users' transactions.
In a decentralised system that power rests with no single participant. In a system with a centralised sequencer it rests with the project's team.
Why rollups so often start with a centralised sequencer
The honest answer is that it is easier.
A decentralised sequencer requires a consensus protocol among several sequencers, anti-collusion mechanisms, leader-election or rotation systems, and economic incentives that are well thought through and cannot be gamed.
Building all of that before launch means years of additional development. Arbitrum, Optimism and Base — the rollups with the highest total value locked on Ethereum — all started with a centralised sequencer, and years on they are still decentralising.
Bitcoin Hyper states plainly (chapter 34.2 of the book) that at the start of mainnet the sequencer will be centralised and operated by the team. The roadmap envisages gradual decentralisation over two to four years through rotation, auctions and leader election. That is a stated intention, not a feature already in place.
How is the censorship risk contained today?
The principal architectural mechanism is forced inclusion: a transaction can be forced into the rollup by way of Bitcoin's base layer, bypassing the sequencer. If the sequencer censors you, you can still have your transaction processed by paying the fee directly in Bitcoin. A single sequencer creates a central point of operational control; forced inclusion is the safety valve that is meant to stop that control becoming absolute.
The catch is that in Bitcoin Hyper forced inclusion is still in development (as at 28 April 2026). It is not yet available on DevNet. Until it is ready and tested, the protection it offers remains theoretical.
Signals to watch
Before considering any position in Bitcoin Hyper, these are the signals that would show real progress on decentralising the sequencer:
- Published technical specifications for the decentralisation mechanism chosen
- Forced inclusion live on testnet or mainnet
- A roadmap with verifiable milestones (not merely “in the coming years”)
- Auditsof the sequencer code by recognised independent firms
- A credible timeline with dependencies stated clearly
In summary
A centralised sequencer at launch is an understandable and pragmatic choice — not necessarily a warning sign. It does not automatically mean a loss of funds, but it can affect the reliability of the system, the ordering of transactions and resistance to censorship. It becomes a problem when there is no concrete roadmap to decentralisation, when forced inclusion is not implemented, or when the team uses its position to extract MEV opaquely.
The project says that sequencing will be decentralised at a later stage. At the time of writing that transition is still a roadmap objective: Bitcoin Hyper has declared its intention, and the assessment will rest on what it actually delivers.