Skip to main content

Before Flashblocks

Base operates a high-availability sequencer system with five sequencer instances:
ComponentRole
op-nodeStandard OP Stack consensus layer (CL)
op-gethStandard OP Stack execution layer (EL)
op-conductorHigh availability controller with Raft consensus for leader election
One sequencer instance acts as the leader, responsible for building blocks and propagating them via P2P. The remaining four act as followers that sync the chain. Leadership transfers if the current leader stops producing blocks.

With Flashblocks

Flashblocks introduce several new infrastructure components:
ComponentPurposeWhat It Unlocks
rollup-boostCL↔EL Engine API proxyEnables sharing Flashblocks with the EL without modifying the CL. Provides a stable seam for future block-building evolutions (multi-builder, etc.)
op-rbuilderOut-of-protocol builder at 200ms cadenceProduces the sub-second Flashblocks, decoupled from the EL. Enables pluggable builder mechanisms
websocket-proxyFlashblocks stream fan-outBroadcast layer so many consumers can read the stream without overwhelming the builder
baseRPC surface exposing preconfirmationsConverts streamed Flashblocks into familiar RPCs so apps and wallets can consume preconfirmation state
Both rollup-boost and op-rbuilder are built and maintained by Flashbots, while Base maintains the websocket-proxy and base components.

Further Reading