TREE NEWS reports: Lido engineering lead Dima Gusakov warned that delegated staking protocols face front-running attacks during Ethereum’s Glamsterdam hard fork transition. Glamsterdam introduces builder deposits using 0xB0-prefixed withdrawal credentials that share the deposit queue with validator deposits around the fork, letting malicious node operators capture staker funds into their builder accounts and preventing the corresponding validators from activating. The fix proposal, consensus-specs #5735, was closed as “not planned,” so staking protocols must run their own pre-deposit checks.
Lido Engineer Warns of Staking Deposit Hijack Risk During Ethereum Glamsterdam Transition
The closed spec fix shifts the burden of defense onto staking protocols themselves, a meaningful operational change for any liquid staking or delegated staking operator preparing for the fork. The risk is narrow in mechanism but sharp in consequence: shared queue ordering around the transition lets a malicious node operator divert funds into builder accounts while validators never activate. Whether protocols actually implement pre-deposit checks before the fork window, and how the shared queue is sequenced, is the open question worth watching.
Generated by AI for reference only.
Share on WeChat
Open WeChat → Scan → then tap "…" to send to a chat or Moments.
Tap "…" in the top-right corner to send to a chat or share to Moments.