Ethereum developers have patched a bug in the forthcoming Glamsterdam upgrade that could have routed staking deposits to block builders, according to an account of the fix. The same developers initially turned the patch down before reversing course as testing slipped.
The flaw lived in code tied to Glamsterdam, the upgrade package now moving through Ethereum's testing pipeline. Left alone, it could have exposed staking deposits to block builders — the intermediaries that assemble blocks and decide which transactions and payloads they carry. The reversal came only after delays in testing handed developers extra time to look at the problem.
Inside the patch
The fix went in against the Glamsterdam upgrade, not a live network release. That distinction matters: Glamsterdam isn't running on mainnet, so the bug was caught while the code was still under review rather than after users had money on the line. The change targets a path where staking deposits could have ended up with block builders instead of where they belonged.
Developers first rejected the patch. They then changed their minds. The exact reasoning behind the initial rejection wasn't spelled out in the available account, and no named developer has put their comments on the record yet.
Why the delay helped
Testing delays are usually bad news for an upgrade schedule. This time they worked in the code's favor. The extra window let developers take a harder look at the flaw in Glamsterdam and confirm what the fix needed to do. A rushed review might have missed it, or waved through a patch that didn't fully close the hole.
Glamsterdam itself is still in the testing phase, and the schedule has already moved. That's not unusual for Ethereum upgrades — the pipeline is long and the review process is deliberately slow — but it does mean the deposit bug surfaced at a point where the network could still absorb the cost.
What block builders have to do with it
Block builders sit between users and validators. They bundle transactions and decide what goes into a block, and in Ethereum's current setup they also handle payloads tied to staking. A flaw that sends deposits their way isn't a theoretical curiosity — it's a routing problem with real funds behind it.
Ethereum's staking deposits are the entry point for anyone who wants to lock ETH and run a validator. If those deposits can be redirected by a bug, the trust model around staking gets shaky. The patch closes that path before Glamsterdam ships.
The unanswered question
What isn't clear yet is how the bug got into the Glamsterdam code in the first place, and whether the initial rejection of the fix points to a disagreement among developers over how serious it was. Neither has been addressed publicly.
Glamsterdam remains in testing, with no firm date for its mainnet activation in the available account. The next concrete step is the upgrade's continued run through the test pipeline, where developers will be watching for anything else the delay might have surfaced.
