Orenix Terminal

Go‑Ethereum v1.17.3: Amsterdam Fork Enhancements, ETH/70 Activation, and Tracing API Updates

The latest Go‑Ethereum release brings maintenance updates and advances the Amsterdam fork implementation. It also activates the ETH/70 protocol on the network and introduces a breaking change to the debug_trace* tracing APIs, removing the reexec option and standardizing response fields.

Ethereum network diagram with highlighted ETH/70 node and code snippet

The Go‑Ethereum team released version 1.17.3 on May 11, 2026, marking a maintenance update that continues progress on the Amsterdam fork. The release includes several small bug fixes and performance improvements while keeping the core client stable.

A key focus of this update is the Amsterdam fork implementation. Developers can now test the new consensus rules in a more complete environment, with the fork’s state transition logic fully integrated into the test network. This paves the way for a smoother transition when the fork is activated on mainnet.

The release also activates the ETH/70 protocol on the network. ETH/70 introduces new transaction semantics that are now live, allowing nodes to process the updated transaction format without additional configuration.

Significant changes affect the debug_trace* APIs. The structLog tracer now follows the client‑wide specification defined in ethereum/execution‑apis#762. The reexec option has been removed from the tracing configuration, and response fields such as memory are now returned as 0x‑prefixed, 32‑byte padded words.

These updates provide developers with clearer, more consistent tracing data and a stable foundation for the upcoming fork. While the changes are backward‑compatible for most clients, those relying on the old reexec parameter will need to adjust their tooling accordingly.