Ethereum developer Kevaundray Wedderburn has submitted a new Ethereum Improvement Proposal through GitHub pull request #12188 on August 17, calling for a reduction in the consensus layer (CL) block retention window.

The proposal, currently a draft awaiting an official EIP number, would cut the required retention period from 33,024 epochs to 8,192 epochs, approximately 36.4 days. With each consensus-layer epoch spanning 32 slots of roughly 6.4 minutes, the current requirement equates to about 147 days — close to five months — of stored history. The EIP is classified as non-forking and informational: rather than altering Ethereum's protocol rules, it would update expectations for node operators.

The change's primary aim is to reduce the backfill burden that follows checkpoint synchronization, the common practice of starting a new beacon node from a recent trusted checkpoint rather than replaying the chain from genesis, then retrieving older blocks afterward. By shortening how long nodes are required to retain historical beacon blocks, the proposal would lower demands on bandwidth, disk space, and sync time, aligning with Ethereum's long-stated goal of keeping node requirements light enough to encourage broad participation. The draft also echoes earlier execution-layer discussions such as EIP-4444, which proposed that clients stop serving historical block data older than one year.

The draft has entered public review and received early support from within the developer community. Ethereum contributor Dapplion endorsed the direction of the proposal, while Lighthouse client developer Michael Sproul said he does not foresee operational issues arising for Lighthouse. Sproul added that in a mixed network, older clients would remain able to sync from peers still holding the longer retention window. The pull request has not been merged; next steps would include the assignment of an official EIP number and, if adopted, aligned default retention settings across client implementations.

Developers Weigh 66 Proposals for the 2027 Hegotá Upgrade

The retention-window draft is one of several proposals circulating in the Ethereum developer community this week, as attention also turns to a broader push to expand Ethereum's protocol-level capabilities ahead of the planned Hegotá network upgrade in 2027. Ethereum upgrades are traditionally shipped as bundles, and candidate lists of this size are typically winnowed as technical review and audits progress.

Developers are currently evaluating a package of 66 Ethereum Improvement Proposals for Hegotá, several of which target on-chain privacy, an area the network has historically left to third-party solutions because its public ledger makes transaction data visible to anyone by default.

The centerpiece privacy proposal is EIP-8141, or "Frame Transactions," which would allow privacy pools to pay their own gas fees without relying on external relayers. Because each intermediary interaction creates a metadata trail that can expose sender information, removing that dependency is seen as a meaningful step toward native transaction privacy.

Complementing it, EIP-8182 would introduce a shared shielded pool for anonymous ETH and ERC-20 transfers, while EIP-8250 proposes keyed nonces to prevent observers from linking separate private transactions through nonce pattern analysis.

Of the proposals under review, only EIP-7805 (FOCIL), a censorship-resistance mechanism enforcing transaction inclusion lists, has been confirmed for Hegotá as of mid-August 2026. The remaining proposals face continued technical review and security auditing.

Hegotá is expected to follow the Glamsterdam upgrade, currently slated for Q4 2026, giving developers roughly a year to finalize the scope of the package, including which of the privacy proposals advance.

Source: Metaverse Post