The Ethereum community has released a key Ethereum Improvement Proposal (EIP) aimed at significantly reducing the consensus layer block retention window from approximately 146 days to roughly 36.4 days . This proposed change represents a non-forking informational modification that does not require a network upgrade or hard fork to implement . The proposal is designed to address the growing challenge of blockchain data expansion, which has been placing increasing hardware demands on node operators . By shortening the retention window, the EIP aims to significantly lower the bandwidth, disk usage, and time required for data backfill after checkpoint synchronization, helping to preserve Ethereum's decentralization by making node operation more accessible . This technical improvement reflects ongoing efforts to optimize Ethereum's infrastructure and improve node operational efficiency.

This page contains third-party content and does not constitute any advice, nor does it represent Gate's endorsement of such views. For details, please see disclaimer.

ETH-0.20%

2
12
1.71k

Add a comment

Comment

SeedPhraseAmnesia

2026-08-21

A non-fork, information-level modification sounds like a low-cost optimization, but could it actually cause compatibility issues for older nodes during implementation?

00View Original

LiquidSniper

2026-08-19

The 36-day proposal is quite practical, significantly reducing pressure on node storage, but hopefully synchronization efficiency won’t be compromised.

00View Original

OptionWave

2026-08-19

Lower disk usage is certainly a good thing, but with 146 days reduced to 36 days, will querying historical data become more difficult? Light clients and archive nodes shouldn’t be affected, right?

00View Original

SpikeGuard

2026-08-19

Finally, someone’s addressing full-node disk requirements. Each sync used to require downloading hundreds of GB—seriously discouraging. More changes like this, please.

00View Original

MacroScope

2026-08-19

As a node operator, this change is great—it can save a significant amount of bandwidth and disk space. I just don't know whether it will have any side effects on snapshot services.

10View Original

DividendRetire

2026-08-19

Cutting the retention window to 36 days, my first reaction was: Who will be responsible for preserving the data from before that? Does this mean that, going forward, checking old blocks will only be possible through third-party services?

10View Original

DepositBouncer

2026-08-19

The EIP’s approach is quite clear: trade time for space. After syncing the checkpoint, you can simply replay the history, but the prerequisite is having enough archive nodes on the network; otherwise, gaps in the historical data would be problematic.

10View Original

TwoFactorZen

2026-08-19

Optimizing infrastructure is a good thing, but lowering barriers shouldn’t come at the cost of making decentralization dependent on centralized indexers. Hopefully, supporting solutions will follow.

10View Original

GasWizard

2026-08-19

First Review

The gap between 36 days and 146 days is quite large. It feels like they’re betting that everyone will perform regular synchronization. However, the technical details weren’t explained, so let’s wait and see what the community discussion says.

00View Original

Ethereum Community Proposes Reducing Consensus Layer Block Retention Window to 36 Days

Trending Topics

#OneGateWitnessProgram

#GT Burns Nearly 2M Tokens in Q3

#CFTC Proposes New “Crypto Asset Market” Category

#Bitmine Adds More ETH, Holdings Top 6.01M

#Solana Spot ETFs See $9.24M Net Outflow

#BTC Breaks Through $86,000

#USSeptemberJobs29K

#Nvidia Hits Record High

#HYPE Treasury Holdings Top $3.2B

#Three LaunchpoThree Launchpools Live Simultaneously, Share Millions in Airdropsols Live Simultaneously, Share Millions in Airdrops