Skip to main content

Sequencer

The sequencer is a set of plugins, bundled with Linea BesuLinea Besu A build of the Besu execution client, extended with Lineth plugins such as the sequencer and tracer that add ZK-rollup functionality. Linea Besu is required to propose blocks and to generate traces, so every sequencer node must run it. Nodes that only import blocks or serve standard Ethereum JSON-RPC can run any Ethereum execution client., that extends the Besu execution client. It is responsible for ordering, building, and executing LinethLineth (Formerly the Linea Stack) The open-source ZK-rollup stack, codebase, and technical protocol that's the foundation of Linea Mainnet. Operators can deploy this stack to launch their own Ethereum-compatible L2 or L3 networks. blocks in a way that enables the creation of ZK proofsZero-knowledge proof A cryptographic method that allows an individual to prove that a statement is true without conveying any additional information. This is useful for scaling blockchain networks through rollups, because it reduces the amount of information you have to provide to lower layers..

The sequencer nodeSequencer node A node that pairs a Maru validator with a Linea Besu execution client running the sequencer plugins. This pairing is what produces canonical blocks: Maru handles consensus, and Linea Besu orders, builds, and executes the block. Some materials use "validator" and "sequencer" interchangeably. Here, the validator is the Maru process, the sequencer is the Linea Besu plugin set, and the sequencer node is the two together. is not directly accessible from outside the network (to prevent DDOS attacks). Instead, it's connected to the RPC nodes via P2P.

note

Because the Besu execution client is fully extensible with plugins, operators can extend and apply arbitrary business logic, such as enforcing regulatory logic at the block building level, and controlling which transactions may be executed by the EVM.

How it works​

The sequencer takes transactions from the memory pool, orders and validates them, and selects them for inclusion in a block according to Lineth's rules. During selection, it runs each candidate through the tracer to enforce per-block limits (trace line counts, gas limits, calldata size) and ensure the block fits within blob size constraints, then executes and imports the block.

The sequencer also provides the coordinator with the data needed to prove those blocks: the trace counts that determine how many blocks to conflate into one batch, and then the conflated trace file for that batch, produced by re-executing its blocks. This keeps proofs as compact as possible, which matters because all proof data has to be written in tiny, costly pieces on the finalization layerFinalization layer The blockchain where a Lineth deployment submits proofs and state commitments for verification and hard finality. If the finalization layer is Ethereum (an L1), the deployment is an L2. If the finalization layer is Linea (an L2), the deployment is an L3..

note

A single-validator deployment runs one sequencer. Multi-validator deployments run one sequencer per Maru validatorMaru validator A Maru node that belongs to the QBFT validator set and proposes and votes on blocks. Each Maru validator requires its own dedicated Linea Besu execution client running the sequencer plugins, which builds the payload Maru then signs and broadcasts. A validator can also drive additional follower execution clients., since each validator needs its own Linea Besu with the sequencer plugins. See Multi-validator consensus.

Transaction validity conditions​

In addition to standard EVM validity checks (signature, nonce, balance, gas limits), the sequencer applies a Lineth-specific profitability threshold during transaction pool admission and block-building selection. By default, the threshold uses the same gas price calculation described in Estimate gas costs, including the compressed transaction size, gas denominator, fixed/variable costs, and context-specific margin.

Transactions that do not meet the threshold can be rejected from the mempool or skipped during selection. This profitability check does not apply to sequencer-prioritized system transactions, including forced transactions.

Operators can configure the fixed and variable gas costs, and separate margins for pool admission and block-building selection, using the sequencer's profitability options.

See also​

Was this page helpful?