Sequencer
Sequencer: the node or operator in a rollup that receives users' transactions, puts them in order, executes them, and bundles them into batches posted to the underlying layer 1 blockchain, usually Ethereum.
A sequencer is the part of a rollup that handles transactions as they come in. It receives users' signed transactions, decides their order, executes them, and returns a near-instant confirmation. It then compresses many transactions into a batch and posts the data to layer 1. There the results can be checked by fraud proofs in optimistic rollups or validity proofs in ZK-rollups.
For example, when someone swaps tokens on a layer 2 network, their wallet sends the transaction to the sequencer rather than to Ethereum's mempool. The sequencer confirms it within moments, which is a large part of why layer 2s feel fast and cheap. That confirmation is only "soft" finality, a promise that the transaction will be included. It becomes final once the batch is posted and settled on layer 1.
Many major rollups still run a single sequencer operated by the project team or a foundation. Because it controls ordering, a centralized sequencer could censor transactions, reorder them to capture MEV, or stop processing transactions during an outage. A common misconception is that it can simply take users' funds. It cannot push invalid state changes past the proof system, as long as the transaction data is available on layer 1. Well-designed rollups also let users submit transactions through a layer 1 contract to force inclusion or withdraw if the sequencer ignores them, though this route is slower and costlier. Decentralized and shared sequencer designs aim to reduce these risks.