If you have read about Base's architecture, you have probably run into the word sequencer without a clear explanation of what it does. It sounds like plumbing, and in a sense it is. But it is also the component most responsible for the experience you actually feel when you swap on Base: the near instant confirmations, the low fees, and the smooth ordering of transactions.
This article explains what a sequencer is, why Base currently relies on one operated by Coinbase, and what would actually happen to your funds if that sequencer stopped working.
What a sequencer does
Every blockchain needs some way to decide the order transactions get processed in. On Ethereum, that job is spread across thousands of independent validators who take turns proposing blocks. On Base, that job is currently done by a single component: the sequencer.
The sequencer receives incoming transactions, puts them in order, executes them, and packages the results into blocks. Because it is one component rather than a large distributed set of validators reaching consensus, it can do this very quickly. That speed is a big part of why a swap on Base can feel almost instant, while the same action on Ethereum mainnet might take much longer to confirm.
After the sequencer produces blocks, Base periodically batches that transaction data and posts it down to Ethereum. That step is what anchors Base's activity to Ethereum's security, a process covered in more detail in our article on how Base stays secure.
Why a single sequencer is a trade off, not a shortcut
It is worth being direct about this: Base's sequencer is centralized today. Coinbase operates it, and there is currently no competing set of independent parties taking turns producing blocks the way there is on Ethereum. Base has publicly stated an intention to move toward a more decentralized, multi-party sequencing model over time, but that is a roadmap item, not the current state.
Centralization here means two different things, and it is easy to conflate them.
The first is a question of censorship and liveness. A single operator is, in principle, able to decide which transactions to include or exclude, and the network depends on that one operator being online and honest for new transactions to process smoothly.
The second, and more important one for you personally, is a question of custody. A centralized sequencer does not mean a centralized custodian. The sequencer orders and executes transactions, but it never takes control of your assets. Your funds move only through your own wallet, following the same self custody rules that apply anywhere else. That distinction matters a lot when thinking through worst case scenarios.
What actually happens during a sequencer outage
Base has experienced brief sequencer outages in the past, as have other rollups built on similar designs. When that happens, the practical effect is straightforward: new transactions stop processing until the sequencer resumes. Swaps will not confirm, transfers will not go through, and the network effectively pauses from a user's point of view.
What does not happen is any change to your existing balances. The state of the chain, including everyone's token balances, is not stored inside the sequencer. It lives in the blockchain's own data, which is periodically committed to Ethereum. A sequencer outage is an availability problem, not a solvency problem. Your tokens are exactly where they were before the outage, and they remain that way whether the sequencer is down for a minute or considerably longer.
This is also why the OP Stack, the framework Base is built on, includes a mechanism often called forced inclusion. In principle, if a sequencer were to censor a transaction indefinitely, users have a path to submit that transaction directly through Ethereum, bypassing the sequencer entirely. It is a slower, more expensive route, and not something an everyday swapper needs to think about day to day, but it exists specifically as a backstop against sequencer misbehavior. It is the kind of safety valve that only matters in an edge case, and its main value is that it changes the incentives long before anyone needs to use it.
What this means for you as a user
A few practical points are enough to carry with you.
- The sequencer is what makes Base feel fast. It orders and processes your transactions in roughly two seconds, rather than the longer block times you would see settling directly on Ethereum.
- A sequencer outage means transactions pause, not that funds disappear. Your balances are secured by data anchored to Ethereum, not by the sequencer's continued operation.
- Centralized sequencing today is a known, publicly acknowledged trade off, with decentralization work underway across Base and the broader OP Stack ecosystem. It is reasonable to want that work to progress, and reasonable to use the network in the meantime with realistic expectations about its current design.
- None of this changes your own responsibilities. Self custody, careful approvals, and verifying what you sign remain entirely on you regardless of how sequencing evolves.
The short version
The sequencer is the component that orders and processes transactions on Base, and it is currently run by a single operator, Coinbase. That centralization affects the availability and censorship resistance of new transactions, but it does not put your existing funds at risk, because Base's security ultimately rests on data settled to Ethereum rather than on the sequencer's uptime. Understanding that distinction is a useful way to reason calmly about outages if you ever encounter one, instead of assuming the worst.