Ethereum Developers Merge Patch for Bug That Put Staking Deposits at Risk

Ethereum Developers Merge Patch for Bug That Put Staking Deposits at Risk


For a week, a bug sat unresolved in Ethereum’s upcoming Glamsterdam upgrade that could have let a single operator walk away with ETH that never belonged to them. The flaw, found in code meant to separate block-building from validator staking, could have let someone register as a builder and then simply absorb a staking service’s validator deposit into their own balance if both used the same public key at the moment of the fork. 

Ethereum developers rejected a fix for it on Oct. 19, reopened the discussion days later, and finally merged the correction on Monday, Oct. 26. That wasn’t the only Glamsterdam news that week — four days earlier, on Oct. 22, the upgrade’s next test-network launch had already been pushed back over a separate, unrelated smart-contract security issue.

Bug stemmed from routing pending deposits by public key instead of withdrawal credentials in the Gloas fork.

Identical public keys for builders and staking services could merge deposits, letting operators withdraw combined ETH without creating validators.

Developers initially rejected, then merged a fix routing deposits by withdrawal credentials after a week of debate.

How the Bug Worked

The flaw lived in Glamsterdam’s “Gloas” fork, which separates two roles that are currently combined on Ethereum: builders, who assemble blocks of transactions, and validators, who stake ETH to secure the network and confirm those blocks. Both roles can deposit ETH, and Gloas is meant to track builder deposits and validator deposits separately going forward.

The bug sat specifically in how pending deposits—ones still waiting to be credited at the moment of the fork—get routed. According to GitHub issue #5735, opened Oct. 12 by researcher avsetsin, the draft rules credited deposits by public key rather than by withdrawal credentials, which determine where a deposit’s funds can eventually go. That created this sequence:

  1. An operator registers as a builder using a specific public key.
  2. A staking service deposits ETH to start a validator under that same public key.
  3. Under the draft rules, both deposits—the builder’s and the staking service’s—get credited to the builder.
  4. The operator can withdraw the combined funds, while no validator is ever created.

Because no validator exists in that scenario, the staking service has no way to produce the proof it would normally need to recover its money—the funds would simply be gone from its perspective, credited to someone else’s builder balance instead.

Which Protocols Were Flagged, and Why This Isn’t a Confirmed Exploit

Avsetsin’s report #5735 named three liquid-staking protocols as potentially affected, depending on how each handles its own deposit flow:

  • Lido PDG: A vault could lose its 1 ETH pre-deposit. Since compensation requires a validator proof that wouldn’t exist in this scenario, the operator’s 1 ETH guarantee would stay locked, and 31 ETH would remain staged without resolution.
  • Origin OETH: A missing initial deposit could block fresh balance verification for the entire strategy, since the cached strategy balance would still include the lost ETH.
  • Rocket Pool Saturn: Without a validator to prove against, immediate proof-based dissolution wouldn’t be possible; the remaining 31 ETH would have to wait out a dissolve timeout, and any shortfall would become operator debt.

Avsetsin was explicit that this analysis involved “quick AI research” and described the findings as “conditional code findings, not confirmed live exploits.” Two caveats stand out: existing pre-deposit checks that reject an earlier builder deposit could block the scenario entirely in practice, and no losses tied to this bug have been reported on any live network. The bug existed in draft upgrade code that hadn’t reached mainnet—this was a flaw caught and fixed before Glamsterdam shipped, not an incident that happened to real deposits.

The Fix, Rejected, Then Merged a Week Later

Avsetsin opened a pull request, #5736, on Oct. 12 alongside the bug report, proposing to route pending deposits by withdrawal credentials instead of by public key—keeping validator deposits with validators even when a builder uses the same key. 

The fix drew technical back-and-forth: reviewer michaelsproul questioned a retained fallback-deposit mechanism and asked about backward compatibility with Sepolia’s fork transition, while avsetsin defended the fallback as preserving pre-Gloas validator top-up behavior and shared before-and-after decision tables to make the case.

Despite that discussion, Ethereum consensus-specs maintainer Justin Traglia closed the PR on Oct. 19, citing insufficient client support for the change at the time, following discussion at Ethereum’s All Core Devs calls. The fix was reopened on Oct. 23 after further review, with avsetsin adding tests, and Traglia merged it on Monday, Oct. 26—a week after first rejecting it.

It’s worth being precise about timing here: Glamsterdam’s scheduled launch on the Hoodi test network was postponed four days earlier. That delay was announced separately on Oct. 22, after security firm ChainSecurity flagged a different risk in Glamsterdam’s gas-repricing changes (EIP-8037 and EIP-8038) that could let failed, supposedly retryable contract operations get permanently recorded as complete—an issue ChainSecurity tied to 13 real-world examples.

The upgrade has already run on the Sepolia test network, but a new Hoodi launch date will need to be set before a mainnet launch for Glamsterdam can be scheduled. The spec change is now part of Ethereum’s consensus specifications, though individual client teams still need to implement it in their own software before it’s ready for the next test run.

Also Read: Zcash Draft Seeks to Redirect 8% Mining Rewards From Grants to Network Reserve


Disclaimer: The information researched and reported by The Crypto Times is for informational purposes only and is not a substitute for professional financial advice. Investing in crypto assets involves significant risk due to market volatility. Always Do Your Own Research (DYOR) and consult with a qualified Financial Advisor before making any investment decisions.





Leave a Reply

Your email address will not be published. Required fields are marked *