Ethereum Fusaka Upgrade Explained: How PeerDAS and EIP-7594 Will Transform L2 Scaling for Developers

Ethereum's next major hard fork, Fusaka, introduces PeerDAS via EIP-7594 to dramatically expand blob capacity and reduce Layer 2 transaction costs. A developer's guide to what's changing and how to prepare.

Ethereum Fusaka Upgrade Explained: How PeerDAS and EIP-7594 Will Transform L2 Scaling for Developers

Ethereum never sits still. Just over a year after the Pectra upgrade reshaped validator operations and introduced EIP-7702 account abstraction, the network is gearing up for its next major hard fork: Fusaka. At the center of Fusaka is PeerDAS, a data availability sampling mechanism defined by EIP-7594 that promises to dramatically increase blob throughput and push Layer 2 transaction costs even lower.

For web3 developers building on Ethereum and its rollup ecosystem, Fusaka is not just a protocol curiosity. It directly affects how much data your L2 can post, what your users pay in fees, and how you architect applications that depend on cheap, reliable data availability. Here is everything you need to know.

What Is the Fusaka Upgrade?

Fusaka is the codename for Ethereum's next planned hard fork following Pectra, which activated on mainnet in May 2025. While Pectra focused on validator experience, account abstraction, and blob gas adjustments, Fusaka zeroes in on scaling Ethereum's data layer.

The name follows Ethereum's tradition of naming upgrades after devcon host cities. Fusaka targets a significant leap in data availability capacity, which is the bottleneck that determines how cheaply rollups can operate. The headline feature is PeerDAS, but the upgrade also includes several smaller EIPs aimed at improving the networking layer and execution efficiency.

PeerDAS and EIP-7594: Data Availability Sampling Explained

PeerDAS stands for Peer Data Availability Sampling. It is specified in EIP-7594 and represents a fundamental shift in how Ethereum nodes verify that blob data is available without downloading every byte of it.

Today, after EIP-4844 introduced blob transactions, every Ethereum node must download and temporarily store all blob data. This works but it caps the number of blobs per block because the bandwidth requirement scales linearly with blob count. PeerDAS changes the game by letting nodes sample small random portions of blob data and use erasure coding to mathematically verify the full dataset's availability.

In practical terms, this means Ethereum can safely support far more blobs per block without requiring nodes to have proportionally more bandwidth. Estimates suggest PeerDAS could increase blob capacity by 4 to 8 times compared to the current post-Pectra baseline, with further increases possible in subsequent upgrades as the sampling model matures.

Why Fusaka Matters for L2 Developers

If you are building on any Ethereum rollup, whether optimistic or ZK-based, blob fees are one of your largest variable costs. When EIP-4844 launched in March 2024, it slashed L2 posting costs by over 90 percent overnight. But as rollup adoption has grown through 2025 and into 2026, blob space competition has increased and fees have started creeping upward during high-demand periods.

Fusaka directly addresses this by expanding blob supply. More blobs per block means lower blob base fees through the existing EIP-4844 fee market mechanism. For developers, this translates to cheaper calldata posting, more headroom for data-heavy applications like onchain gaming or social protocols, and less fee volatility during congestion spikes.

This is especially relevant for rollups that post frequently. High-throughput chains that settle every few seconds on Ethereum will see the most dramatic cost reductions because their blob consumption is continuous rather than bursty.

How PeerDAS Works Under the Hood

The technical mechanism behind PeerDAS involves three key components: erasure coding of blob data, random sampling by validators, and a peer-to-peer distribution protocol.

When a blob transaction is included in a block, the blob data is erasure-coded into extended data columns. This redundancy means that the full data can be reconstructed from any sufficiently large subset of columns. Validators then randomly sample a small number of columns from the network rather than downloading all of them. If enough randomly selected columns are available, the validator can be statistically confident that the entire dataset is available.

The peer-to-peer layer handles efficient distribution. Instead of broadcasting all blob data to every node, data columns are distributed across the network so that each node only needs to store and serve a subset. This distributes the bandwidth load while preserving the security guarantee that data cannot be withheld without detection.

For developers, the important takeaway is that this happens entirely at the consensus layer. Your smart contracts, rollup bridges, and application logic do not need to change. The benefits flow through automatically as lower blob fees and higher data throughput.

What Developers Should Do Now to Prepare

Even though Fusaka does not require changes to your smart contracts, there are several ways developers can prepare to take advantage of the upgrade.

First, review your rollup's data posting strategy. If you have been compressing data aggressively or batching transactions heavily to minimize blob costs, you may be able to relax some of those optimizations post-Fusaka. Posting data more frequently or in larger chunks could improve user experience by reducing confirmation latency without significantly increasing costs.

Second, consider building features that are currently cost-prohibitive. Applications that require high-frequency onchain data, like decentralized order books, real-time gaming state, or social feeds, become more viable when blob space is abundant and cheap. Now is the time to prototype and test these architectures on testnets.

Third, monitor blob fee markets. Tools and dashboards that track blob base fees, utilization rates, and rollup posting patterns will become essential for optimizing your deployment economics. Understanding the fee dynamics lets you make informed decisions about when to post and how much data to include.

Building for the Post-Fusaka Ethereum Ecosystem

Fusaka represents a clear signal that Ethereum's roadmap is delivering on its rollup-centric vision. Each upgrade makes the L1 a more capable data availability and settlement layer while pushing execution to L2s where developers have more flexibility and users get better performance.

For teams building across this expanding rollup ecosystem, the infrastructure layer matters as much as the protocol layer. You need reliable contract deployment, cross-chain tooling, and wallet infrastructure that works consistently whether your users are on Ethereum mainnet, an optimistic rollup, or a ZK chain. If you are looking for developer tools that scale across this multi-rollup landscape, thirdweb offers plans designed to grow with your project at thirdweb.com/pricing.

Timeline and What Comes After

As of June 2026, Fusaka is in active development with multiple Ethereum client teams implementing PeerDAS support. Testnet deployments are expected in the coming months, with a mainnet target that will depend on testing outcomes and client readiness. The Ethereum core developer community has been cautious about committing to exact dates, but the scope of Fusaka is intentionally narrower than Pectra to enable a faster development cycle.

Looking beyond Fusaka, the Ethereum roadmap includes further data availability improvements through full Danksharding, which would expand blob capacity by another order of magnitude. PeerDAS is an essential stepping stone toward that goal because it validates the sampling approach at a smaller scale before the network commits to the full Danksharding design.

The Bottom Line

Fusaka and PeerDAS mark the next major milestone in Ethereum's scaling roadmap. By introducing data availability sampling through EIP-7594, the upgrade will expand blob capacity, reduce rollup costs, and unlock new categories of data-intensive decentralized applications.

For web3 developers, the message is clear: the infrastructure is maturing rapidly, and the cost barriers that once limited onchain application design are falling with each upgrade. Whether you are building DeFi protocols, onchain games, or social platforms on rollups, Fusaka sets the stage for the next wave of growth in the Ethereum ecosystem.