HomeEIPsNewsletter

Fusaka Upgrade

Enhancements to Ethereum's Scalability and Data Availability

The Fusaka upgrade introduces foundational improvements to Ethereum, focusing on data availability, Layer 2 scaling, and preparing the network for full Danksharding. Key components include technologies such as PeerDAS, which allow nodes to specialize in storing different pieces of data while still verifying overall availability, significantly increasing Layer 2 network capacity while maintaining security.

Fusaka Upgrade

Fusaka Mainnet Fork NFT

Loading information from smart contract…OpenSeaEtherscan

Mint Configuration

Wallet

Not connected

Whitelist

Supply

Whitelist cap

Public cap

Whitelist price

Public price

Transferable

Whitelist start

Public start

Mint has not started yet.
Fusaka NFT

What is the Fusaka Upgrade?

Fusaka enhances Ethereum’s ability to handle high-throughput Layer 2 applications, reduces transaction costs, and strengthens the network’s readiness for future scaling solutions. The name “Fusaka” is a combination of Fulu and Osaka: Fulu is a star representing the consensus layer upgrade, while Osaka is the city representing the execution layer upgrade.

Related EIPs for this upgrade

EIP 7594
PeerDAS - Peer Data Availability Sampling
PeerDAS lets nodes sample and serve different pieces of data while keeping availability verifiable, massively boosting data throughput for rollups.
Learn more
EIP 7823
Set upper bounds for MODEXP
Caps each MODEXP input to 8192 bits to reduce consensus risk from unbounded inputs and simplify future replacements.
Learn more
EIP 7825
Transaction Gas Limit Cap
Sets a 16,777,216 gas cap per transaction to prevent single-tx block domination and improve stability.
Learn more
EIP 7883
ModExp Gas Cost Increase
Raises gas costs for the ModExp precompile (e.g., from 200 to 500 base) to better price heavy operations.
Learn more
EIP 7917
Deterministic proposer lookahead
Stores a deterministic proposer schedule ahead of time so apps can know future proposers for MEV mitigation and coordination.
Learn more
EIP 7918
Blob base fee bounded by execution cost
Ensures blob gas has a reserve price tied to execution gas so the blob market cannot collapse to 1 wei when execution dominates.
Learn more
EIP 7934
RLP Execution Block Size Limit
Adds a ~10 MiB cap (incl. 2 MiB beacon margin) on RLP-encoded block size to avoid propagation/DoS issues.
Learn more
EIP 7939
Count leading zeros (CLZ) opcode
Introduces a native opcode to count leading zero bits in a 256-bit word, making math/crypto primitives cheaper.
Learn more
EIP 7951
Precompile for secp256r1 Curve Support
Adds a secp256r1 (P-256) signature verification precompile, enabling common device ecosystems and wallets. Supersedes RIP-7212.
Learn more
EIP 7892
Blob Parameter Only ('BPO') Hardforks
Defines lightweight blob-only hardforks so Ethereum can tune blob capacity more frequently.
Learn more
EIP 7642
eth/69 - Drop pre-merge fields
Eth/69 p2p upgrade: advertise served history window, drop unused total difficulty from handshake, remove receipt blooms. Clients MUST support this for Fusaka activation.
Learn more
EIP 7910
eth_config JSON-RPC Method
Adds eth_config to expose current/next fork config over RPC. Clients MUST support this by Fusaka activation.
Learn more
EIP 7935
Set default gas limit to 60M
Updates client defaults to 60M gas (from 36M) to align with Fusaka expectations; requires careful testing by client teams.
Learn more

How do Ethereum network upgrades work?

Ethereum network upgrades require explicit opt-in from node operators on the network. While client developers come to consensus on what EIPs are included in an upgrade, they are not the ultimate deciders of its adoption.

For the upgrade to go live, validators and non-staking nodes must manually update their software to support the protocol changes being introduced.

If they use an Ethereum client that is not updated to the latest version, at the fork block, it will disconnect from upgraded peers, leading to a fork on the network. In this scenario, each subset of the network nodes will only stay connected with those who share their (un)upgraded status.

While most Ethereum upgrades are non-contentious and cases leading to forks have been rare, the option for node operators to coordinate on whether to support an upgrade or not is a key feature of Ethereum's governance.

Serve Ethereum Builders, Scale the Community.
Resources
GitHub