✳flâneur — a map of the web's best reading

Proposal: Delay stateRoot Reference to Increase Throughput and Reduce Latency - Ethereum Research

ethresear.ch · 2,774 words · saved by 1 readers

Right now, each block header includes a stateRoot that represents the state after executing all transactions within that block. This design requires block builders and intermediaries (like MEV-Boost relays) to compute the stateRoot, which is computationally intensive and adds significant latency during block production. This proposal suggests modifying the Ethereum block structure so that the stateRoot in block n references the state at the beginning of the block (i.e., after executing the transactions in block n - 1, rather than the state at the end of the block). By delaying the stateRoot reference by one block, we aim to remove the stateRoot calculation from the critical path of block verification at the chain tip, thereby reducing L1 latency and freeing up capacity to increase L1 throughput. When validating block n, nodes ensure that the stateRoot matches the state resulting from executing block n-1 (i.e., the pre-state root of block n). To be clear, there is no change to exeuction

Proposal: Delay stateRoot Reference to Increase Throughput and Reduce Latency - Ethereum Research Proposal: Delay stateRoot Reference to Increase Throughput and Reduce Latency _charlienoyes September 25, 2024, 5:12pm 1 Proposal: Delay stateRoot Reference to Increase Throughput and Reduce Latency By: Charlie Noyes , Max Resnick Introduction Right now, each block header includes a stateRoot that represents the state after executing all transactions within that block. This design requires block builders and intermediaries (like MEV-Boost relays) to compute the stateRoot , which is computationally

Explore this link on the map →

related reading