# History Expiry Moves Forward in Ethereum’s Fusaka Upgrade Source: https://etherworld.co/2025/06/16/history-expiry-moves-forward-in-ethereums-fusaka-upgrade Kiwi News: https://news.kiwistand.com/stories/History-Expiry-Moves-Forward-in-Ethereums-Fusaka-Upgrade?index=0x6851eac0b025effd0b54493293118b827a76617ec41162cd4287095a79ab2742ea6ed6ee Submitted by misha on 2025-06-17 UTC, 1 upvote, 0 comments ## Summary 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. ## Article As Ethereum scales its infrastructure to support greater throughput and more efficient state management, one persistent challenge remains: the growing burden of maintaining the network’s full historical data. In preparation for Fusaka Devnet 2, Ethereum core developers have made tangible progress on a history expiry strategy. The goal is to reduce disk usage and sync overhead across clients while preserving access to essential data through modular mechanisms. A key innovation is the introduction of ERA files, which separate execution and consensus history into independently manageable formats. This approach is expected to provide long-term flexibility for pruning while maintaining the integrity required for historical audits. What Is History Expiry & Why It Matters Ethereum nodes store terabytes of historical block and state data, much of which is no longer essential for routine operations or ongoing validation. While archival nodes and block explorers may depend on this history, most validators and full nodes do not need to retain data stretching back to Ethereum’s genesis. Eliminating this burden could significantly reduce node sync times, lower storage costs, and improve decentralization by making node operation more accessible. However, any pruning strategy must ensure that historical access remains possible, whether for fraud proofs, audits, or consensus level reconciliation. The ERA File Framework To manage this balance, developers are converging around a dual-layered history pruning model: ERA-E (Execution Layer File): Stores essential execution-layer data such as block headers, receipts, and state roots. Allows pruning of older state while retaining the execution logic needed for validation. ERA-C (Consensus Layer File): Captures finalized checkpoints, beacon chain roots, and other consensus-critical metadata required for validating historical attestations. This separation allows clients to drop pre-merge history and retain only the data relevant to post-merge functionality, without compromising trust guarantees. Developers have agreed that history pruning will remain optional and client-driven: Each client (e.g., Geth, Nethermind, Erigon, Teku, Prysm) can ship history-pruning as a default or opt-in mode. Releases will begin dropping pre-merge history independently, depending on implementation readiness. Ethereum Foundation plans to publish guidance to help node operators enable pruning where supported. For now, clients will still provide access to full history if desired, while also introducing lightweight modes that exclude old chain segments. Integration with the Portal Network In parallel, developers are re-examining the role of the Portal Network, Ethereum’s decentralized history retrieval system designed to replace traditional archival nodes. While the Portal spec offers a broad set of features, most are not directly useful to execution clients. Fusaka Devnet 2 will initiate efforts to: Extract and prioritize only the useful subset of Portal functionality (e.g., range queries, header sync) Integrate this subset directly into execution clients Enable fallback access to historical data without requiring external systems or centralized storage providers A dedicated community call is being planned for late June to finalize direction on Portal modifications. Conclusion History expiry is not just a disk optimization; it is a prerequisite for long term scalability and decentralization. By enabling clients to drop legacy data safely, Ethereum ensures that future node operators can participate in consensus without requiring multi terabyte infrastructure. Fusaka Devnet 2 provides the proving ground for these architectural changes, and success here will shape how Ethereum balances accessibility, security, and state efficiency for years to come. If you find any issues in this blog or notice any missing information, please feel free to reach out at yash@etherworld.co for clarifications or updates. Related Articles Ethereum Fusaka Devnet 0 Coming Soon Will Fusaka Be Ready in Time? Vitalik's 2025 Vision Glamsterdam: The Next Upgrade After Fusaka Ethereum Developers are Rethinking Transaction Signatures & Authority Censorship Resistance Vs Scalability _____________________________________________________________________ Disclaimer: The information contained in this website is for general informational purposes only. The content provided on this website, including articles, blog posts, opinions, and analysis related to blockchain technology and cryptocurrencies, is not intended as financial or investment advice. The website and its content should not be relied upon for making financial decisions. Read full disclaimer and privacy Policy. For Press Releases, project updates and guest posts publishing with us, email to contact@etherworld.co. Subscribe to EtherWorld YouTube channel for ELI5 content. Share if you like the content. Donate at avarch.eth. You've something to share with the blockchain community, join us on Discord! Follow us at Twitter, Facebook, LinkedIn, and Instagram.