History Expiry Moves Forward in Ethereum’s Fusaka Upgrade

Ethereum core developers have made progress on a history expiry strategy in preparation for Fusaka Devnet 2, aiming to reduce disk usage and sync overhead while keeping access to essential data. The approach centers on ERA files, with ERA-E storing essential execution-layer data such as block headers, receipts and state roots, and ERA-C capturing finalized checkpoints and beacon chain roots. Developers have agreed that history pruning will remain optional and client-driven, with clients including Geth, Nethermind, Erigon, Teku and Prysm able to ship it as a default or opt-in mode. The article also says developers are re-examining the Portal Network, with Fusaka Devnet 2 set to extract and integrate its useful subset into execution clients.