Category: general

The post Ethereum Fusaka Upgrade Set for December 3 Mainnet Launch: What You Need to Know appeared com. Ethereum is preparing to deploy its Fusaka upgrade on December 3, introducing infrastructure enhancements focused on rollup scalability, node efficiency, and wallet functionality rather than flashy new features. The upgrade’s centerpiece arrived through EIP-7594, introducing peer data availability sampling. The implementation enables nodes to verify blob data by sampling small pieces from peers, rather than downloading full datasets. The architecture maintains security guarantees while slashing bandwidth requirements, enabling Ethereum to expand blob capacity without forcing validators to operate datacenter-grade infrastructure. Lower data costs for layer-2 networks translated directly into cheaper transaction fees for end users, even during periods of high network congestion. EthEthereum Upgradeereum Upgrade: Blob Capacity Expansion and Block Size Changes Fusaka triggers a series of Blob Parameter Only mini-forks scheduled immediately after mainnet deployment. BPO1 on December 9 raises blob targets from 6 to 10 and maximums from 9 to 15. BPO2 will follow on January 7, pushing targets to 14 and maximums to 21. The configuration-only approach enables rapid capacity scaling without requiring full hard forks, allowing the network to monitor performance and stability between incremental increases. Additionally, EIP-7935 lifts the default block gas limit to 60 million, expanding throughput capacity for legitimate usage. EIP-7825 simultaneously capped individual transactions at 16, 777, 216 gas, preventing single operations from monopolizing entire blocks. The dual implementation increased network capacity while closing denial-of-service vectors and smoothing the path toward future transaction parallelization. Ethereum Upgrade: Blob Fee Market Stabilization and Network Protocol Cleanup EIP-7918 ties blob base fees to execution layer costs, preventing the extreme price volatility that plagued earlier implementations. The mechanism stops blob fees from crashing to zero or spiking independently of layer-1 network conditions.