Ethereum’s latest upgrade, Fusaka, has been operational on the network since December 3rd. This earned the ecosystem its second reception. hard fork (hard fork) this year, following Pectra in May.
As reported by CriptoNoticias, the proposal is known as: PeerDAS is Fusaka’s most important improvement And Vitalik Buterin himself brought to the network what he had been waiting for since 2015.
PeerDAS introduces the following systems Verify data availability by sampling across nodes. Rather than each node having to download all files, blob Completeness (the space in which the second layer network stores information) now only requests small random samples from different peers.
The graph below was taken a few hours after Fusaka’s release and reflects PeerDAS. works as intended:
In the image, the node located in Finland (‘tysm’) requests some data strings from the network corresponds to blob Used by Base and Arbitrum.
You will see a “MISSING” message because those samples are not stored on that particular node. This is normal for PeerDAS. Nodes no longer need to store all data to check availability.
Instead, Node queries other peers (In this case, the Taiwan node). These peers have these columns and send them within 0.5 seconds.
In this way, The network ensures that relevant data is availableThis is true even if it is not fully replicated on each node.
This behavior accurately reflects the goal of PeerDAS on Ethereum. This means reducing the burden on individual storage while making the information accessible to those who need it.
Ethereum’s second layer network exposes more data in the following formats: blob
next graph «Average number of blobs per block» (average blob block). Trends in average number blob block by block.
The black line rises from around “4” (left axis) until it approaches the target marked “6”. blob Block by block (horizontal skyline).
This shows that after Fusaka the network started using more space blob Within the block, it approaches the goal defined by its parameters.
In short: L2 has started publishing more data in the following formats: blobPeerDAS then begins to play a role in checking that increased traffic.
Why is it useful for L2? Because by sharding and distributing the load across many nodes, Layer 2 can expose more data without having to rely on each Ethereum node to fully download and verify everything.
This reduces operational costs, increases batch processing speed, and L2 continues to scale without increasing the load on the base network.
Moreover, this chart shows just the beginning of a series of planned expansions. Therefore, this effect will become even greater in the future.
Starting with proposal EIP-7892, it proposes a series of incremental updates that adjust limits exclusively. blob, December 9th, fork what Raise your current goals blob From 6:00 to 10:00And again on January 7th next year fork It will take place from 10:00 to 14:00.
rate blob: Peak and correction after Fusaka
Hours before Fusaka’s arrival, the network sudden peak of BLOB charges The fee that L2 pays to publish data on Ethereum. mass.
According to the following graph, that fee amounted to approximately 1,463 Gwei (the smallest unit of Ether used to express fees in Ethereum). Currently equivalent to approximately $0.0047:
Until Fusaka integration, BLOB fee It was essentially symbolic. The minimum possible value was set to 0.000000001 Gwei and remained that way unless there was congestion.
This stationary floor L2 will publish data on Ethereum for almost free 99% of the timeEven if that activity results in a real cost to the network.
With the enablement of Fusaka, specifically EIP-7918, the “floor” of this fee is blob Since it is no longer fixed, We have moved to a dynamic system linked to the actual cost of operations at L1.
committee floor blob was standing around 1/16th of the Ethereum base fee (1/16)according to the text of EIP-7918.
This is what the dynamic floor looks like BLOB fee Truss flap:
Considering normal Ethereum usage levels, the system established by EIP-7918 requires a minimum BLOB charges Usually a value between 0.01 and 0.5 gwei (i.e. Tens of millions of times, hundreds of millions of times (from the old minimum value 1 way). Unlike the previous scheme, it is no longer possible to go down to zero.
Additionally, this new rate floor directly impacts the Ethereum economy by charging a realistic minimum fee. blobthe network will stop subsidizing verification, Fee income will start to increase.
On the other hand, for the end user, the impact is almost imperceptible. L2 fees are still very low. Because of these costs. They are diluted between: Millions of transactions.
Gas limit per block: more data capacity
Since Fusaka, EIP-7935, Ethereum client works by default Gas limit per block is 60 million. This represents a 100% increase from the 30 million people using the network at the beginning of 2025.
The “gas limit” defines the amount of computational work or transaction space that can be contained in a block. Apart from fusaka, gas limits are measures agreed upon by validators and can be increased or decreased.
Increasing this to 60 million allows us to hold more transactions per block, making it easier for the network to support larger loads without immediately congesting it.
Ethereum consensus software crashed after Fusaka
Finally, a few hours after Fusaka went live, the Prysm consensus client (one of the programs used by nodes to coordinate the chain) failed. He also temporarily left the company. About offside 23% of the network.
According to what they communicated from Prysm: There are no signs The cause of the failure was fusaka.
The Prysm team identified the problem and published a simple solution that operators can implement in minutes by simply adding a line of code to their node, without having to download a new version.
As a result, the network continued to function without significant impact.