TLDR
Ethereum (ETH) raised its blob parameters: the per?block blob target increased to 14%%CKPROTECTED2%% and the max blob limit to 21%%CKPROTECTED4%% in the second Blob Parameter?Only fork (Cointelegraph report).
- More blob supply can expand rollup data throughput and help pressure blob fees lower (Decrypt analysis).
- Each blob is 128 KB, so blocks can now carry about 2,688 KB of blob data (Cointelegraph report).
- It is a config?only, phased tuning step within the Fusaka upgrade cadence (The Block summary).
Deep Dive
1. Parameter Changes
The network raised the blob target from 10 to 14 and the maximum limit from 15 to 21 at 1:01:11 UTC, increasing data availability for rollups (Cointelegraph report).
The Blocks recap notes this was the final planned Blob Parameters Only fork in the Fusaka cycle, following a first fork in December that moved the target from 6 to 10 and the max from 9 to 15 (The Block summary).
2. Throughput and Fees
More blob capacity lets rollups batch more data per unit time, which can translate into lower blob fees passed through to end users when demand doesnt overwhelm the added supply (NewsBTC overview).
Decrypt emphasizes the incremental, parametric nature of Ethereums scaling: tuning blob capacity helps smooth rollup fee dynamics and adds headroom before congestion emerges (Decrypt analysis).
If you rely on L2s for activity, monitor blob fees and rollup batch behavior. Lower blob fees could reduce end?user transaction costs, but the benefit depends on demand and network stability.
3. Limits and Monitoring
The community highlights the blob target as the key health indicator. Persistently approaching the 21?blob ceiling may strain node bandwidth and storage, so the higher target allows more throughput while keeping an eye on sustainability (Cointelegraph report).
Phased, config?only bumps enable controlled testing of increased load rather than bundling changes into larger hard forks, keeping decentralization and stability front?of?mind (The Block summary).
Conclusion
Ethereums latest blob parameter increase is an incremental, safety?first tuning that boosts data capacity for rollups. It can lower blob fees and improve throughput when demand is manageable, but sustained performance depends on how close usage runs to the new ceiling and how L2s adapt.
CoinsKid.Com