A single sequencer: pragmatic choice or structural risk?
Several leading rollups, including Arbitrum, Optimism and Base, launched with a centralised sequencer. Is that an acceptable trade-off or a warning sign?
Educational purpose. The contents of this article are for information and general understanding only. They do not constitute financial advice. Full disclaimer.
Transaction ordering 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 or reordering transactions for profit; censor transactions by ignoring unwanted ones; and engage in front-running by getting ahead of other users' transactions.
In a decentralised system, no single actor holds this power. In a system with a centralised sequencer, the project team does.
Why rollups often start with a centralised sequencer
The honest answer is that it is simpler.
A decentralised sequencer requires a consensus protocol among multiple sequencers, anti-collusion mechanisms, leader-election or rotation systems, and economic incentives that are sound and not open to attack.
Building all of this before launch means years of additional development. Arbitrum, Optimism and Base — the rollups with the highest total value locked on Ethereum — all launched with a centralised sequencer, and are still decentralising years later.
Bitcoin Hyper states explicitly (chapter 34.2 of the book) that, at mainnet launch, the sequencer will be centralised and run by the team. The roadmap sets out a gradual decentralisation over two to four years, through rotation, auctions and leader election. This is a stated intention rather than a completed feature.
How is censorship risk mitigated today?
The key architectural mechanism is forced inclusion: a transaction can be "forced" into the rollup by way of Bitcoin's base layer, bypassing the sequencer itself. If the sequencer censors you, you can still have your transaction processed by paying the fee directly on Bitcoin. A single sequencer introduces a central point of operational control; forced inclusion is the safety valve designed to keep that control from becoming absolute.
The catch is that forced inclusion is still under development in Bitcoin Hyper (status as of 28 April 2026). It is not yet available on the devnet. Until it ships and is tested, the protection it is meant to provide remains theoretical.
Signals worth watching
Before considering any exposure to Bitcoin Hyper, these are the signals that point to genuine progress on decentralising the sequencer:
- Published technical specifications for the chosen decentralisation mechanism
- Forced inclusion live on testnet or mainnet
- A roadmap with verifiable milestones (not merely "in the coming years")
- An audit of the sequencer code by recognised independent firms
- A credible timeline with explicit dependencies
Conclusion
A centralised sequencer at launch is an understandable, pragmatic choice — not necessarily a red flag. It does not necessarily imply any loss of funds, but it may affect liveness, transaction ordering and censorship resistance. It becomes a problem if there is no concrete decentralisation roadmap, if forced inclusion is never implemented, or if the team uses its position to extract MEV opaquely.
The project states that sequencing will be decentralised at a later stage. At the time of writing, that transition remains a roadmap objective: Bitcoin Hyper has declared its intent, and the judgement will be formed on what it actually delivers.