BREAKING
Vercel Resolves OpenTelemetry Blind Spot in AI SDK With New Inference Duration Histogram ● YBUSDT Approaches Potential Turning Point Amid Signs of Returning Buying Interest ● SEC to Resume Processing Registration Applications ● Rarible Unveils Rebuilt Cross-Chain Marketplace Featuring High-Speed Trading and New Rewards System ● Niko Bellic Appears in GTA 6: Voice Actor Michael Hollick Returns for Late-Game Cameo ● Ant International’s Alipay+ Connects Over 50 Global E-Wallets to Brazil’s Pix to Revolutionize Cross-Border Payments ● Federal Investigation Links Ransomware Negotiation Executives to ShinyHunters Hacking Group and FBI Data Breach ● White House National Cyber Director Sean Cairncross to Step Down Amid Transitioning Political Landscape and Unexplained Tech Outages ●
Ethereum Ecosystem

Glamsterdam on Hoodi Postponed

Photo: Documentation / News Illustration

The decision to delay the rollout was reached during All Core Developers Execution (ACDE) meeting #248. Core developers determined that additional time is required to thoroughly investigate the interactions between EIP-8037 and existing mainnet smart contracts. Because testnets serve as the final proving ground before mainnet deployments, ensuring that proposed upgrades do not introduce unforeseen edge cases or vulnerabilities with complex smart contract logic is critical for maintaining network security and stability.

By halting the current schedule, developers have removed both the Amsterdam execution layer activation and the Gloas consensus layer activation from the upcoming Hoodi timeline. Furthermore, this postponement eliminates the planned gas-limit schedule that would have temporarily raised Hoodi’s network gas limit to 200 million at the exact same epoch. Network architects emphasize that this action effectively rolls back the configuration for this specific upcoming upgrade cycle, though it does not in any way revert or alter Hoodi’s historical chain data. The October 26 target has been entirely scrubbed from the active configuration, leaving no replacement activation epoch or timestamp in place. The formal rescheduling of the replacement upgrade will be communicated to the community at a later date once further analysis of EIP-8037 is complete.

Hoodi Node and Validator Operators

For individuals and organizations operating a Hoodi node or validator, immediate attention is required to review both execution and consensus layer client setups. Operators must verify that their software configurations reflect the postponed activation well before the previously anticipated October 26 date. Any custom network configurations or local software builds that still hardcode or schedule the Glamsterdam upgrade at the original timestamp must be manually updated to align with the revised Hoodi network configuration.

It is critical that operators do not rely on the client release tables published in earlier announcements as confirmation that those software versions incorporate the latest postponement. Instead, infrastructure runners must closely follow official release notes and instructions provided by their respective client development teams for the revised Hoodi schedule. Additionally, validator operators should carefully examine any specific guidance pertaining to their validator clients and external builder infrastructure to prevent unexpected validation errors or desynchronization once the network moves past the old epoch marker.

Client Releases

New and updated client releases that properly incorporate the postponed Hoodi activation configuration are expected to be rolled out by development teams. Node runners are advised to update both their execution layer and consensus layer clients exclusively to software versions whose official release notes explicitly confirm that the October 26 Glamsterdam activation on Hoodi has been removed or disabled.

When running a validator, administrators must ensure that both the consensus layer beacon node and the underlying validator client are updated simultaneously to maintain compatibility. Furthermore, builder and validator tooling guidance will be distributed as soon as it is officially confirmed for the delayed Hoodi activation path. Operators who rely on external block-building infrastructure or third-party relay services should remain vigilant and follow the specific instructions issued by their tooling providers to ensure a seamless operational transition.

Application Developers and Mainnet Users

Application developers who have built testing pipelines around the Hoodi testnet must adjust their schedules and avoid planning any protocol-level testing around an October 26 Glamsterdam activation. Because the core development team is taking extra precautions to evaluate EIP-8037 interactions, a revised Hoodi activation timeline will be announced independently once technical assessments conclude.

It is important to note that this announcement pertains strictly to the Hoodi testnet environment. The postponement does not establish a Glamsterdam mainnet activation date, nor does it impact the mainnet operational status in any way. Consequently, no action is required from general Ethereum mainnet users, decentralized application users, or ETH holders as a direct result of this temporary testnet delay.

What is your reaction to this story?

Nana

Writer and contributor at Bitcoin 98.

Comments (0)