Overview
This section describes how transactions are ordered on the Base networks.Block Building
Base builds a complete canonical block every 200ms. Each block has its own hash, state root, and receipts. Blocks are built bybase-reth-node, and transactions within each block are ordered by priority fee. See 200ms Native Blocks for the protocol design.
When a block starts building, the builder takes a snapshot of the transaction pool, and it builds the block only from transactions in that snapshot. This applies to standard transactions and validity transactions alike. A transaction that reaches the sequencer after a block has started building waits for the next block: it becomes eligible for the first block that starts building after it arrives, where it is ordered by priority fee. A transaction can’t join the block that is already being built, whatever priority fee it pays.
As soon as a block is built, the sequencer seals it and broadcasts it to the network. It doesn’t wait for a fixed deadline, so other nodes receive each block sooner and have more time to react before the next block starts building. If the sequencer doesn’t get the signal that a block is ready, it seals the block at the 150ms deadline instead. Early broadcasting doesn’t change block contents or timestamps.