Ethereum

Fusaka

Taiko

Blob

<a href="https://bsc.news/post/what-is-ethereum-eth-how-it-works-explained" rel="noopener noreferrer nofollow">Ethereum</a>’s&nbsp;<a href="https://bsc.news/post/ethereum-fusaka-upgrade" rel="noopener noreferrer nofollow">Fusaka upgrade</a>&nbsp;<a href="https://bsc.news/post/ethereum-fusaka-upgrade-live" rel="noopener noreferrer nofollow">went live</a> on December 3, reducing Layer 2 data costs, increasing network capacity, and strengthening the network’s core infrastructure. On top of this, Taiko COO Joaquin Mendes noted in a recent comment to BSCN that the upgrade also signals a shift in how Ethereum expects rollups to operate, especially those built around L1 sequencing such as Taiko.
Fusaka improves Ethereum’s data availability model, introduces deterministic proposer lookahead through EIP-7917, adjusts block parameters, and prepares the network for future rollup-heavy activity. For Taiko and other L1-sequenced rollups, these changes are substantial, practical, and highly technical. They affect how data flows, how validators coordinate, and how rollups confirm transactions.
<h2 id="span-span-strong-what-is-fusaka-and-why-does-it-matter-strong-span-span">What Is Fusaka and Why Does It Matter?</h2>
Ethereum relies on rollups for most transaction activity. When those rollups get expensive or congested, the entire ecosystem slows. Fusaka addresses this by improving how Ethereum handles data posted by rollups.
Fusaka’s main goals are as follows:
<ul>
 <li>Increase the amount of Layer 2 data Ethereum can safely handle</li>
 <li>Reduce blob costs so rollups become cheaper</li>
 <li>Improve validator efficiency</li>
 <li>Strengthen spam resistance</li>
 <li>Prepare Ethereum for the long-term Danksharding roadmap</li>
</ul>
This upgrade follows earlier steps in Ethereum’s evolution. The Merge introduced proof-of-stake. Pectra improved wallet functionality and validation rules. Fusaka now focuses on scaling Ethereum’s data layer, which is the foundation for rollups like Taiko.
From Taiko’s viewpoint, the most important elements are data availability improvements and deterministic proposer lookahead. Both directly affect how L1-sequenced rollups operate.
<h2 id="span-span-strong-how-does-fusaka-change-ethereum-s-data-model-strong-span-span">How Does Fusaka Change Ethereum’s Data Model?</h2>
Before going into Taiko’s interpretation, it is important to understand PeerDAS, the central feature of Fusaka.
<h3 id="span-span-strong-introduction-strong-span-span">Introduction</h3>
PeerDAS stands for Peer Data Availability Sampling. It changes how Ethereum verifies the large “blob” data that rollups publish.
<h3 id="span-span-strong-before-fusaka-strong-span-span">Before Fusaka</h3>
Every validator needed to download entire blobs. This worked when rollups produced less data, but it became a burden for home stakers with average internet connections.
<h3 id="span-span-strong-after-fusaka-strong-span-span">After Fusaka</h3>
Validators only verify small pieces of the data. Through erasure coding, Ethereum can still reconstruct the full data set even if each validator sees only a small slice.
<h3 id="span-span-strong-what-peerdas-achieves-strong-span-span">What PeerDAS Achieves</h3>
<ul>
 <li>Up to eight times more throughput for rollup data</li>
 <li>Around 85 percent lower bandwidth use for validators</li>
 <li>More decentralization since home stakers face smaller hardware requirements</li>
 <li>Faster settlement for rollup transactions</li>
</ul>
The logic is similar to checking random pages of a book instead of reading the entire book. If enough people check different pages, everyone knows the full book is intact.
This is a key part of Ethereum’s long-term plan. It makes large rollup ecosystems sustainable without turning Ethereum into a system that requires data center-grade hardware.
<h2 id="span-span-strong-is-fusaka-changing-ethereum-s-role-strong-span-span">Is Fusaka Changing Ethereum’s Role?</h2>
Mendes says yes, in a practical sense. Ethereum is no longer trying to handle all execution, computation, and settlement. Instead, it is positioning itself as a secure base layer for data availability and consensus.
From Taiko COO Joaquin Mendes:
<blockquote>
 “L1 isn’t trying to do everything for everyone anymore. It’s becoming infrastructure for data availability and consensus coordination, assuming rollups will handle execution.”
</blockquote>
This reflects the reality of today’s ecosystem. The highest-volume activity already happens on rollups. Fusaka reinforces this model by making it cheaper for rollups to post data and easier for validators to keep up.
But it also introduces new expectations. Rollups now require reliable blob access. Mendes notes that this means running beacon clients in semi-supernode or supernode configurations. It is a tradeoff: more throughput, but heavier requirements for rollup operators who rely heavily on blobs.
Taiko accepts this cost because the benefits to its architecture are significant.
<h2 id="span-span-strong-what-does-eip-7917-do-and-why-does-it-matter-for-taiko-strong-span-span">What Does EIP-7917 Do and Why Does It Matter for Taiko?</h2>
One of the most important elements of Fusaka is EIP-7917. It introduces deterministic proposer lookahead. This means Ethereum’s Beacon Chain now knows the upcoming block proposers for the next epoch.
<h3 id="span-span-strong-why-this-matters-strong-span-span">Why this matters</h3>
Rollups can now coordinate with future block proposers instead of waiting for blocks to be included. This enables&nbsp;preconfirmation mechanisms, which let a rollup commit to transaction inclusion before the actual block lands on-chain.
Taiko COO Joaquin Mendes explains:
<blockquote>
 “Rollups can now commit to transaction inclusion with upcoming validators instead of waiting for blocks to land. For based rollups specifically, this matters.”
</blockquote>
A “based rollup” is one that uses Ethereum’s L1 as the sequencer. Taiko follows this model. Because Taiko depends on L1 sequencing, having visibility into who will propose blocks gives it design advantages that other rollups cannot easily replicate.
<h3 id="span-span-strong-practical-benefits-for-taiko-strong-span-span">Practical benefits for Taiko</h3>
<ul>
 <li>Preconfirmations become possible</li>
 <li>Sequencing latency becomes more predictable</li>
 <li>The rollup can align its architecture with Ethereum’s timing</li>
 <li>Risk of reorg-related delays becomes easier to manage</li>
</ul>
This is a significant structural advantage for any rollup built around L1 sequencing.
<h2 id="span-span-strong-fusaka-s-phased-rollout-and-what-it-signals-strong-span-span">Fusaka’s Phased Rollout and What It Signals</h2>
Fusaka is not a single event. It is a phased upgrade:
<ul>
 <li>December 3: Fusaka activation</li>
 <li>December 9: Blob Parameter Only fork</li>
 <li>January 7: Second Blob Parameter Only fork</li>
</ul>
These smaller “parameter-only” forks allow Ethereum to increase blob capacity without performing a full hard fork. The network can now adjust to demand more frequently and with less complexity.
Mendes highlights this as a change in how Ethereum evolves:
<blockquote>
 “Ethereum can now iterate on DA capacity as demand requires rather than waiting for major upgrades.”
</blockquote>
This means rollups can plan with more clarity. For Taiko, it means a predictable scale-up path that fits its model of L1 sequencing.
<h2 id="span-span-strong-does-fusaka-affect-block-capacity-and-fee-stability-strong-span-span">Does Fusaka Affect Block Capacity and Fee Stability?</h2>
Fusaka increases the effective block gas limit from around 36 million to about 60 million. It also introduces new rules about blob pricing and block size.
Key changes include:
<ul>
 <li>EIP-7918: Adjusts blob fee pricing</li>
 <li>EIP-7934: Prevents oversized blocks</li>
 <li>EIP-7825: Introduces transaction gas limits inside blocks</li>
</ul>
<h3 id="span-span-strong-why-these-changes-matter-strong-span-span">Why these changes matter</h3>
<ul>
 <li>Rollups get more predictable posting slots</li>
 <li>Layer 2 fees stabilize</li>
 <li>Congestion spikes become less severe</li>
 <li>Ethereum becomes more reliable during high-volume periods</li>
</ul>
These mechanics support the goal of making Ethereum a strong data availability layer rather than a general-purpose settlement bottleneck.
<h2 id="span-span-strong-how-fusaka-improves-daily-user-experience-strong-span-span">How Fusaka Improves Daily User Experience</h2>
Most users will not need to take any direct action. But the effects appear across the ecosystem:
<ul>
 <li>Lower rollup fees</li>
 <li>Fewer failed transactions during busy market moments</li>
 <li>More stable&nbsp;<a href="https://bsc.news/post/decentralized-finance-defi-comprehensive-guide" rel="noopener noreferrer nofollow">DeFi</a> execution</li>
 <li>More responsive applications</li>
</ul>
<h3 id="span-span-strong-biometrics-and-secp256r1-strong-span-span">Biometrics and secp256r1</h3>
Fusaka adds support for the secp256r1 signature scheme. This makes it possible for smartphones to sign transactions using built-in hardware security features. In the future, users might approve transactions through Face ID or a fingerprint sensor rather than typing seed phrases.
This does not replace existing wallets, but it expands the design choices for wallet developers.
<h2 id="span-span-strong-conclusion-strong-span-span">Conclusion</h2>
Fusaka improves Ethereum’s data availability, reduces rollup costs, strengthens validation, expands block capacity, and enables deterministic proposer lookahead. These changes benefit the entire ecosystem, but they offer special advantages to L1-sequenced rollups like Taiko. The upgrade gives Ethereum a more efficient foundation and gives Taiko a clearer architectural roadmap. Fusaka focuses on capability increases rather than speculation, and its effects are already shaping how rollups prepare for the next stage of Ethereum’s scaling plan.
For Taiko, Fusaka expands the advantages of L1 sequencing. Deterministic proposer lookahead, greater blob capacity, and more predictable data availability allow Taiko to refine its architecture in ways that other rollup models cannot easily copy.
<h2 id="span-span-resources-span-span">Resources</h2>
<ol>
 <li><a href="https://x.com/ethereum/status/1996339856415342914" rel="noopener noreferrer nofollow">Ethereum on X</a>: Announcement (Dec. 3)</li>
 <li><a href="https://consensys.io/ethereum-fusaka-upgrade" rel="noopener noreferrer nofollow">Consensys Fusaka dashboard</a>: About Fusaka upgrade</li>
 <li><a href="https://blockworks.co/news/fusaka-update-today" rel="noopener noreferrer nofollow">Report by Blockworks</a>: Ethereum’s Fusaka upgrade lands today</li>
 <li><a href="https://docs.taiko.dev/" rel="noopener noreferrer nofollow">Taiko docs</a>: About Taiko</li>
</ol>

Taiko COO on What Fusaka Really Means for Ethereum

Table of Contents

BSCN

Other articles published on Dec 10, 2025

Join our free newsletter for daily crypto updates!