Deep Dive
1. Amsterdam Fork Configuration (26 September 2025)
Overview: This commit adds the initial configuration for the Amsterdam fork to the Geth client. It's a foundational step that allows developers and testnets to start working with the new rules before the upgrade goes live.
The update defines Amsterdam as a new fork option within the client's parameters. This doesn't change how users interact with Ethereum today but is essential for node operators and developers to prepare for the future upgrade, which includes changes to gas costs and new opcodes.
What this means: This is neutral for Ethereum in the short term but bullish for its long-term health. It shows disciplined, forward-looking development essential for implementing scaling improvements and keeping the network competitive. It means the next major upgrade is moving from research into active development.
(Source)
2. Blobpool Legacy Transaction Conversion (24 September 2025)
Overview: This update ensures that blob transactions created before the Osaka (Fusaka) hardfork remain valid and can be processed afterward, preventing user transactions from being dropped.
The code implements a background process that automatically converts older "legacy" blob transactions to the new proof format required post-Osaka. This conversion happens seamlessly when a reorg occurs near the fork boundary, guaranteeing compatibility.
What this means: This is bullish for Ethereum because it prioritizes user experience and network stability during a major upgrade. Users and applications relying on blobs (like many Layer 2s) won't experience disruption, fostering continued adoption and trust in the network's upgrade process.
(Source)
3. Maintenance Release Geth v1.17.3 (11 May 2026)
Overview: This stable release focuses on refining the Amsterdam fork implementation and introduces eth/70, a new version of the Ethereum wire protocol that improves how nodes communicate.
The release includes numerous core improvements like binary trie updates and state database refactoring. For everyday users, the most notable change is that certain tracing API outputs have been standardized across different Ethereum clients, making developer tools more reliable.
What this means: This is bullish for Ethereum as it demonstrates consistent, iterative progress beyond headline-grabbing hardforks. The network becomes more robust and efficient for node operators, while developers benefit from more consistent tools, ultimately leading to a better experience for all applications built on Ethereum.
(Source)
Conclusion
Ethereum's development remains highly active, with recent codebase work squarely focused on executing its roadmap—finalizing the Fusaka upgrade's mechanics and laying the groundwork for the subsequent Amsterdam fork. This steady cadence of core optimizations and protocol evolution strengthens Ethereum's foundation as a scalable settlement layer. How will these under-the-hood improvements translate to tangible benefits for the next wave of decentralized applications?