Recently, at an All Core Devs meeting, Ethereum developers discussed and approved a package of proposals to improve the network as part of the upcoming Fusaka fork. The update, at first glance, does not look revolutionary — it does not have a new "main feature", as was the case with sharding or PoS. But if you dig deeper, it becomes clear: Fusaka can significantly improve the performance of Ethereum without dramatically complicating the protocol. And that's exactly what we need in 2025.
About gas and limits
One of the key decisions is to increase the gas limit to 45 million. This could give Ethereum a bandwidth boost of more than 11% if everything goes smoothly. However, the developers emphasize that you can't just increase the volume — you need to make sure that the blocks don't start spreading too slowly, because this threatens to destabilize the network.
Blobs and blobs
Do you remember the Dencun update and EIP-4844? It added so-called BLOB objects, an inexpensive way to put data "outside" the blockchain. The problem is that no one has limited how many such blobs can be thrown into one transaction. This opened the way to a potential overload. Now this is being fixed: EIP-7892 introduces limits on the number of blobs per transaction, and EIP-7918 introduces a minimum fee and a total ceiling of blobs per block. Ironically, by limiting the size of one blob, you can allow more of them to be included in the block — such is the engineering magic.
Technical treats for developers
The update also includes EIP-7939, which introduces the CLZ operation code into the Ethereum virtual machine (EVM) — a zero counter at the beginning of the number. This is a highly specialized piece that can speed up cryptographic calculations and randomization. It's already available in many modern VMs, and now it's coming to us.
Another long—awaited moment is EIP-7951. It adds built—in secp256r1 cryptography support, an important step towards full-fledged WebAuthn authorization and deeper integration of Ethereum into mobile and enterprise solutions.
But not everything is smooth.
There was also some controversy. Paradigm's chief technology Officer, Georgios Konstantopoulos, recalled two old Solidity issues: the stack depth limit and the 24 KB contract size. He believes that Fusaka's current changes don't do anything about it. The developers, in turn, answer: EOF (the new contract model) is precisely aimed at solving these problems — it's just not part of Fusaka directly.
What is the result?
Fusaka is not a bright revolution, but a balanced engineering refinement that makes Ethereum faster, more flexible and a little more convenient for developers. Without unnecessary risk, without dramatic changes. Perhaps this is exactly the maturity that is needed now.
What do you think — is Ethereum worth focusing on small but steady improvements, or is it time to take another swing at something grand?
