An Update Regarding Lido and the Glamsterdam Upgrade on Hoodie
We want to reassure our community right away that the recent delay of the testnet upgrade will not impact the mainnet Lido protocol in any way. If you currently hold stETH or wstETH, you do not need to take any action at all.
During the ACDE #248 meeting yesterday, Ethereum core developers chose to pause the scheduled Glamsterdam upgrade on the Hoodi testnet. This postponement was implemented to provide ample time for a deeper look into how EIP-8037 and EIP-8038 might interact with mainnet contracts. For more details on this decision, please visit https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay
The Hoodi contracts for Lido had actually already been updated in preparation for the initial October 26 activation date. Because of this, contributors are currently organizing a Hoodi vote aimed at reversing the fork-specific modifications. This rollback will ensure that the testnet remains fully functional until a fresh date for the upgrade is established.
To manage this reversion smoothly, Lido DAO contributors are actively collaborating with both Lido Node Operators and the wider Ethereum ecosystem. If you are currently operating a Hoodi node or a validator, it is important that you review your Execution and Consensus Layer clients before October 26 to find the latest instructions regarding the delayed launch.
Security remains a top priority, and Lido contributors have been rigorously evaluating EIP-8037 alongside Lido contracts since June. Thus far, this screening has uncovered no disruptive effects on the essential contracts of the protocol. Furthermore, ChainSecurity has independently verified these safe findings. As the Ethereum core devs continue their wider investigation, our internal review process will proceed concurrently.
We want to reassure our community right away that the recent delay of the testnet upgrade will not impact the mainnet Lido protocol in any way. If you currently hold stETH or wstETH, you do not need to take any action at all.
During the ACDE #248 meeting yesterday, Ethereum core developers chose to pause the scheduled Glamsterdam upgrade on the Hoodi testnet. This postponement was implemented to provide ample time for a deeper look into how EIP-8037 and EIP-8038 might interact with mainnet contracts. For more details on this decision, please visit https://blog.ethereum.org/2026/10/22/glamsterdam-hoodi-delay
The Hoodi contracts for Lido had actually already been updated in preparation for the initial October 26 activation date. Because of this, contributors are currently organizing a Hoodi vote aimed at reversing the fork-specific modifications. This rollback will ensure that the testnet remains fully functional until a fresh date for the upgrade is established.
To manage this reversion smoothly, Lido DAO contributors are actively collaborating with both Lido Node Operators and the wider Ethereum ecosystem. If you are currently operating a Hoodi node or a validator, it is important that you review your Execution and Consensus Layer clients before October 26 to find the latest instructions regarding the delayed launch.
Security remains a top priority, and Lido contributors have been rigorously evaluating EIP-8037 alongside Lido contracts since June. Thus far, this screening has uncovered no disruptive effects on the essential contracts of the protocol. Furthermore, ChainSecurity has independently verified these safe findings. As the Ethereum core devs continue their wider investigation, our internal review process will proceed concurrently.