Ethereum developers have successfully patched a vulnerability in the forthcoming Glamsterdam upgrade that risked redirecting ETH intended for new validators directly to block builders.
This fix was integrated into Ethereum’s consensus specifications on October 26, following a reversal by developers who had previously dismissed the proposal a week prior. The vulnerability centered on pending deposits awaiting processing when the network transitions to the updated rules introduced by Glamsterdam.
There have been no documented financial losses stemming from this bug. The patch modifies how Ethereum processes deposits specifically for the upcoming upgrade, rather than affecting any transactions already finalized on the main network.
How the Deposit Flaw Could Have Redirected ETH
With the Glamsterdam upgrade, the responsibilities of block building and block proposal will be divided. While validators stake ETH to maintain network security, builders group transactions together into blocks. The upgrade establishes a distinct deposit mechanism for builders, even though both functions are permitted to share an identical public key.
Ethereum researcher avsetsin described a scenario where an operator initially deposits ETH to set up a builder. Afterward, a staking service might transfer ETH to spin up a validator utilizing that exact same key. If both transactions were still pending at the time of the upgrade, the initial rules could have erroneously funneled the staking service’s funds into the builder’s account balance.
Consequently, the operator would have been able to withdraw the money without actually establishing the intended validator. This outcome also would have deprived the staking service of the validator records required for specific recovery verifications. In a GitHub report dated October 12, avsetsin cautioned that “the operator can withdraw the protocol’s funds.”
While the researcher looked into potential exposure affecting Lido, Origin, and Rocket Pool, they emphasized that these assessments were preliminary. “These are conditional code findings, not confirmed live exploits,” noted avsetsin, adding that pre-existing safety checks implemented by certain platforms might have blocked the vulnerability.
Developers Reverse an Earlier Decision
Initially, the suggested fix lacked the necessary backing. Justin Traglia, an Ethereum consensus-specifications maintainer, closed the issue on October 19 following talks with client developers. “There was not enough support from clients to make this change at this time,” Traglia stated.
Even so, a scheduling shift for Glamsterdam’s subsequent testnet release afforded the team an opportunity to reconsider the patch. On October 23, contributor Dmitry Gusakov urged the developers to re-evaluate the issue due to the altered upgrade timetable, prompting Traglia to reopen the discussion that very day.
Following the addition of regression tests by avsetsin to evaluate deposit behaviors across various sequencing orders, Traglia merged the updated code into the consensus specifications on October 26. The new patch directs deposits based on their specific withdrawal credentials, which clarify the deposit category and designate the destination for withdrawals.
Under these updated guidelines, validator deposits stay safely in the validator queue even if a builder utilizes the same public key. Meanwhile, builder deposits travel along a separate path. Ethereum client teams are now tasked with incorporating these protocols into the software utilized by network participants.
Hoodi Delay Leaves Mainnet Timetable Open
Glamsterdam went live on the Sepolia test network on October 6, giving developers a chance to review its modifications prior to a broader deployment. A subsequent test on Hoodi was slated for October 26, but the core team chose to delay that rollout.
In an October 22 statement, the Ethereum Foundation explained that more time was required to study how an unrelated gas-accounting proposal, EIP-8037, affects current smart contracts. This issue was entirely separate from the validator deposit bug. The foundation indicated that a new schedule for Hoodi would be released following additional analysis.
At present, a rescheduled Hoodi activation date and an official Ethereum mainnet launch date remain unannounced. Node operators are advised to adhere to updated client release guidelines while developers press on with testing the guidelines for validators and builders ahead of the official release.
ALSO READ: NBA Signs CFTC Deal, Names Kalshi and Polymarket as Partners



