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

Author: @ChromiteMerge

Ethereum is scheduled 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 simple terms 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 Layer 2 data storage, a key issue has arisen: how to ensure these massive data sets are truly available? Currently, each validator node must download and verify all blob data in a block. When a block carries up to 9 blobs, this is manageable. But if future blob counts increase (e.g., to 128), downloading and verifying all blobs will become costly, raising the barrier for validator participation and threatening network decentralization.

Solution: PeerDAS (Peer Data Availability Sampling) turns the traditional “check everything” approach into “sample and verify.” Simply put:

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

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

4. Then, 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 DAS concept 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 storage burdens 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 is constantly changing. 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 (like target blobs per block), without complex code changes. Node operators can simply accept new parameters at a specified time, similar to updating a configuration file online, without needing to upgrade client software immediately.

Significance: BPO enables Ethereum to quickly and safely adjust network capacity. For example, after Fusaka, the community plans to execute two consecutive BPO upgrades to double Blob capacity gradually. This allows Ethereum to scale blob space on-demand, flexibly and incrementally, smoothing out costs and throughput increases while managing risks.

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 effectively 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 spend.” It links the blob fee limits to the Layer 2 execution fee on Layer 1, which remains relatively stable regardless of 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 approach, but it must be done without raising hardware requirements for validators or weakening decentralization.

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

Significance: This means each Layer 1 block can include more transactions, directly increasing TPS and alleviating network 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 scaling, ensuring network security and stability is paramount. The Ethereum Foundation launched the “Trillion Dollar Security” (1TS) 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” for Ethereum’s high-speed operation.

EIP-7934: Set Block Size Limit

Pain point: Ethereum’s “block Gas limit” only considers computational load but doesn’t specify physical block size. Attackers could craft “low-cost, large-volume” transactions (e.g., sending 0 ETH to many addresses) that are computationally cheap but physically large, 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 truck dimensions on a highway, this prevents oversized data blocks from affecting network traffic, 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 have no maximum. Someone could craft a single transaction consuming nearly all block resources, delaying others and creating unfairness.

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

Significance: This improves fairness and predictability, preventing any single transaction from monopolizing block space and ensuring normal transactions aren’t delayed by “super-large” ones.

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 large computations more expensive and resource-aware.

Significance: These measures remove attack vectors by bounding input sizes and aligning costs with resource consumption, enhancing network robustness.

Feature upgrades! Providing developers with more powerful tools

Beyond scaling and security, Fusaka introduces new tools and features to empower developers, making building on Ethereum more efficient and powerful.

EIP-7951: Support for Mainstream Hardware Signatures

Pain point: Devices like iPhones, bank security tokens, and hardware security modules (HSMs) commonly use the secp256r1 (P-256) standard, while Ethereum defaults to secp256k1. This mismatch limits seamless integration with mainstream hardware.

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

Significance: This is a milestone—enabling Ethereum to directly interact with billions of hardware devices worldwide. Soon, you could sign Ethereum transactions directly with your phone’s secure chip, without extra wallets or conversions, improving user experience and security. It greatly lowers the barrier for traditional device integration into Web3.

EIP-7939: Efficient CLZ Instruction

Pain point: Calculating the number of leading zero bits in a 256-bit number is common in cryptography and zero-knowledge proofs, but current EVM lacks a direct opcode for this, forcing complex Solidity code that is costly and inefficient.

Solution: Introduce a new “CLZ” (Count Leading Zeros) opcode that performs this calculation directly.

Significance: This provides developers with a specialized, time-saving tool, reducing gas costs for math-heavy applications like ZK Rollups, making them cheaper and more efficient.

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: As Ethereum’s history grows, new nodes must download and sync massive amounts of data, making it increasingly difficult. Post-Merge, some redundant fields in old receipts also add unnecessary data.

Solution: Implement “data expiry” strategies to allow new nodes to skip some old data during sync, and simplify receipt formats by removing unnecessary fields. This reduces the data volume needed for full sync from genesis.

Significance: This “lightening” can cut about 530GB from full node syncs, lowering entry barriers 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—single entities that order transactions, risking censorship and MEV extraction. The “Based Rollup” idea proposes using Ethereum’s L1 proposer to order L2 transactions, inheriting L1’s decentralization. But this introduces delays, as Layer 2 must wait for L1 inclusion, degrading user experience.

Solution: EIP-7917 modifies consensus to precompute and publish the proposer order for upcoming blocks, turning random selection into a predictable schedule.

Significance: This is foundational for “Based Rollup” and similar schemes. With a known proposer schedule, Layer 2 gateways can negotiate with future proposers in advance, enabling trusted pre-confirmations secured by slashing penalties. It bridges decentralization with near-instant transaction finality, opening a new path toward more decentralized, scalable rollups.

Why is Fusaka timely?

This upgrade isn’t just technical; it’s a strategic move amid the era of real-world asset (RWA) onboarding and stablecoins on Ethereum. Currently, Ethereum hosts over 56% of 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, with unlimited scaling “fuel”

As traditional finance enters crypto, we’ll see more Layer 2 “dedicated chains” tailored for specific needs (e.g., KYC compliance). These chains require Ethereum mainnet to provide vast, cheap, and secure data availability.

Proposals like EIP-7594, EIP-7892, and EIP-7918 are designed to drastically reduce data publishing costs and enable elastic, on-demand scaling.

• Moving toward “Trillion Dollar Security”—building unbreakable financial infrastructure

For institutions managing trillions in assets, security is paramount. The “Trillion Dollar Security” plan aims to harden Ethereum’s defenses. EIPs like 7934, 7825, 7823, and 7883 reinforce this goal by setting size limits, improving validation, and tightening cryptographic safeguards.

In summary, Fusaka’s main theme is clear: scaling and security. Under favorable regulations and market enthusiasm, this upgrade is perfectly timed. It will help Ethereum seize policy opportunities, solidify its dominance in stablecoins and asset onboarding, and evolve from a speculative asset to a mainstream financial infrastructure.

Conclusion: Deep waters, steady progress

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 more powerful, efficient, and secure Ethereum can realize ambitious visions—be it 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!