Deep Dive
1. Amsterdam Fork Implementation (May 2026)
Overview: The Geth v1.17.4 release, tagged "Flexible Polymer Casing," is a maintenance update that continues implementing the upcoming Amsterdam hard fork. It introduces core features designed to make the network process data more efficiently, which should result in lower costs and faster confirmation times for users.
This release focuses on several key Ethereum Improvement Proposals (EIPs). EIP-7928 introduces Block-Level Access Lists (BALs), which allow nodes to pre-fetch the exact state data needed to execute a block, drastically speeding up processing. EIP-8189 establishes snap/2, a new state-sync protocol built on these access lists for more efficient initial synchronization. Additionally, EIP-8037 increases the gas cost for creating new state, encouraging better resource management by developers. The update also includes various RPC improvements, such as the new eth_baseFee method and optimized engine API handling for large data payloads.
What this means: This is bullish for Ethereum because it lays the groundwork for significantly faster and cheaper transactions. The new block-level access lists mean nodes can verify blocks more efficiently, reducing the hardware burden and improving network decentralization. For everyday users, this translates to a smoother experience with dApps and lower fees, especially as these optimizations trickle down to Layer 2 networks.
(Source)
2. Fusaka Upgrade & BPO Forks (December 2025)
Overview: The Fusaka (Osaka) network upgrade went live on mainnet on December 3, 2025. Its headline feature is the implementation of PeerDAS (Peer Data Availability Sampling), a sophisticated mechanism that allows nodes to verify large amounts of data without downloading it all. Following Fusaka, two parameter-only forks, BPO1 and BPO2, were scheduled to progressively increase the network's blob capacity.
The upgrade's primary goal is scaling data availability for Layer 2 rollups. Fusaka itself began expanding blob capacity, and the subsequent BPO forks were planned to raise the target and maximum blobs per block significantly—for example, from 6/9 to 10/15 and then to 14/21. This structured increase is designed to safely boost the network's data throughput, which directly reduces transaction costs on rollups like Arbitrum and Optimism.
What this means: This is extremely bullish for Ethereum as it directly tackles high fees, the network's most significant user pain point. By more than doubling the data capacity for rollups, Fusaka and the BPO forks enable Layer 2s to offer transactions for pennies instead of dollars. This makes Ethereum more competitive and accessible for millions of users, strengthening its position as the leading smart contract platform.
(Source)
3. Gas Limit Increase & Client Updates (June 2025)
Overview: In late June 2025, the Ethereum community group ethPandaOps recommended that validators increase the gas limit per block to 45 million. In response, new releases of core execution clients, Geth v1.16.0 and Nethermind 1.32.0, set this higher limit as their default. This is a consensus-driven parameter change that allows each block to contain more transactions or complex operations.
Increasing the gas limit is a direct method to enhance network throughput. It means the base layer can process more activity within the same 12-second block time. This change followed extensive testing and community discussion to ensure network stability, as a higher limit also increases the potential resource load on nodes. The coordinated client updates ensure the network operates uniformly under the new parameters.
What this means: This is neutral to bullish for Ethereum. It provides immediate relief for network congestion by increasing capacity, which can help moderate gas fees during peak demand. However, it also requires node operators to have adequate hardware to handle larger blocks. For users, the main benefit is a more responsive network during busy periods, reducing transaction wait times.
(Source)
Conclusion
Ethereum's codebase is in a phase of aggressive optimization, with recent work squarely focused on executing the Amsterdam upgrade and building upon the scaling foundations laid by Fusaka. This trajectory emphasizes lower fees, higher throughput, and a more robust base layer. How will the successful deployment of Amsterdam's block-level access lists further catalyze the next wave of Layer 2 innovation?