Terminology & Versions
Comprehensive document explaining how the components are connected in a modular manner to achieve a generalist stack that can be integrated by different applications.
Sequencer Client 1.0 — Current
Off-Chain Components (Rust)
Node Client Interface: Connects to and reads data from underlying node clients (e.g.,
reth).Event Listener Service: Monitors integrated chains for incoming transactions and submitted batches.
Transaction Manager Service: Manages the lifecycle of individual transactions.
Block Execution Security Service: Provides protection against reorgs.
Batch Manager: Sequences transactions into batches within a 15-second window.
Prover Service: Interfaces with the Bonsai/Boundless network to request proofs.
Lane Manager: A security service that manages transaction flow with a volume tracker and lane selector.
Sequencer Database: Stores a history of all relevant on-chain events.
On-Chain Components (Solidity)
BatchSubmitter.sol: Submits and executes transactions in the correct sequence on the destination chain.GasFeeManager.sol: Dynamically adjusts cross-chain submission gas prices.
Sequencer Client 2.0 — Future
Off-Chain Components (Rust)
Dynamic Batch Manager: Optimizes Batches for gas costs and latency delivery, proof generation optimizer, Dynamic Sequencer Fee market
Dynamic Lane Manager: Adjusts and moves transactions between lanes as volume frees up on market
Threat Responder: Leverages security monitoring tools to dynamically prevent critical
Dynamic Chain Kill Switch (Temporary or permanent)
Blob Monitoring on ETH Mainnet for trustless finalization
Inflow/Outflow reset trigger
Action temporary pause (mints/repays/borrows/withdraws)
On-Server Monitoring Agent: To monitor system health, uptime, and API latency
Liquidity Monitoring Tool: Monitors pool liquidity before execution to optimize gas consumption
On-Chain Components (Solidity)
BatchSubmitter.solv2: Selects TXs with an array from batch to be executed
Sequencer 3.0 — Future
Future improvements
Pre-confirms: ZK-STARK based TX execution acting as pre-confirms secured by EigenLayer Actively Validated Services
Stateless Account Management System with Merkle-trees: Apps can directly maintain accounting in a stateless manner leveraging the power of ZK
Last updated
