Deep Dive
1. Geth v1.17.5 with Amsterdam Prep (June 2026)
Overview: This maintenance release for the Go-Ethereum (Geth) client includes bug fixes and continues implementation work for the upcoming Amsterdam hard fork. It updates default system settings and adds support for a new database backend.
The release implements or updates several key Amsterdam EIPs, including EIP-2780 (resource-based transaction gas), EIP-8037/8038 (state gas costs), EIP-8246 (removing SELFDESTRUCT burn), and EIP-7928 (Block-Level Access Lists). It also introduces a "sparse blobpool" to reduce memory usage for blob transactions and adds a new CLI flag (--override.amsterdam) for testing.
What this means: This is neutral for Ethereum as it represents routine, forward-looking maintenance. For node operators, it means a required software update for future compatibility. For users, it lays the groundwork for future network improvements that aim to be more efficient and scalable.
(Source)
2. Fusaka Upgrade Activation (December 2025)
Overview: The Fusaka (Fulu-Osaka) hard fork activated on Ethereum mainnet on 3 December 2025. Its centerpiece was EIP-7594, known as Peer Data Availability Sampling (PeerDAS), which significantly expands data capacity for Layer 2 rollups.
The upgrade increased the target blobs per block from 3 to 4 and the maximum from 6 to 8. It also included parameter-only forks (BPO1 & BPO2) in December 2025 and January 2026 to further increment blob capacity. This work shifts transaction growth to Layer 2 networks, which now process over 24 million daily transactions compared to 1.77 million on mainnet.
What this means: This is bullish for Ethereum because it directly increases the network's scalability and reduces costs for users on Layer 2s. It strengthens Ethereum's role as a secure settlement layer for a thriving ecosystem of faster, cheaper applications.
(Source)
3. Binary Trie Development (Ongoing)
Overview: Core developers are actively working on replacing Ethereum's current Merkle-Patricia Trie state structure with a Binary Trie. This is a foundational change aimed at enabling stateless clients and more efficient state proofs.
Recent commits to the Geth repository show ongoing refactoring of the state database and trie logic to support this new structure. This long-term project, part of the "Verkle Trees" roadmap, is critical for reducing the hardware requirements to run a node and improving network decentralization.
What this means: This is bullish for Ethereum's long-term health. A successful transition to a binary trie would make running a node cheaper and easier, leading to a more decentralized and resilient network. For developers, it enables new, efficient ways to interact with the chain's state.
(Source)
Conclusion
Ethereum's codebase is in a phase of steady evolution, balancing immediate client maintenance, recently deployed scalability upgrades, and deep, long-term architectural research. This multi-track development reinforces the network's foundational stability while methodically advancing its scalability roadmap. How will the completion of the binary trie work reshape the node operator landscape and further decentralize the network?