Ethereum Developers Merge Glamsterdam Fix to Keep Validator Deposits Out of Builder Accounts
By Unchained
AI summary of the source article
Ethereum developers merged a fix on Oct. 26 for a Glamsterdam upgrade bug that could have credited validator deposits to builder accounts. The update ensures builder accounts are funded only by deposits carrying builder credentials.
Why it matters
Under the prior fork rules, "If both deposits are pending at the fork, both amounts go to the builder. The operator can withdraw the protocol’s funds."
Key facts
- Ethereum developers merged a fix on Oct. 26 to prevent pending validator deposits from being credited to builder accounts during the Glamsterdam upgrade.
- The pull request, written by Lido Chief Protocol Architect George Avsetsin, requires Gloas to check withdrawal credentials on deposits pending at fork activation.
- The fix was previously closed on Oct. 19 due to lack of client support, then reopened after the upgrade's Oct. 26 Hoodi testnet activation was unscheduled.
Source excerpt · Unchained
The change keeps validator deposits pending at the Gloas fork from being credited to a builder that shares the same key, a scenario its author called a conditional finding, not a live exploit. The post Ethereum Developers Merge Glamsterdam Fix to Keep Validator Deposits Out of Builder Accounts appeared first on Unchained .