Go Ethereum has released Geth v1.17.9, adding support for Ethereum’s upcoming Glamsterdam activation on the Hoodi testnet alongside execution, database and networking improvements. The October 21 release configures the Amsterdam execution fork for October 26 at 17:42:48 UTC, making the update particularly relevant to operators participating in Ethereum’s final major public test environment before a future mainnet deployment.
According to the official Go Ethereum release, v1.17.9 is recommended for all Geth users running Hoodi nodes rather than being presented as a mandatory mainnet-wide upgrade. Geth remains one of Ethereum’s most widely deployed execution clients and handles EVM execution, transaction processing, state management and communication with consensus clients through the Engine API.
The update arrives as Glamsterdam moves beyond earlier devnet testing. Sepolia already activated the upgrade on October 6, while Hoodi is scheduled to follow on October 26. Glamsterdam therefore remains a testnet-stage protocol upgrade rather than functionality already active on Ethereum mainnet.
Geth Improves EVM and Database Performance
Geth v1.17.9 introduces several execution-level optimizations unrelated to the fork schedule itself. A new inlined switch implementation makes EVM opcode dispatch approximately 16% faster, according to the development team’s benchmark, while moving state-history commits into the background improves newPayload processing by roughly 2%.
The release also addresses multiple operational defects. Fixes cover database corruption following power failures, concurrent state reads, mempool corruption when tips fall below the base fee and Block-Level Access List corruption caused by RPC activity during block processing, alongside changes intended to improve key-value database write performance.
Block-Level Access Lists are particularly relevant to Glamsterdam. Introduced through EIP-7928, BALs record accounts and storage locations accessed during a block so clients can process state more efficiently. Geth’s fixes are therefore part of client-level preparation for a protocol feature rather than evidence that BAL-based parallelization is already operating on Ethereum mainnet.
The execution-client work complements earlier consensus-side preparation. Prysm’s v7.1.5 and v7.1.6 releases introduced Gloas, PeerDAS and validator-performance work months before the current Hoodi transition. Ethereum upgrades depend on compatible execution and consensus implementations working together, not on any single client shipping support independently.
Client Updates Turn Glamsterdam Into Running Software
Glamsterdam combines Amsterdam on the execution layer with Gloas on the consensus layer. Its principal changes include enshrined proposer-builder separation and Block-Level Access Lists, restructuring block production while creating infrastructure for more concurrent execution and higher Layer 1 capacity.
Those changes have progressed through several testing stages. Ethereum previously launched the Platåberget public testnet specifically to expose Glamsterdam implementations to wider testing before moving into Sepolia and Hoodi. The October Hoodi activation is therefore another interoperability checkpoint rather than the conclusion of the upgrade process.
Geth also retains its existing version-check security command, which compares the installed client against Go Ethereum’s published vulnerability database. That capability predates v1.17.9 and should be treated as an ongoing node-security tool rather than a feature introduced by the new release.
The importance of v1.17.9 is consequently narrower but concrete. The release gives Geth-based Hoodi nodes the Amsterdam rules required for the October 26 fork while improving execution performance and fixing several operational edge cases, providing another client implementation needed to test Glamsterdam under persistent network conditions before any mainnet activation is scheduled.
Jack Reynolds is SatoshiPick’s infrastructure mind. Based in Denmark, he follows Bitcoin, Ethereum, Layer 1 networks, stablecoins and DeFi with a practical question always in the background: does this actually make crypto work better?
His articles focus on the systems beneath the headlines: settlement rails, protocol upgrades, stablecoin usage, DeFi coordination and the regulatory limits around them. Jack avoids turning technical coverage into a maze. He explains what is live, what is still experimental and why the difference matters.