Ethereum’s Fusaka upgrade may face delay

Key Points

1. Consensus-client teams, including Lodestar and Prysm, requested an additional four weeks to finalize release candidates, citing the current September 1 deadline as 'aggressive.'

2. Prysm's Manu Nalepa emphasized the need for thorough testing, particularly for private mempools, and noted over 4,000 lines of code still need merging.

3. The delay would allow teams to integrate large feature branches, including PeerDAS for improved blob data distribution and private mempool behavior testing.

4. Fusaka's fork is critical for enabling PeerDAS and introducing Blob Parameter Updates (BPOs), which aim to increase blob capacity without requiring another hard fork.

5. Despite the delay, the plan remains to launch the Holesky testnet in September and target the mainnet fork for November, aligning with Devconnect in Buenos Aires.