Ethereum Block Time Proposal to Reduce from 12s to 10s Under Consideration

Ethereum's proposed adjustment to reduce block generation intervals from the current 12 seconds to around 10 seconds has entered discussions for the next upgrade. However, EIP-8198 is still in its draft phase, and neither network application nor final slot timing has been confirmed.

Ethereum Institutional announced on X that Ethlabs' proposed EIP-8198 'Quick Slots' is supported, citing the need to increase Ethereum's processing speed as institutional on-chain activity grows. The proposal aims to make Ethereum (ETH) slot time adjustable during execution rather than a fixed value.

Ethlabs argues EIP-8198 should be included in the upcoming HegoTa upgrade, initially suggesting a reduction of slot time to 10 seconds. However, the current draft proposes 8 seconds as the baseline, which is not the final target but an initial benchmark subject to change based on network performance metrics.

Previously, Ethereum's block time reduction from 12 seconds to around 10 seconds was considered for HegoTa. The proposal will proceed in three phases: first removing the 12-second prerequisite and enabling slot time adjustment; second measuring consensus bottlenecks via developer networks and benchmarks; third gradually reducing slot time based on verification results.

The goal is not merely to increase block count but to adjust gas limits per block and blob-related parameters in line with slot timing, maintaining hourly throughput. By adjusting processing capacity alongside shorter slots, the network aims to prevent sudden increases in load. Shorter slots could potentially reduce transaction confirmation times, exchange deposits/withdrawals, DEX price updates, and Layer 2 sequencing and interoperability delays.

However, reduced block propagation and validation time may widen participation gaps based on equipment and network conditions. Whether EIP-8198 will be included in HegoTa remains undecided, with final slot timing and implementation dates pending client implementation, developer community consensus, and performance test results.