$ETH {currencycard:futures}(ETHUSDT) ‌ EIP PROPOSE | CryptoJourney1 on Gate Square

‌ EIP PROPOSES CUTTING NODE RETENTION WINDOW – 146 DAYS TO JUST 36 DAYS

Ethereum developers have just proposed a major improvement: reducing the consensus layer block retention window from approximately 146 days to just 36.4 days.

The problem: Ethereum's historical state and block data continue to expand, making node operation hardware requirements increasingly challenging.

The solution: As a non-fork informational change, the proposal would significantly reduce the backfill overhead for new nodes after checkpoint synchronization.

Why it matters: This change would help preserve Ethereum's decentralized foundation by lowering the hardware barrier to running a node.

The debate: Community members are discussing whether this is enough to address long-term scalability concerns as Ethereum continues to grow.

👇 Do you run an Ethereum node? Type YES or NO.
#GateEventPointsSystemLaunched

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+1.24%

13
2.44k

Add a comment

Comment

BalancedHand

2026-08-21

36.4 days is exactly one month plus a few days—pretty aggressive. It feels like the developers are determined to reduce synchronization costs.

00View Original

MemeArchaeologist

2026-08-21

I don’t run a node, but this feels very reasonable. Ordinary users should use light wallets; fully syncing a node is too painful.

00View Original

OnChainGeologist

2026-08-20

It is recommended to pair it with a decentralized historical data layer; otherwise, once the window is shortened, data accessibility will immediately deteriorate. At the same time, nodes could be offered an optional archival mode, allowing those willing to store data to continue doing so, while those unwilling would retain only 36 days, so everyone can choose what suits them without a one-size-fits-all approach affecting the ecosystem.

00View Original

GasStationAtt

2026-08-20

The problem is that many DApps need to query historical events, but nodes don’t store them. Are we supposed to have enterprises provide APIs for everything? Then can we still talk about privacy and decentralization?

00View Original

GasFeeFighter

2026-08-19

This proposal treats the symptoms, not the root cause; the real issues are statelessness and state expiration. Looking forward to the EIP in the next phase.

00View Original

VolumeRatioWatcher

2026-08-19

Support reducing the burden, but please preserve on-chain history.

00View Original

PositionRuler

2026-08-19

This change essentially outsources responsibility for historical data to specialized nodes, while ordinary nodes only handle the latest state. The approach makes sense.

10View Original

TrendlineArtist

2026-08-19

I’m already running a node, and honestly, disk space is definitely tight. Reducing it from 146 days to 36 days would save me at least quite a bit of space. I support this.

10View Original

MarketCapEstimator

2026-08-19

Lowering the hardware barrier is a good thing, but I think the more fundamental solution is to slim down the state data as well; otherwise, nodes will still become increasingly difficult to run.

10View Original

SharpeStar

2026-08-19

I’m just worried that once historical data is discarded, on-chain audits and compliance analysis will become dependent on centralized service providers, which contradicts decentralization.

10View Original

Trending Topics

#GateAtTOKEN2049

#LedgerLossesNear90Million

#GateWCTCS9GlobalTradingCompetition

#CRCLLeadsCryptoStocks

#EthereumUpOver71%inQ3

#GateEventMarketVolumeHits73M

#USOpensRussianDieselImports

#GateNetInflowRanks3rd

#SimpleEarnUSDTLimitedTime11%APR

#BTC Pulls Back to 81000