For the first time in its history, the Ethereum Network reached its maximum blob capacity per block on August 27th last year.
As Cryptootics notified, the BLOB was entered in the DenCun update in March 2024 and is the data package that the second tier solution (L2) uses to reduce transaction costs. By storing information outside the main chain.
According to data from researchers at the L2Beat site, the use of blob usage reached 225 MIB per hour on the day, sometimes slightly exceeding that threshold. 228.5 Maximum Record of Effective Data in MIB.
“MIB” or Mebibyte is a digital storage unit. In reality, 1 MIB is equivalent to 1,048 MB (Megabytes). If L2Beat shows a blob capacity of 225 MIB, that number equals 236 million bytes of data per hour.
The next graphic shows how the volume of data on blobs remained high throughout the previous week until it reached its historic peak on August 27th.
The blue line shows the actual size of the data occupied by the blob, while the dotted line corresponds to the desired capacity set by the protocol. What’s related is that for the first time, both curves intersect, and the system intersects Design limit reached.
In the second graphic from L2Beat, we observe the chain costs of different types of data in Ethereum.
The punctual rebound stands out on August 27th. Matches the moment the mass reaches its maximum capacity.
Still, the costs associated with this type of data remained. Less than $0.01. This “cost” refers to the commission that a user pays to the Ethereum Network and is the inclusion of a blob in a block.
It reflects that, despite capacity saturation, the chunk is a chunk We continued to offer low-cost alternatives We reaffirm our central role in scalability in Ethereum as we face other forms of storage within our network.
Limit the effect of the amount of chunks reached
It reflects the fact that the network touched the maximum blob capacity by block A sustained increase in spatial demand of data from Ethereum’s second tier. This can be interpreted in two ways.
On the other hand, it is a recruitment indicator. This means that more and more transactions are being processed through this resource-dependent scaling solution. In that sense, when the limit is reached, a mass is confirmed They serve their function to ease the load on the main network Reduce transaction costs.
Meanwhile, he also raises doubts about the future. If Blobs demand is consistently above the capacity set at 225 MIB, You can present a bottleneck It raises the commissions associated with its use, as occurs when the main network is busy.
Technically speaking, the event suggests that as Ethereum continues to rise through the second-tier network, we need to see if Blobs’ current capacity is sufficient and if we should increase that threshold.
Adjusting this type requires new proposals for improvement (EIP) and broad discussion within the developer community.
For now, the fact that a certain time limit has been reached does not imply a structural problem.
However, it provides an important precedent. Ethereum is already operating at the theoretical maximum of key resources for scalability. The challenge is to maintain its capabilities as demand continues to grow in the coming months.
