LP-226 Dynamic Minimum Block Times for Sub-Second Blocks

LP-226 replaces per-block gas cost with a dynamic minimum block delay to enable sub-second blocks, align with validator preferences, and prepare the network for higher gas targets.

Back

What's Changing?

LP-226 proposes swapping the old per-block gas cost for a simple, enforced minimum wait between blocks. New block header fields make sub-second blocks possible and keep spacing consistent. The delay naturally gravitates toward the stake-weighted median preference of all validators (same control style as LP-176), so cadence aligns with what validators actually want.

Why Change the Current Mechanism?

The current gas check mechanism is overly complex and does not reliably prevent exceeding the target rate when priority fees already cover the costs. No enforced minimum time between blocks can allow for bursts and risk periods of network instability.

LP-226 introduces a minimum wait before the next block, enabling sub-second block production without network upgrades.

How the Dynamic Delay Work?

The effective minimum delay uses a controller similar to LP-176 with a dynamic Q parameter. Validators can set their preferred minimum delay and the network will converge around the stake-weighted median. While the LP-176 dynamic fee mechanism still sets the target gas rate, LP-226 reinforces network safety and prepares all the network's EVM chains for higher gas targets and smoother UX.

Looking Ahead

As gas targets climb, expect smaller, more frequent blocks and a snappier user experience. Streaming Asynchronous Execution (a.k.a. SAE, a.k.a. LP-194) and ongoing performance work make lower delays practical. We'll also share visuals that show how LP-226 and LP-176 fit together in practice.

Want to Learn More?

Here are some resources to learn more about LP-226, as well as future updates:

Is this guide helpful?

Written by

On

Thu Sep 04 2025

Topics

LPBlock TimeEVM ChainsConsensusPerformance