Lido engineering lead warns Glamsterdam of a potential staking-deposit hijacking risk during the upgrade transition
BIBIBI
AT A GLANCE
The Lido engineering lead said that during the Ethereum Glamsterdam hard fork transition, there may be a risk of front-running and hijacking staking deposits.
Article
Lido engineering lead warns: Ethereum Glamsterdam upgrade transition carries a risk of staking-deposit hijacking
PANews October 20 reported, according to Crypto Briefing, that Lido engineering lead Dima Gusakov disclosed that during the Ethereum Glamsterdam hard fork transition, delegated staking protocols face a risk of front-running attacks.Glamsterdam will introduce builder deposits using 0xB0-prefixed withdrawal credentials. Before and after the fork, these deposits will share a deposit queue with validator deposits. Malicious node operators could use this to preempt stakers' funds, causing them to be credited to the attacker's builder account, while the corresponding validators cannot be activated. The related fix proposal (consensus-specs #5735) has been closed as “not planned,” and defenses will require each staking protocol to conduct pre-deposit checks itself.Glamsterdam will be activated on the Hoodi testnet in the early hours of October 27, but the text is truncated...
According to Crypto Briefing, Lido engineering lead Dima Gusakov disclosed that during the Ethereum Glamsterdam hard fork transition, delegated staking protocols face a risk of front-running attacks.
02
Glamsterdam will introduce builder deposits using 0xB0-prefixed withdrawal credentials.
03
Before and after the fork, these deposits will share a deposit queue with validator deposits.
04
The original text states that malicious node operators could use this to preempt stakers' funds, causing the funds to be credited to the attacker's builder account and preventing the corresponding validators from being activated.
05
The related fix proposal, consensus-specs #5735 has been closed as “not planned.”
06
The original text states that defenses require each staking protocol to conduct pre-deposit checks itself.
07
Glamsterdam will be activated on the Hoodi testnet in the early hours of October 27, but the end of the original text is truncated.
AI-assisted interpretation
The following is analysis, separate from reported facts. Verify important claims independently.
Simply put, during the upgrade transition, the types of deposits will enter the same queue. Dima Gusakov warned that malicious node operators could exploit the processing order to act first, causing staked funds to be credited to the attacker's builder account and preventing the originally corresponding validators from starting. Since the related fix proposal has been closed, each staking protocol needs to conduct its own pre-deposit checks.
Why it matters to readers
If this risk materializes, stakers' funds may be incorrectly credited to the attacker's account, and validators may also be unable to activate. Therefore, whether delegated staking protocols have adequate deposit checks in place merits attention.
New users of delegated staking services should monitor whether the protocol they use has announced pre-deposit check measures, and whether any anomalous deposit events occur during the Hoodi testnet upgrade; the original text does not prove that an attack has already occurred.
Risks and unknowns
The material is PANews's paraphrase of Crypto Briefing's report and statements by Dima Gusakov; it does not provide the full original technical disclosure.
It remains unclear which delegated staking protocols are affected or have deployed defensive measures.
The original text does not state whether the attack has actually occurred.
The original text is truncated at the end; the Hoodi testnet activation schedule and subsequent content are incomplete.
Related Developments
Loading event timeline…
“October 27”The year is not specified in the main text.
It is not possible to confirm consensus-specs # based solely on the available materials. 5735 Alternative remediation arrangements after closure.
Related concepts
Hard Fork
A protocol change that is not backward-compatible and may cause the blockchain to split into two independently operating paths if there is disagreement.
