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 simple terms what problems they address and why they are crucial for Ethereum’s future.
Scalability! Making Ethereum Faster and More Capacity
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 are aimed at achieving this, especially focusing on reducing costs and improving efficiency for Layer 2 scaling solutions.
EIP-7594: PeerDAS - Data Availability Sampling
Pain Point: Since the Dencun upgrade introduced data “Blob” for low-cost data storage on Layer 2, a key issue arose: how to ensure the massive amount of data is truly available? Currently, each validator downloads and verifies all blob data in a block. When a block carries up to 9 Blobs, this is manageable. But if the number of Blobs increases (e.g., to 128), downloading and verifying all blobs becomes costly, raising the barrier for validators and threatening network decentralization.
Solution: PeerDAS (Peer Data Availability Sampling) turns the traditional “check all” approach into “sample check”. Simply put:
The network slices the complete blob data into pieces.
Validators don’t need to download all blobs—they randomly download and verify only a few data slices.
Validators then cross-check and exchange verification results to collectively confirm the integrity and availability of the entire blob data.
It’s like a big puzzle game: everyone has only a few pieces, but by checking key connection points, they can confirm the whole puzzle is intact. It’s worth noting that PeerDAS isn’t entirely new; its core idea of DAS has been successfully implemented in third-party projects like Celestia. Implementing PeerDAS is like filling a “technical 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 changes rapidly. Waiting for a major upgrade like Fusaka every time the Blob limit is adjusted is too slow and cannot keep pace with ecosystem growth.
Solution: This EIP defines a “Blob Parameter Only Hardfork (BPO)” mechanism. It’s a lightweight upgrade that only modifies a few parameters related to Blobs (e.g., target Blob count per block), without complex code changes. Node operators don’t even need to upgrade their clients—just accept the new parameters at a specified time, like updating a configuration file online.
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 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 unpredictable prices. When demand was low, fees dropped near zero, which didn’t stimulate new demand and created an “all-time low” price. When demand surged, fees spiked, creating extreme high prices. This “price competition” made fee planning difficult for Layer 2 projects.
Solution: EIP-7918’s core idea is to set a reasonable price range for Blob fees, with a flexible “minimum spend”. It links the upper and lower limits of Blob fees 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 fees to this “anchor” prevents wild price swings.
Significance: This prevents Blob fee “price wars,” making Layer 2 operating costs more predictable. As a result, Layer 2 projects can set more stable and reasonable transaction fees, avoiding rollercoaster experiences like “free today, expensive tomorrow.”
EIP-7935: Increasing Mainnet Transaction Capacity
Pain Point: The total transaction capacity per Ethereum block is limited by the “block Gas limit” (around 30 million), which hasn’t been adjusted for years. To increase throughput, the simplest way is to raise this limit, but without increasing hardware requirements or reducing decentralization.
Solution: This proposal suggests raising the default Gas limit to a new level (specific number 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 boosting TPS and alleviating network congestion and gas price spikes. However, it also demands higher hardware specs from validators, so the community will proceed cautiously.
Security and Stability! Building a Strong Network Defense
While expanding capacity, ensuring network security and stability is paramount. The Ethereum Foundation launched the “Trillion Dollar Security” plan in May 2025, aiming to build a secure Ethereum network capable of handling assets worth trillions. Several EIPs in Fusaka advance this plan, like installing more reliable “brakes” and “guardrails” on the high-speed Ethereum highway.
EIP-7934: Set Block Size Limit
Pain Point: Ethereum’s “block Gas limit” only considers computational load, not physical size. Attackers could craft “low-cost, large-volume” transactions (e.g., sending 0 ETH to many addresses) that are computationally cheap but physically huge, creating “data bombs” that slow network propagation and pose DoS risks.
Solution: Enforce a hard cap of 10MB on block size. Any block exceeding this size will be rejected.
Significance: Like setting maximum truck dimensions on a highway, this prevents “oversized” data vehicles from affecting traffic flow, 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 unfairness and security issues.
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 delaying others.
EIP-7823 & EIP-7883: Security Hardening for ModExp Precompile
Pain Point: ModExp (modular exponentiation) is used in cryptography but has two risks: input length can be unbounded, and its low Gas cost can be exploited for DoS attacks.
Solutions:
EIP-7823: Limit input length to 8192 bits, enough for practical use.
EIP-7883: Increase Gas costs for larger inputs, making attacks more expensive.
Significance: These measures remove a potential attack vector, like setting “maximum task size” and “tiered pricing” for a service, boosting network robustness.
Developer Tools! Empowering Application Builders
Beyond scalability and security, Fusaka introduces new tools for developers to build more powerful and efficient applications.
EIP-7951: Support for Mainstream Hardware Signatures
Pain Point: Devices like iPhones, bank U-shields, and hardware security modules often use the secp256r1 (P-256) standard, while Ethereum defaults to secp256k1. This mismatch limits direct secure interactions with Ethereum.
Solution: Add a precompiled contract to support and verify signatures from secp256r1.
Significance: This is a milestone—enabling Ethereum to directly support hundreds of millions of devices worldwide. You could sign Ethereum transactions directly with your phone’s security chip, simplifying user experience and increasing security, bridging Web2 and 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 ZK applications. Currently, there’s no direct opcode, so developers use complex Solidity code, which is costly and inefficient.
Solution: Add a “CLZ” (Count Leading Zeros) opcode to the EVM for one-step calculation.
Significance: This provides developers with a powerful, 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 are less perceptible to users but 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, which is time-consuming and high barrier. 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 receipt formats by removing unnecessary fields. This reduces the data size for full node sync by about 530GB.
Significance: This “lightens” nodes, making it easier for more people to run full nodes, strengthening decentralization and resilience.
EIP-7917: Deterministic Block Proposal Order and Pre-Confirmation
Pain Point: Current Layer 2 Rollups rely on a central sequencer, which can censor transactions or extract MEV, conflicting with decentralization. The “Based Rollup” idea proposes using L1 block proposers for ordering, inheriting L1’s decentralization. But this introduces delays, as Layer 2 must wait for L1 to finalize.
Solution: Modify consensus to precompute and publish the proposer order in advance, turning “random selection” into a publicly available “schedule”.
Significance: This is key for next-gen decentralized rollups. With a “schedule,” Layer 2 gateways can identify future proposers and negotiate pre-confirmations backed by penalties, enabling near-instant transaction finality while maintaining security. It opens a major door toward more decentralized scaling solutions.
Why Is Fusaka the Right Upgrade at the Right Time?
Fusaka isn’t just a technical upgrade; it’s a strategic move in Ethereum’s evolution amid the era of RWA and stablecoins on-chain. Currently, Ethereum hosts over 56% of the global stablecoin supply, becoming the core settlement layer of the digital dollar economy. Fusaka aims to prepare for Wall Street-scale assets and transaction volumes.
Custom chains for institutional Layer 2, providing unlimited “fuel” for expansion
As traditional finance enters, we’ll see more “dedicated chains” tailored for specific needs (like KYC compliance). These chains require Ethereum’s mainnet to provide massive, low-cost, secure data availability.
Proposals like EIP-7594, EIP-7892, and EIP-7918 are designed to meet this need. Their core goal: drastically reduce Layer 2 data publishing costs and enable flexible, 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” goal is a major vision. EIPs like EIP-7934, EIP-7825, EIP-7823, and EIP-7883 strengthen defenses, eliminate potential vulnerabilities, and push toward this target.
In summary, Fusaka’s main theme is clear and firm: scalability and security. With favorable regulation and market momentum, Fusaka arrives at an opportune moment. It will help Ethereum seize policy opportunities, solidify its dominance in stablecoins and on-chain assets, and transform from a “speculative asset” into 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 directly target scalability, security, and efficiency. It broadens Ethereum’s “value highway,” enhancing capacity and reliability, preparing for future mass adoption of users, assets, and applications.
For ordinary users, these changes may seem “silent,” but their impact will be profound. A stronger, more efficient, and safer Ethereum can realize grand visions once thought impossible—such as a global instant settlement network or “On-Chain Wall Street.” Fusaka is a solid step toward that future.
This article is based on publicly available information and does not constitute investment advice. Cryptocurrency investments carry significant risks; please decide carefully and DYOR.
If you enjoy this article, please follow, like, and share to support!
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
Scalability and Security in Parallel: 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 simple terms what problems they address and why they are crucial for Ethereum’s future.
Scalability! Making Ethereum Faster and More Capacity
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 are aimed at achieving this, especially focusing on reducing costs and improving efficiency for Layer 2 scaling solutions.
EIP-7594: PeerDAS - Data Availability Sampling
Pain Point: Since the Dencun upgrade introduced data “Blob” for low-cost data storage on Layer 2, a key issue arose: how to ensure the massive amount of data is truly available? Currently, each validator downloads and verifies all blob data in a block. When a block carries up to 9 Blobs, this is manageable. But if the number of Blobs increases (e.g., to 128), downloading and verifying all blobs becomes costly, raising the barrier for validators and threatening network decentralization.
Solution: PeerDAS (Peer Data Availability Sampling) turns the traditional “check all” approach into “sample check”. Simply put:
The network slices the complete blob data into pieces.
Validators don’t need to download all blobs—they randomly download and verify only a few data slices.
Validators then cross-check and exchange verification results to collectively confirm the integrity and availability of the entire blob data.
It’s like a big puzzle game: everyone has only a few pieces, but by checking key connection points, they can confirm the whole puzzle is intact. It’s worth noting that PeerDAS isn’t entirely new; its core idea of DAS has been successfully implemented in third-party projects like Celestia. Implementing PeerDAS is like filling a “technical 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 changes rapidly. Waiting for a major upgrade like Fusaka every time the Blob limit is adjusted is too slow and cannot keep pace with ecosystem growth.
Solution: This EIP defines a “Blob Parameter Only Hardfork (BPO)” mechanism. It’s a lightweight upgrade that only modifies a few parameters related to Blobs (e.g., target Blob count per block), without complex code changes. Node operators don’t even need to upgrade their clients—just accept the new parameters at a specified time, like updating a configuration file online.
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 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 unpredictable prices. When demand was low, fees dropped near zero, which didn’t stimulate new demand and created an “all-time low” price. When demand surged, fees spiked, creating extreme high prices. This “price competition” made fee planning difficult for Layer 2 projects.
Solution: EIP-7918’s core idea is to set a reasonable price range for Blob fees, with a flexible “minimum spend”. It links the upper and lower limits of Blob fees 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 fees to this “anchor” prevents wild price swings.
Significance: This prevents Blob fee “price wars,” making Layer 2 operating costs more predictable. As a result, Layer 2 projects can set more stable and reasonable transaction fees, avoiding rollercoaster experiences like “free today, expensive tomorrow.”
EIP-7935: Increasing Mainnet Transaction Capacity
Pain Point: The total transaction capacity per Ethereum block is limited by the “block Gas limit” (around 30 million), which hasn’t been adjusted for years. To increase throughput, the simplest way is to raise this limit, but without increasing hardware requirements or reducing decentralization.
Solution: This proposal suggests raising the default Gas limit to a new level (specific number 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 boosting TPS and alleviating network congestion and gas price spikes. However, it also demands higher hardware specs from validators, so the community will proceed cautiously.
Security and Stability! Building a Strong Network Defense
While expanding capacity, ensuring network security and stability is paramount. The Ethereum Foundation launched the “Trillion Dollar Security” plan in May 2025, aiming to build a secure Ethereum network capable of handling assets worth trillions. Several EIPs in Fusaka advance this plan, like installing more reliable “brakes” and “guardrails” on the high-speed Ethereum highway.
EIP-7934: Set Block Size Limit
Pain Point: Ethereum’s “block Gas limit” only considers computational load, not physical size. Attackers could craft “low-cost, large-volume” transactions (e.g., sending 0 ETH to many addresses) that are computationally cheap but physically huge, creating “data bombs” that slow network propagation and pose DoS risks.
Solution: Enforce a hard cap of 10MB on block size. Any block exceeding this size will be rejected.
Significance: Like setting maximum truck dimensions on a highway, this prevents “oversized” data vehicles from affecting traffic flow, 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 unfairness and security issues.
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 delaying others.
EIP-7823 & EIP-7883: Security Hardening for ModExp Precompile
Pain Point: ModExp (modular exponentiation) is used in cryptography but has two risks: input length can be unbounded, and its low Gas cost can be exploited for DoS attacks.
Solutions:
EIP-7823: Limit input length to 8192 bits, enough for practical use.
EIP-7883: Increase Gas costs for larger inputs, making attacks more expensive.
Significance: These measures remove a potential attack vector, like setting “maximum task size” and “tiered pricing” for a service, boosting network robustness.
Developer Tools! Empowering Application Builders
Beyond scalability and security, Fusaka introduces new tools for developers to build more powerful and efficient applications.
EIP-7951: Support for Mainstream Hardware Signatures
Pain Point: Devices like iPhones, bank U-shields, and hardware security modules often use the secp256r1 (P-256) standard, while Ethereum defaults to secp256k1. This mismatch limits direct secure interactions with Ethereum.
Solution: Add a precompiled contract to support and verify signatures from secp256r1.
Significance: This is a milestone—enabling Ethereum to directly support hundreds of millions of devices worldwide. You could sign Ethereum transactions directly with your phone’s security chip, simplifying user experience and increasing security, bridging Web2 and 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 ZK applications. Currently, there’s no direct opcode, so developers use complex Solidity code, which is costly and inefficient.
Solution: Add a “CLZ” (Count Leading Zeros) opcode to the EVM for one-step calculation.
Significance: This provides developers with a powerful, 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 are less perceptible to users but 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, which is time-consuming and high barrier. 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 receipt formats by removing unnecessary fields. This reduces the data size for full node sync by about 530GB.
Significance: This “lightens” nodes, making it easier for more people to run full nodes, strengthening decentralization and resilience.
EIP-7917: Deterministic Block Proposal Order and Pre-Confirmation
Pain Point: Current Layer 2 Rollups rely on a central sequencer, which can censor transactions or extract MEV, conflicting with decentralization. The “Based Rollup” idea proposes using L1 block proposers for ordering, inheriting L1’s decentralization. But this introduces delays, as Layer 2 must wait for L1 to finalize.
Solution: Modify consensus to precompute and publish the proposer order in advance, turning “random selection” into a publicly available “schedule”.
Significance: This is key for next-gen decentralized rollups. With a “schedule,” Layer 2 gateways can identify future proposers and negotiate pre-confirmations backed by penalties, enabling near-instant transaction finality while maintaining security. It opens a major door toward more decentralized scaling solutions.
Why Is Fusaka the Right Upgrade at the Right Time?
Fusaka isn’t just a technical upgrade; it’s a strategic move in Ethereum’s evolution amid the era of RWA and stablecoins on-chain. Currently, Ethereum hosts over 56% of the global stablecoin supply, becoming the core settlement layer of the digital dollar economy. Fusaka aims to prepare for Wall Street-scale assets and transaction volumes.
As traditional finance enters, we’ll see more “dedicated chains” tailored for specific needs (like KYC compliance). These chains require Ethereum’s mainnet to provide massive, low-cost, secure data availability.
Proposals like EIP-7594, EIP-7892, and EIP-7918 are designed to meet this need. Their core goal: drastically reduce Layer 2 data publishing costs and enable flexible, on-demand scaling.
For institutions managing trillions in assets, security is paramount. The “Trillion Dollar Security” goal is a major vision. EIPs like EIP-7934, EIP-7825, EIP-7823, and EIP-7883 strengthen defenses, eliminate potential vulnerabilities, and push toward this target.
In summary, Fusaka’s main theme is clear and firm: scalability and security. With favorable regulation and market momentum, Fusaka arrives at an opportune moment. It will help Ethereum seize policy opportunities, solidify its dominance in stablecoins and on-chain assets, and transform from a “speculative asset” into 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 directly target scalability, security, and efficiency. It broadens Ethereum’s “value highway,” enhancing capacity and reliability, preparing for future mass adoption of users, assets, and applications.
For ordinary users, these changes may seem “silent,” but their impact will be profound. A stronger, more efficient, and safer Ethereum can realize grand visions once thought impossible—such as a global instant settlement network or “On-Chain Wall Street.” Fusaka is a solid step toward that future.