Glamsterdam deposit bug fixed: what ETH stakers need to know

A Glamsterdam spec fix merged October 26, 2026 keeps validator deposits separate from builder deposits at the fork. No losses have been reported.

Share
stakefish banner: Glamsterdam bug in staking deposits patched

Ethereum developers fixed a flaw in the Glamsterdam spec that could have credited a pending staking deposit to the wrong account. The fix was merged on October 26, 2026. The flaw never reached mainnet, and no losses have been reported.

Key facts

  • Upgrade: Glamsterdam (Gloas consensus layer)
  • Risk: pending validator deposits credited to a builder account at the fork
  • Reported: October 12, 2026, in consensus-specs issue #5735 (GitHub)
  • Fix: consensus-specs PR #5736, merged October 26, 2026 (GitHub)
  • Losses reported: none
  • Next step: client teams implement the fix

What was the Glamsterdam deposit bug?

Glamsterdam adds enshrined proposer-builder separation (ePBS), which lets block builders register onchain with a deposit. At the Gloas fork, deposits still waiting in the queue are sorted into builders and validators. The original spec sorted them by public key. If a builder deposit for a key sat in the queue ahead of a staking service’s validator deposit for the same key, and both were still pending at the fork, both amounts would go to the builder, whatever the validator deposit’s withdrawal credentials. The staking service could lose its normal recovery path, and the builder could potentially withdraw the funds. After the fork, builder and validator deposits take separate paths, so the risk was limited to deposits pending at the moment of the fork.

How was it fixed?

Pull request #5736, “Separate builder and validator deposits at the Gloas fork,” routes pending deposits by withdrawal credentials, so validator deposits stay in the validator queue even if a builder uses the same key. It was first closed on October 19 over limited client-team support, then reopened with more tests on October 23 and merged on October 26.

Does this affect the Glamsterdam timeline?

Client teams still need to implement the fix. Separately, the Glamsterdam launch on the Hoodi testnet was postponed on October 22 over EIP-8037, not over this bug.

Why it matters for stakers and institutions

Deposits that are still pending when a fork activates are where edge cases like this appear. Staking providers and institutions with large pending deposits around Glamsterdam should follow client release notes.

Read our Glamsterdam explainer for institutional stakers, or learn about Ethereum staking with stakefish.

Frequently asked questions

What was the Glamsterdam deposit bug?

A conditional flaw in the Glamsterdam spec. If a builder deposit for a public key was queued ahead of a validator deposit for the same key, and both were pending when the Gloas fork activated, both amounts would be credited to the builder, whatever the validator deposit’s withdrawal credentials.

Were any funds lost?

No losses have been reported, and the flaw never reached mainnet.

How was the bug fixed?

Consensus-specs pull request #5736, merged October 26, 2026, separates builder and validator deposits at the Gloas fork by routing pending deposits by withdrawal credentials.

Does this delay Glamsterdam?

Client teams still need to implement the fix. Separately, the Hoodi testnet launch was postponed on October 22, 2026 over EIP-8037, not over this bug.

Sources