Lido Engineer Flags Staking Deposit Hijack Risk at Glamsterdam

The significance here is less the attack vector itself than the process signal: a researcher flagged a deposit-hijack path, and the relevant consensus-specs issue was closed as not planned, leaving mitigation to pre-deposit checks rather than protocol-level changes. That shifts responsibility toward staking operators and deposit tooling, not just Lido, since any staker relying on default deposit flows could inherit the exposure. With no exploit or loss reported, this remains a design-review question rather than an incident. Worth watching is whether the pre-deposit-check defense gets formalized in tooling, and whether the closed issue is revisited as Glamsterdam work proceeds.