Skip to content
Crypto.world

The Ledger

Ethereum Developers Merge Fix for Glamsterdam Deposit Flaw

Ethereum developers merged a consensus-specification change addressing a draft Gloas deposit-routing flaw that could have credited a validator deposit to a builder with the same public key. The change separates validator and builder deposit handling, while the Ethereum Foundation has postponed Glamsterdam’s Hoodi activation without setting a replacement date.

Ethereum Developers Merge Fix for Glamsterdam Deposit Flaw

“The operator can withdraw the protocol’s funds.”

avsetsin, author of Ethereum consensus-specs issue #5735

Ethereum developers merged a fix on Monday, October 26, for a Glamsterdam deposit-routing flaw that could have sent staking-service ETH to a block builder instead of a new validator. The change updates the consensus specifications for Gloas, Glamsterdam’s consensus-layer fork, and separates pending builder deposits from validator deposits during the fork transition. The issue arose in draft rules, before the upgrade reached Ethereum mainnet.

How one public key could redirect a deposit

The flaw involved a builder and a validator using the same public key. Under the draft onboarding rule, once a pending deposit registered a builder, later deposits tied to that key could increase the builder’s balance regardless of their withdrawal credentials. A staking protocol’s validator deposit could therefore be routed to a builder controlled by the operator.

In issue #5735, opened on October 12, avsetsin described a possible sequence: an operator queues a valid builder deposit, then a staking service funds a validator deposit for the same key. If both deposits remain pending when Gloas activates, the draft rule could credit both to the builder. Without a validator record, the staking service might also lack the proof its process requires to verify the validator or recover funds.

The issue named Lido’s Predeposit Guarantee, Origin’s OETH and Rocket Pool Saturn as protocols that could face knock-on accounting or recovery problems, depending on their deposit flows. Avsetsin cautioned that the protocol analysis was preliminary, could contain errors and did not establish a live attack. The issue says existing pre-deposit checks that reject an earlier builder deposit could prevent the scenario.

New rules keep validator deposits in their queue

Pull request #5736 routes pending deposits by withdrawal credentials during Gloas onboarding. Validator deposits remain in the validator queue even when a builder uses the same key; valid builder deposits can register or add funds to the builder. The revised handling lets the two roles keep separate records instead of allowing the first builder deposit to dictate where later deposits go.

The patch also adds routing and deposit-order regression tests. Its author says the change aligns fork onboarding with the separate builder and validator registries specified for the upgrade. The revised rules preserve existing validator top-up behavior in cases where a deposit does not create a builder.

A rejected proposal returns for more testing

Developers first closed the pull request on October 19. Consensus-specifications maintainer Justin Traglia wrote that “There was not enough support from clients to make this change at this time.” The proposal reopened on October 23 after further review, and reviewers requested additional tests before approval.

Avsetsin added tests covering deposit combinations on October 23. Reviewer potuz wrote that the change made sense but added, “I could not find any way of exploiting this, which is not to say that there isn't any.” Traglia merged the update on October 26, with GitHub showing 19 checks passed.

Hoodi’s next date remains unset

The merge lands while Glamsterdam’s public test schedule is already in flux. The Ethereum Foundation postponed the Hoodi testnet activation on October 22, citing a separate investigation into how EIP-8037 interacts with existing mainnet smart contracts. The planned October 26 activation was removed, and the Foundation had not set a replacement date.

The Foundation’s Hoodi notice says the postponement does not set a Glamsterdam mainnet activation date. That date remains unscheduled, while the Hoodi testnet waits for a revised activation time.

Sources

  1. Original source Ethereum consensus-specs on GitHub · page 1 github.com

Other pages read

  1. Ethereum consensus-specs on GitHub · page 2 github.com
  2. Ethereum Foundation blog.ethereum.org

Related stories

Explore

More articles