Ethereum Developers Tap Dima to Coordinate Lido Operators’ Hoodi Client Rollback

At the Oct. 22 developer call, Dima, a Lido representative, was tasked with coordinating with Lido operators on moving their clients back to pre-Amsterdam versions.

The task was recorded at the Oct. 22 All Core Developers Execution call. It concerns Hoodi client software and specifies no Lido DAO vote or contract-level change. The assignment followed the removal of Hoodi’s Oct. 26 activation from the Glamsterdam test schedule; developers have not set a replacement time.

Hoodi’s revised configuration removes the planned Amsterdam and Gloas activation entries, along with a gas-limit schedule that would have raised the testnet limit to 200 million gas. The settings change does not erase blocks already recorded on Hoodi.

Developers postponed the test while examining how EIP-8037, which changes the gas cost of creating state, affects smart contracts already deployed on Ethereum mainnet. No mainnet activation date has been set, and Ethereum mainnet users and Ether (ETH) holders do not need to take action.

Hoodi node and validator operators were advised to check that both execution- and consensus-layer clients use the revised configuration before Oct. 26.