Scaling and security go hand in hand: A comprehensive analysis of Ethereum Fusaka upgrade and 12 EIPs

Author: @ChromiteMerge

Ethereum is set to undergo a hard fork upgrade called “Fusaka” on December 3, 2025. This upgrade includes 12 Ethereum Improvement Proposals (EIPs), which are like 12 precise components working together to enhance Ethereum’s scalability, security, and operational efficiency. Below, I will categorize these 12 EIPs and explain in plain language what problems they address and why they are crucial for Ethereum’s future.

Scalability! Making Ethereum faster and capable of handling more

This is the core theme of the Fusaka upgrade. To support the global digital economy, Ethereum must solve transaction congestion and high fees. The following EIPs aim to achieve this, especially focusing on reducing costs and increasing efficiency for Layer 2 scaling solutions.

EIP-7594: PeerDAS - Data Availability Sampling

Pain point: Since the Dencun upgrade introduced data “Blob” for cheap data storage on Layer 2, a key issue has arisen: how to ensure these massive amounts of data are truly available? Currently, each validation node must download and verify all blob data in a block. When a block carries up to 9 Blobs, this is feasible. But if the number of Blobs increases further (e.g., to 128), downloading and verifying all blobs becomes costly, raising the barrier for validator participation and threatening network decentralization.

Solution: PeerDAS (Peer Data Availability Sampling) turns the traditional “check all” approach into “sampling.” Simply put:

2. The network slices the complete blob data into pieces.

3. Validators don’t need to download all blobs—only randomly select and check a few data segments.

4. Through mutual checks and exchange of verification results, everyone can collectively confirm the integrity and availability of the entire blob data.

It’s like a large puzzle game—everyone holds a few pieces, but by checking key connection points, they can confirm the whole puzzle is intact. Notably, PeerDAS isn’t entirely new; its core idea of DAS has been successfully implemented in third-party projects like Celestia. Implementing PeerDAS is like addressing a critical “tech debt” in Ethereum’s long-term scaling blueprint.

Significance: PeerDAS greatly reduces the storage burden on validators, clearing obstacles to large-scale data expansion while maintaining decentralization. In the future, each block could contain hundreds of Blobs, supporting the Teragas vision of up to 10 million TPS, while ordinary users can run validators easily, keeping the network decentralized.

EIP-7892: BPO Hard Fork - Lightweight Parameter Upgrade

Pain point: Market demand for Layer 2 data capacity fluctuates rapidly. Waiting for a major upgrade like Fusaka every time Blob limits are adjusted is too slow and can’t keep pace with ecosystem growth.

Solution: This EIP defines a special “Blob Parameter Only Hardfork” (BPO) mechanism. It’s a lightweight upgrade that only modifies a few Blob-related parameters (e.g., target Blob count per block), without complex code changes. Node operators don’t even need to upgrade clients—just accept new parameters at a specified time, similar to updating a configuration file online.

Significance: BPO enables Ethereum to quickly and safely adjust network capacity. For example, after Fusaka, the community plans two consecutive BPO upgrades to double Blob capacity gradually. This allows for on-demand, elastic, and incremental expansion of Blob space, smoothing out costs and throughput increases, with lower risk.

EIP-7918: Stable Blob Fee Market

Pain point: The previous Blob fee adjustment mechanism was too “market-driven,” leading to issues. When demand is low, fees drop near zero, which doesn’t stimulate new demand and creates an “all-time low” price. When demand is high, fees spike, creating extreme high prices. This “price competition” makes fee planning difficult for Layer 2 projects.

Solution: EIP-7918’s core idea is to prevent Blob fees from fluctuating wildly by setting a reasonable price range—an elastic “minimum consumption.” It links Blob fee limits to the Layer 2 execution fee (e.g., for state root updates or ZK proof verification). These execution fees are relatively stable and less affected by transaction volume. By anchoring Blob fees to this stable “reference,” their volatility is reduced.

Significance: This prevents fee market “internal competition,” making Layer 2 operational costs more predictable. Stable fees help Layer 2 projects set more consistent and reasonable transaction costs, avoiding rollercoaster experiences like “free today, expensive tomorrow.”

EIP-7935: Increasing Mainnet Transaction Capacity

Pain point: The total transaction capacity per Ethereum block is determined by the “block Gas limit” (around 30 million), which hasn’t been adjusted for years. To increase throughput, raising this limit is the most direct way, but it must not raise hardware requirements for validators or weaken decentralization.

Solution: This proposal suggests raising the default Gas limit to a new level (specific value TBD, possibly 45 million or higher). It’s not mandatory but recommended, guiding validators to gradually accept higher limits.

Significance: This means each Layer 1 block can include more transactions, directly increasing TPS and alleviating congestion and high gas fees. However, higher limits also demand better hardware, so the community will proceed cautiously with testing.

Security and Stability! Building a robust defense for the network

While expanding capacity, ensuring network security and stability is essential. The Ethereum Foundation launched the “Trillion Dollar Security” plan in May 2025, aiming to build a network capable of securely handling assets worth trillions. Several EIPs in Fusaka advance this plan, like installing more reliable “brakes” and “guardrails.”

EIP-7934: Set Block Size Limit

Pain point: Ethereum’s “block Gas limit” only considers computational load, not physical size. Attackers can craft “low-cost, large-volume” transactions (e.g., sending 0 ETH to many addresses) that produce a huge data size but low computational cost, creating “data bombs” that slow network propagation and risk DoS attacks.

Solution: Enforce a hard cap of 10MB on block size. Any block exceeding this size is rejected.

Significance: Like setting maximum dimensions for trucks on a highway, this prevents oversized data from clogging the network, ensuring faster propagation, lower latency, and improved resilience against attacks.

EIP-7825: Set Per-Transaction Gas Limit

Pain point: While the block has a total Gas limit, individual transactions currently do not. Someone could craft a single transaction consuming nearly all block resources, crowding out others and creating security risks.

Solution: Impose a hard cap of 16.77 million Gas per transaction. Transactions exceeding this must be split into multiple parts.

Significance: This improves fairness and predictability, preventing any single transaction from monopolizing block space and delaying others.

EIP-7823 & EIP-7883: Secure ModExp Precompile

Pain point: ModExp (modular exponentiation) is used in cryptography but has two risks: input length can be unbounded, potentially causing resource exhaustion; and its low gas cost can be exploited for attacks.

Solutions:

• EIP-7823: Limit input length to 8192 bits, sufficient for practical use.

• EIP-7883: Increase gas costs for larger inputs, making attacks more expensive.

Significance: These measures remove a potential attack vector, akin to setting maximum task sizes and tiered pricing, enhancing network robustness.

Feature upgrades! Providing developers with more powerful tools

Beyond scalability and security, Fusaka introduces new tools and features to empower developers, making application building more efficient and powerful.

EIP-7951: Support for Mainstream Hardware Signatures

Pain point: Common devices like iPhones, bank security tokens, and hardware security modules use the secp256r1 (P-256) standard. Ethereum defaults to secp256k1, so these devices can’t directly sign Ethereum transactions, limiting Web3 adoption.

Solution: Add a precompile contract to support and verify signatures from secp256r1.

Significance: This is a milestone—enabling Ethereum to connect with billions of existing hardware devices. In the future, you could sign transactions directly with your phone’s secure element, simplifying user experience and boosting security. It lowers the entry barrier from Web2 to Web3.

EIP-7939: Efficient CLZ Instruction

Pain point: Many cryptographic and mathematical applications need to count leading zeros in a 256-bit number (e.g., in hash functions, compression, ZK proofs). Currently, EVM lacks a direct opcode for this, forcing developers to write costly, inefficient Solidity code.

Solution: Introduce a new “CLZ” (Count Leading Zeros) opcode in EVM for one-step calculation.

Significance: This provides developers with a specialized, time-saving tool, reducing gas costs for complex math operations, especially benefiting ZK Rollups and other math-intensive applications.

Network optimization! Invisible improvements for a healthier ecosystem

The last two EIPs may not be immediately noticeable to users but are vital for long-term network health and coordination.

EIP-7642: Reduce Syncing Burden for New Nodes

Pain point: Over time, Ethereum has accumulated massive historical data. New nodes need to download and sync all this data, which is time-consuming and increasingly difficult. After The Merge transitioned to PoS, some redundant fields in old receipts remain, adding unnecessary data.

Solution: Implement a “data expiration” strategy to allow nodes to skip some old data during sync; simplify receipt formats by removing unnecessary fields. This reduces the data volume for full sync from genesis.

Significance: This “lightening” of nodes can cut about 530GB of data transfer per sync, lowering the barrier to running full nodes and strengthening decentralization and resilience.

EIP-7917: Deterministic Block Proposal Order & Pre-Confirmation

Pain point: A key challenge in Layer 2 Rollups is the centralization of sequencers. Most rely on a single entity to receive and order transactions, risking censorship and MEV extraction. The “Based Rollup” concept proposes using Ethereum’s L1 proposer to order L2 transactions, inheriting L1’s decentralization.

However, this approach is slow—Layer 2 must wait for L1 inclusion, causing delays. The solution is “pre-confirmation”: the Layer 2 gateway gets a promise from future proposers that their blocks will be included, allowing it to update state early. But with current randomness, the gateway can’t know who will propose next.

Solution: EIP-7917 modifies consensus protocols to make future proposer sequences predictable and publicly available, turning “on-the-fly” randomness into a pre-ordered schedule.

Significance: This is foundational for next-gen decentralized Layer 2s like Based Rollup. With a known proposer schedule, Layer 2 gateways can pre-arrange trusted pre-approvals, enabling near-instant transaction finality while maintaining Ethereum-level security and decentralization.

Why is Fusaka the right upgrade at the right time?

This upgrade isn’t just about technology—it’s a strategic move in Ethereum’s evolution amid traditional finance integration via RWA and stablecoins. Currently, Ethereum hosts over 56% of the global stablecoin supply, becoming the core settlement layer for the digital dollar economy. Fusaka aims to prepare for Wall Street-scale assets and transaction volumes.

• Custom chains for institutional Layer 2, providing unlimited scalability “fuel”

As traditional financial institutions enter, we will see more Layer 2 “dedicated chains” tailored for specific needs (e.g., KYC compliance). These chains require Ethereum mainnet to provide massive, cheap, and secure data availability.

Proposals like EIP-7594, EIP-7892, and EIP-7918 are designed to meet this demand. Their core goal: drastically reduce data publishing costs and enable elastic, on-demand capacity expansion.

After Pectra, Blob fees are already low—why lower them further? Because Fusaka adopts a strategy of “sacrificing short-term fee income to enable larger economic activity,” aiming to grow the network’s GDP, increase transactions, staking, and ETH burns, thus supporting overall value.

• Moving towards “Trillion Dollar Security,” building unbreakable financial infrastructure

For institutions managing trillions in assets, security is paramount. Ethereum’s “Trillion Dollar Security” goal is to create a network capable of securely handling assets of that scale. EIPs like 7934, 7825, 7823, and 7883 reinforce this by closing security gaps and strengthening defenses.

In summary, Fusaka’s main theme is clear: scalability and security. With favorable regulation and market momentum, Fusaka arrives at an opportune moment, helping Ethereum solidify its dominance in stablecoins and on-chain assets, transforming from a speculative asset to a mainstream financial infrastructure.

Conclusion: Deep and steady transformation

As a key upgrade at the end of 2025, Fusaka quietly injects strong internal momentum into Ethereum. Its 12 improvements target the core issues of scalability, security, and efficiency. It broadens Ethereum’s “value highway,” boosting capacity and reliability, preparing for a future with massive users, assets, and applications.

For ordinary users, these changes may seem subtle, but their impact will be profound. A stronger, more efficient, and secure Ethereum can realize grand visions—such as a global instant settlement network or “On-Chain Wall Street.” Fusaka is a solid step toward that future.

• This analysis is based on publicly available information and does not constitute investment advice. Cryptocurrency investments carry significant risks; please DYOR and proceed cautiously.

• If you enjoyed this article, please follow, like, and share to support!