Ethereum Fixes Glamsterdam Bug That Could Have Sent Staking Deposits to Builders
Ethereum developers fixed a flaw in the upcoming Glamsterdam upgrade that could have sent staking deposits to block builders instead of their intended destination. They first rejected the change, then reconsidered it as testing delays gave them more time to inspect the issue.
Key takeaways
- A Glamsterdam bug could have sent Ethereum staking deposits to block builders.
- Ethereum developers initially rejected the change before reversing course.
- Testing delays gave developers more time to examine and fix the flaw.
- The report does not say that deposits were actually misdirected or provide a deployment date.

Ethereum developers have fixed a bug in the upcoming Glamsterdam upgrade that could have routed staking deposits to block builders. The team initially rejected the proposed change, but reversed course after delays in testing created more time to examine the flaw.
The report does not specify how many deposits could have been affected or when the fix will be deployed. The key development is that the issue was caught and addressed before Glamsterdam goes live.
How could the Glamsterdam bug affect staking deposits?
The flaw involved where staking deposits could be sent: instead of reaching their intended destination, they could have gone to builders, the participants responsible for assembling blocks of Ethereum transactions. The available report does not describe the technical cause or say that any deposits were actually misdirected.
For people who stake ETH, the reported risk was tied to the upcoming upgrade, not a confirmed loss of funds. The fix was made during development and testing.
Why did developers change their decision?
Developers initially rejected the change, then revisited it as testing delays gave them more time to investigate. That sequence matters: a delay can be frustrating, but in this case it also gave the team more opportunity to examine a potentially consequential flaw before launch.
Glamsterdam has already faced testing setbacks, including a Hoodi testnet activation canceled after researchers raised concerns about a separate contract risk. Those events make this deposit-routing fix part of a broader pattern in the upgrade’s testing: developers are still finding issues that warrant review before activation. The earlier Hoodi test delay over contract risk provides context, but it concerned a different problem.
What should ETH stakers watch for next?
The report confirms a fix, but does not give a deployment date or technical details. Stakers should distinguish this development-stage bug from an active incident: no misdirected deposits are reported. The practical next signal is whether the fix is incorporated and validated in Glamsterdam’s ongoing testing before the upgrade is activated.
Frequently asked questions
What was the Ethereum Glamsterdam bug?
A flaw in the upcoming upgrade could have routed staking deposits to block builders instead of their intended destination. Developers fixed it during the development process.
Were any Ethereum staking deposits sent to builders?
The report does not say that any deposits were misdirected. It describes a potential bug in the upcoming Glamsterdam upgrade and says developers fixed it.
When will the Glamsterdam fix go live?
The report does not provide a deployment date. The fix needs to be incorporated and validated as Glamsterdam continues through testing.
Live on-chain data from our sister sites: