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 provide simple explanations of 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 arose: 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 feasible. But if future blobs increase (e.g., to 128), downloading and verifying all blobs will incur high costs, raising the barrier for validators 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—they randomly download and check only a few data slices.

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 only 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 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, preserving network decentralization.

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 need adjustment 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 blobs per block), without complex code changes. Node operators can simply accept new parameters at a specified time, like updating a configuration file online, without needing to upgrade client software.

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 while keeping risks manageable.

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 volatility (“internal competition”) complicates Layer 2 fee planning.

Solution: EIP-7918’s core idea is to prevent Blob fees from fluctuating wildly by setting a reasonable price range, i.e., a flexible “minimum spend.” It links the blob fee limits to the Layer 2 execution fee on Layer 1. Whether updating state roots or verifying ZK proofs, these execution fees are relatively stable and less affected by Layer 2 transaction volume. Tying blob fee limits to this stable “anchor” prevents wild swings.

Significance: This directly prevents “fee market internal competition,” making Layer 2 operational costs more predictable. Consequently, Layer 2 projects can set more stable and reasonable transaction fees, avoiding rollercoaster experiences of “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” (currently about 30 million), which hasn’t been adjusted for years. To increase throughput, raising this limit is the most direct approach, but it must not raise validator hardware requirements or weaken decentralization.

Solution: This proposal suggests increasing 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 boosting TPS, easing network congestion and gas price spikes. However, it also demands higher hardware specs for validators, 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” (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” on a high-speed Ethereum.

EIP-7934: Set Block Size Limit

Pain point: Ethereum’s “block Gas limit” only considers total computational load but doesn’t specify physical block size. Attackers can craft many “low-cost, large-volume” transactions (e.g., sending 0 ETH to many addresses), creating blocks with low computational but enormous physical size. Such “data bombs” 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 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 Gas limit exists, individual transactions currently have no cap. Someone could craft a single transaction consuming nearly the entire block, crowding out others, which is unfair and risky.

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-sized” 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, which is sufficient for practical use.

• EIP-7883: Increase gas costs for larger inputs, making large computations more expensive and deterring abuse.

Significance: These improvements remove a potential attack vector by capping input size and aligning costs with resource consumption, enhancing network robustness.

Developer Tools and Functionality Upgrades

Beyond scalability and security, Fusaka introduces new tools to empower developers and improve application building.

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, while Ethereum defaults to secp256k1. This mismatch limits direct secure interactions with Ethereum.

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

Significance: This milestone opens the door for billions of devices to securely sign Ethereum transactions directly, simplifying user experience and boosting Web3 adoption by integrating with existing hardware security standards.

EIP-7939: Efficient CLZ Instruction

Pain point: Many cryptographic and mathematical applications need to count leading zeros in a 256-bit number. Currently, EVM lacks a direct opcode, forcing developers to write costly Solidity code.

Solution: Introduce a new “CLZ” (Count Leading Zeros) opcode in EVM.

Significance: Provides developers with a powerful, efficient tool, reducing gas costs for zero-counting operations, especially beneficial for ZK rollups and advanced cryptography.

Network Optimization! Invisible improvements for a healthier ecosystem

The last two EIPs, though less perceptible to users, 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 data, raising barriers. Post-Merge, some redundant fields in old receipts also add unnecessary data.

Solution: Implement “data expiry” strategies to skip old data during sync, and simplify transaction receipts by removing obsolete fields. This allows new nodes to sync from genesis with less data.

Significance: This “lightening” reduces full node sync data by about 530GB, lowering entry barriers and strengthening decentralization and resilience.

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

Pain point: Current Layer 2 Rollups rely on a centralized sequencer, which can censor transactions or extract MEV, conflicting with decentralization. The “Based Rollup” idea proposes using Ethereum’s proposer to order L2 transactions, inheriting L1’s decentralization.

However, this introduces delays, as Layer 2 must wait for L1 inclusion. Pre-commitment mechanisms could help, but current randomness makes proposer selection unpredictable.

Solution: EIP-7917 modifies consensus to precompute and publish the proposer schedule in advance, turning the random selection into a predictable, publicly available “block proposer timetable.”

Significance: This is key for implementing “Based Rollup” and similar decentralized sequencing solutions. It enables Layer 2 gateways to pre-negotiate with future proposers, ensuring trust-minimized pre-confirmations, and bringing near-instant transaction finality while maintaining Ethereum’s security and decentralization.

Why is Fusaka’s timing so perfect?

This upgrade isn’t just technical; it’s a strategic move amid the era of on-chain real-world assets (RWA) and stablecoins. Ethereum now hosts over 56% of global stablecoin supply, becoming the core settlement layer of the digital dollar economy. Fusaka aims to prepare Ethereum for Wall Street-scale assets and transaction volumes.

• Custom chains for institutional Layer 2, providing unlimited scaling “fuel”
  As traditional finance enters crypto, we’ll see more “private” Layer 2 chains tailored for specific needs (e.g., KYC compliance). These need Ethereum’s data availability for cheap, secure storage. EIPs like 7594, 7892, and 7918 are designed to drastically reduce data publishing costs and enable flexible, on-demand expansion.

• Moving towards “Trillion Dollar Security” — building unbreakable financial infrastructure
  For institutions managing trillions, security is paramount. Fusaka’s EIPs (7934, 7825, 7823, 7883) reinforce Ethereum’s defenses, aiming for a security level that can safely host assets of that scale.

In summary, Fusaka’s clear focus on scalability and security aligns perfectly with market trends and regulatory support. It positions Ethereum to solidify its dominance in stablecoins and on-chain assets, transforming from a speculative asset to a mainstream financial backbone.

Conclusion: Deep and steady change

As a major 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, faster, safer Ethereum can realize ambitious visions—global instant settlement networks, “on-chain Wall Street,” and more. Fusaka is a solid step toward that future.

• This analysis is based on public 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!