Continuous Block Pipeline

In typical layer 2 architecture, as little as 8% of the blocktime is spent on execution. Here is what the flow looks like:

1. Consensus deriving L1 transactions and new block attributes
2. Execute Derived Transactions
3. Fetch transaction from mempool and execute
4. Prepare the header and compute the state root

In traditional systems, these steps are executed sequentially, leading to inefficient use of block time. RISE's CBP introduces a parallelized block pipeline with concurrent stages and a Continuous Execution (CE) thread. This allows for:

• Concurrent execution of transactions: The CE thread monitors the Mempool for transactions and executes them in multiple block segments, no longer waiting for consensus to request a new block.
• Continuous state root computation: State root computation occurs concurrently with execution.
• Optimized mempool processing: A new Mempool structure balances latency and throughput by pre-ordering transactions to minimize shared states and maximize parallel execution.

This results in significantly improved block production efficiency compared to traditional sequential approaches. In practice, CBP allows for transaction execution close to 100% of the available time, compared to as low as 8% in worst-case scenarios for traditional systems.

The Continuous Block Pipeline (CBP) ensures one thing: If there are transactions in the mempool, the execution client is executing. Ie, CBP ensure that transactions are continuously being executed.