Lido Warns Glamsterdam Fork Vulnerability Could Divert Staking Deposits to Builders

Ethereum staking protocols face risks of deposit hijacking during the upcoming Glamsterdam hard fork after core developers declined to implement protocol-level fixes. The timing edge case arises when builder and validator deposits sharing a public key remain queued at the fork transition, potentially crediting funds to builders via 0xB0 credentials rather than creating validators. Core developers rejected proposed specification adjustments because Glamsterdam had already activated on Sepolia and Hoodi client releases were underway, leaving liquid staking protocols and institutional operators responsible for implementing application-level safeguards ahead of the October 26 Hoodi testnet launch.