🛠 $ETH | Postponing a testnet fork: prudent caution or lost momentum?
Geth v1.17.10 cancels the Amsterdam activation on the Hoodi testnet, which had been scheduled for Oct 26, 2026, 17:42:48 UTC; a new date will be set in a future release, and other networks are unaffected. Hoodi node operators running v1.17.9 must upgrade before then. The same release makes snap sync switch to snap/2 automatically once Amsterdam is active, with flags to force a protocol, and optimizes DUP/SWAP dispatch in the interpreter. One reading sees a disciplined pause to get the fork right; another sees a schedule slipping while client work continues.
Why it matters: Testnet forks are the rehearsal for mainnet changes, so a postponed activation shifts the timeline for operators and client teams alike.
💬 Is delaying a testnet fork the safer engineering choice, or does it signal coordination problems worth scrutinizing?
Source: GitHub release https://github.com/ethereum/go-ethereum/releases/tag/v1.17.10
#Ethereum #Blockchain
Geth v1.17.10 cancels the Amsterdam activation on the Hoodi testnet, which had been scheduled for Oct 26, 2026, 17:42:48 UTC; a new date will be set in a future release, and other networks are unaffected. Hoodi node operators running v1.17.9 must upgrade before then. The same release makes snap sync switch to snap/2 automatically once Amsterdam is active, with flags to force a protocol, and optimizes DUP/SWAP dispatch in the interpreter. One reading sees a disciplined pause to get the fork right; another sees a schedule slipping while client work continues.
Why it matters: Testnet forks are the rehearsal for mainnet changes, so a postponed activation shifts the timeline for operators and client teams alike.
💬 Is delaying a testnet fork the safer engineering choice, or does it signal coordination problems worth scrutinizing?
Source: GitHub release https://github.com/ethereum/go-ethereum/releases/tag/v1.17.10
#Ethereum #Blockchain