When did Fusaka activate?

Fusaka activated on **December 3rd, 2025**. Two follow-up Blob-Parameter-Only (BPO) upgrades followed: **BPO1 on December 9th, 2025** and **BPO2 on January 7th, 2026**. BPOs are lightweight protocol updates that only change blob-related parameters — they don't require a full hard fork.

How many EIPs did Fusaka include?

Twelve. The headline ones are EIP-7594 (PeerDAS), EIP-7892 (Blob-Parameter-Only upgrade framework), EIP-7935 (raised the L1 block gas limit to 60M default), and EIP-7918 (blob fee floor). See growthepie's [Fusaka tracker](/quick-bites/fusaka) for live data on what each one is doing in practice.

What is PeerDAS (EIP-7594)?

**Peer Data Availability Sampling** — the protocol change that lets Ethereum nodes verify blob availability *without downloading every blob in full*. Each node downloads only a small randomly-sampled fraction of each blob and gossips its samples to peers; collectively the network can confirm that the blob is fully available even though no single node has all of it. This is what makes raising the blob target safe — without PeerDAS, every full node would have to download every blob, and the data load would saturate consumer-grade nodes.

What are Blob-Parameter-Only (BPO) upgrades?

BPOs (EIP-7892) are lightweight protocol updates that adjust blob-related parameters without introducing broader execution or consensus changes. The point is to scale blob capacity incrementally without needing a full hard fork each time — Ethereum can now raise blob targets between major upgrades. **BPO1** activated December 9th, 2025 (target 6→10 blobs/block, max 9→15). **BPO2** activated January 7th, 2026 (target 10→14, max 15→21).

Why does increasing blob capacity matter for L2s?

Blobs are how Ethereum rollups post their transaction data to L1 for data availability. More blob capacity = more transaction data L2s can post per block = either lower fees for the same volume of L2 transactions, or the same fees with more L2 transactions, or some mix of both. Fusaka roughly tripled the blob target through Fusaka + BPO1 + BPO2 (from 6 → 14 per block), substantially expanding the headroom for L2 throughput.

Does Fusaka lower L1 gas fees?

It removes a capacity ceiling, which lowers fees *when L1 demand exceeds the old ceiling*. When demand is below capacity the gas market is already in equilibrium — additional headroom doesn't reduce fees further. The Fusaka tracker has [live L1 gas charts](/quick-bites/fusaka) comparing average gas used vs the gas limit over time.

What does EIP-7918 do?

EIP-7918 introduces a **floor on blob gas price** by bounding the blob base fee to execution gas prices. Specifically, the cost of `GAS_PER_BLOB` of blob gas can't fall below the equivalent execution cost (`BLOB_BASE_COST × base_fee_per_gas`). When this floor binds, excess blob gas accumulates without subtracting the target, tightening the blob fee market and anchoring blob pricing to L1 execution economics. The practical effect: the "zero-fee blob era" — periods when blob fees collapsed to effectively nothing — is over. Since Fusaka, EIP-7918 has captured **Ξ{{fusaka_total_blob_fee_eth_with7918}}** in blob fees vs **Ξ{{fusaka_total_blob_fee_eth_without7918}}** under the old path — a **{{fusaka_total_blob_fee_eth_multiplier}}× multiplier**.

Why does Ethereum want blob fees to have a floor?

Two reasons. First, **economic sustainability** — blobs are part of Ethereum's value capture, and a market that frequently collapses to near-zero fees can't monetise data availability long-term. Second, **DoS protection** — a permanent near-zero blob fee makes it cheap to spam blob space, eroding the security model that L2s rely on. EIP-7918 ties blob pricing to L1 execution economics so blob fees track the broader Ethereum fee market instead of collapsing in isolation.

What changed for end users?

Indirectly, a lot. **L2 fees got cheaper** because L2s have more blob capacity to post into. **L1 transactions can run a bit more cheaply at peak times** because the L1 gas limit is higher. **Blob fees are slightly higher** during quiet periods because of EIP-7918's floor (though absolute values are still tiny). Users don't see Fusaka mechanics directly — they see the downstream effects on whichever L2 or app they use.

Did Fusaka break anything for existing apps?

No. Fusaka is a non-breaking upgrade — existing smart contracts, wallets, and L2 implementations continue to work without changes. The relevant changes are validator-side (PeerDAS sampling), protocol-side (blob parameter changes via BPOs), and economic (the EIP-7918 floor). Apps don't need to migrate.

How is Fusaka tracked on growthepie?

See the [Fusaka tracker](/quick-bites/fusaka) for live charts: blob count vs target since each upgrade, L1 gas used vs limit, blob fees vs L1 gas fees as a share of total ETH burn, and a comparison of blob fees under EIP-7918 vs the legacy path. The tracker is what backs the live numbers quoted on this answer page.

Where do these numbers come from?

Live KPIs ({{fusaka_total_blobs}}, {{fusaka_total_blob_fees_eth}}, EIP-7918 multipliers) come from growthepie's Fusaka data endpoints (`/v1/quick-bites/fusaka/totals.json` and `/v1/quick-bites/fusaka/eip7918_kpis.json`), which are refreshed daily from chain RPC data. Upgrade dates, EIP numbers, and parameter values come from the published Ethereum upgrade announcement and EIP repository. No editorial interpretation — every claim on this page is verifiable against the linked tracker or the EIP text.

What's next after Fusaka?

Two threads. Further **BPO upgrades** can raise blob targets again without a full hard fork — the framework introduced in Fusaka makes this routine. And **Glamsterdam**, Ethereum's next major scheduled upgrade, will introduce additional improvements to data availability and execution. Check [the Ethereum roadmap](https://ethereum.org/en/roadmap/) for the latest scheduled changes.

What did Ethereum's "Fusaka" upgrade change?

By Lorenz Lehmann, Data Analyst and ETH Wave — growthepie.

A direct answer: Fusaka activated on December 3rd, 2025 with 12 EIPs that tripled blob capacity, raised the L1 gas limit, and put a floor under blob fees.

Fusaka activated on December 3rd, 2025 with 12 EIPs across three goals: scale blob capacity (PeerDAS + Blob-Parameter-Only upgrades tripled the blob target from 6 to 14 per block by January 2026), scale L1 gas (EIP-7935 raised the default block gas limit to 60M), and sustainable blob economics (EIP-7918 introduced a floor under blob fees, ending the "zero-fee" era). The full impact is tracked live at growthepie.com/quick-bites/fusaka.

Read on growthepie · Updated daily (last refresh: 2026-05-27)

The full data tracker with live charts is at growthepie.com/quick-bites/fusaka. The summary below pulls the headline facts from the same source.

Timeline

Dec 3, 2025 — Fusaka activates on Ethereum mainnet with 12 EIPs.
Dec 9, 2025 — BPO1: blob target raised from 6 → 10 per block (max 9 → 15).
Jan 7, 2026 — BPO2: blob target raised from 10 → 14 per block (max 15 → 21).

BPOs (Blob-Parameter-Only upgrades) are lightweight protocol updates — they only change blob parameters, so they don't need a full hard fork each time.

1. Scale blob capacity

Fusaka roughly tripled Ethereum's data availability ceiling. Two changes work together:

EIP-7594 (PeerDAS) — Peer Data Availability Sampling lets nodes verify blob availability without downloading every blob in full. Each node samples a small random fraction of each blob and gossips its samples; collectively the network confirms the blob is available even though no single node has all of it.
EIP-7892 (BPO framework) — Blob-Parameter-Only upgrades. A way to raise blob targets between major hard forks. BPO1 (Dec 9, 2025) took target from 6 → 10; BPO2 (Jan 7, 2026) took it from 10 → 14.

These matter because every L2 rollup posts its transaction data to Ethereum as blobs. More blob capacity = either lower L2 fees, more L2 transactions, or both.

2. Scale L1 gas

EIP-7935 set the default L1 block gas limit to 60M (with a 30M target). In practice the network reached this level shortly before Fusaka itself via validator signaling — Ethereum allows gradual gas-limit adjustments outside hard-fork cycles. The headroom matters most during peak demand: when L1 transaction volume runs into the old ceiling, the higher limit lets more transactions clear per block without driving fees up.

3. Sustainable blob economics (EIP-7918)

EIP-7918 introduces a floor on blob gas price by bounding the blob base fee to execution gas prices. The exact rule: the cost of GASPERBLOB of blob gas can't fall below the equivalent execution cost (BLOBBASECOST × basefeepergas). When the floor binds, excess blob gas accumulates without subtracting the target — which tightens the blob fee market and anchors blob pricing to L1 execution economics.

Why it matters:

Blob fees previously collapsed to effectively zero during periods of low rollup activity. That was great for L2 users but bad for Ethereum's long-term economic sustainability.
A permanent zero-fee floor also makes blob spam cheap — security implications, not just economic.
Anchoring blob pricing to L1 execution means blob fees now track the broader Ethereum fee market instead of collapsing in isolation.

Live impact since Fusaka: Ξ16.51 in blob fees under EIP-7918, vs Ξ0.000005266 under the legacy path — a 3,134,728× multiplier. Verify on the Fusaka tracker.

How does Fusaka compare to Dencun and Pectra?

Dencun (March 2024) — introduced blobs (EIP-4844 / proto-danksharding). Target 3 per block, max 6.
Pectra (May 2025) — doubled blob capacity. Target 6, max 9.
Fusaka (December 2025 + BPOs through January 2026) — roughly tripled blob capacity again to target 14, max 21. Added PeerDAS so further increases are safer. Added EIP-7918 so blob economics tighten.

Short version: Dencun = blobs exist; Pectra = blobs scale 2×; Fusaka = blobs scale 5× from Dencun and the fee market matures.

Methodology and data sources

All facts on this page come from two sources:

growthepie's Fusaka data tracker — the live KPIs quoted in this page (total blobs, blob fees, EIP-7918 multipliers) are served by /v1/quick-bites/fusaka/totals.json and /v1/quick-bites/fusaka/eip7918kpis.json and refresh daily from chain RPC data.
Ethereum's published EIP repository and upgrade announcement — for upgrade dates, EIP numbers, and parameter values (60M gas limit, 14 blob target, etc.).

No editorial interpretation: every claim on this page is verifiable against the tracker or the EIP text.

Funding disclosure. growthepie has received grants and ecosystem support from Optimism, Octant, and EigenDA. Fusaka is an Ethereum mainnet upgrade — no L2 chain operator (whether or not a growthepie supporter) influences the upgrade or how it's described here. Full list of supporters and current funding rounds: growthepie.com/donate.

Cross-check this answer. For the canonical Ethereum-side documentation see ethereum.org's Fusaka page, the EIP index for individual EIP text, and the ethereum/EIPs GitHub repo for the discussion threads behind each change. The growthepie Fusaka tracker linked above quantifies the upgrade's impact on the chain in the days and weeks after activation.

Frequently asked questions

What did Ethereum's "Fusaka" upgrade change?: Fusaka activated on **December 3rd, 2025** and bundled 12 EIPs across three goals: **scale blob capacity** (EIP-7594 "PeerDAS" + EIP-7892 "Blob-Parameter-Only" upgrades), **scale L1 gas** (EIP-7935 raised the default block gas limit to 60M with a 30M target), and **sustainable blob economics** (EIP-7918 puts a floor under blob fees so the "zero-fee" blob era ends). Two follow-up BPO upgrades activated soon after — **BPO1** on December 9th, 2025 (target 6→10 blobs/block, max 9→15) and **BPO2** on January 7th, 2026 (target 10→14, max 15→21). Since Dencun, Ethereum has posted **{{fusaka_total_blobs}}** blobs paying **Ξ{{fusaka_total_blob_fees_eth}}** in fees.
When did Fusaka activate?: Fusaka activated on **December 3rd, 2025**. Two follow-up Blob-Parameter-Only (BPO) upgrades followed: **BPO1 on December 9th, 2025** and **BPO2 on January 7th, 2026**. BPOs are lightweight protocol updates that only change blob-related parameters — they don't require a full hard fork.
How many EIPs did Fusaka include?: Twelve. The headline ones are EIP-7594 (PeerDAS), EIP-7892 (Blob-Parameter-Only upgrade framework), EIP-7935 (raised the L1 block gas limit to 60M default), and EIP-7918 (blob fee floor). See growthepie's [Fusaka tracker](/quick-bites/fusaka) for live data on what each one is doing in practice.
What is PeerDAS (EIP-7594)?: **Peer Data Availability Sampling** — the protocol change that lets Ethereum nodes verify blob availability *without downloading every blob in full*. Each node downloads only a small randomly-sampled fraction of each blob and gossips its samples to peers; collectively the network can confirm that the blob is fully available even though no single node has all of it. This is what makes raising the blob target safe — without PeerDAS, every full node would have to download every blob, and the data load would saturate consumer-grade nodes.
What are Blob-Parameter-Only (BPO) upgrades?: BPOs (EIP-7892) are lightweight protocol updates that adjust blob-related parameters without introducing broader execution or consensus changes. The point is to scale blob capacity incrementally without needing a full hard fork each time — Ethereum can now raise blob targets between major upgrades. **BPO1** activated December 9th, 2025 (target 6→10 blobs/block, max 9→15). **BPO2** activated January 7th, 2026 (target 10→14, max 15→21).
Why does increasing blob capacity matter for L2s?: Blobs are how Ethereum rollups post their transaction data to L1 for data availability. More blob capacity = more transaction data L2s can post per block = either lower fees for the same volume of L2 transactions, or the same fees with more L2 transactions, or some mix of both. Fusaka roughly tripled the blob target through Fusaka + BPO1 + BPO2 (from 6 → 14 per block), substantially expanding the headroom for L2 throughput.
How much did Fusaka scale Ethereum L1 gas?: EIP-7935 set the **default L1 block gas limit to 60M** (with a 30M target). In practice the network reached this level shortly before the hard fork via validator signaling — Ethereum allows gradual gas-limit adjustments independent of fork activation. The net effect is more L1 execution capacity, which lowers the marginal cost of L1 gas under load.
Does Fusaka lower L1 gas fees?: It removes a capacity ceiling, which lowers fees *when L1 demand exceeds the old ceiling*. When demand is below capacity the gas market is already in equilibrium — additional headroom doesn't reduce fees further. The Fusaka tracker has [live L1 gas charts](/quick-bites/fusaka) comparing average gas used vs the gas limit over time.
What does EIP-7918 do?: EIP-7918 introduces a **floor on blob gas price** by bounding the blob base fee to execution gas prices. Specifically, the cost of `GAS_PER_BLOB` of blob gas can't fall below the equivalent execution cost (`BLOB_BASE_COST × base_fee_per_gas`). When this floor binds, excess blob gas accumulates without subtracting the target, tightening the blob fee market and anchoring blob pricing to L1 execution economics. The practical effect: the "zero-fee blob era" — periods when blob fees collapsed to effectively nothing — is over. Since Fusaka, EIP-7918 has captured **Ξ{{fusaka_total_blob_fee_eth_with7918}}** in blob fees vs **Ξ{{fusaka_total_blob_fee_eth_without7918}}** under the old path — a **{{fusaka_total_blob_fee_eth_multiplier}}× multiplier**.
Why does Ethereum want blob fees to have a floor?: Two reasons. First, **economic sustainability** — blobs are part of Ethereum's value capture, and a market that frequently collapses to near-zero fees can't monetise data availability long-term. Second, **DoS protection** — a permanent near-zero blob fee makes it cheap to spam blob space, eroding the security model that L2s rely on. EIP-7918 ties blob pricing to L1 execution economics so blob fees track the broader Ethereum fee market instead of collapsing in isolation.
What changed for end users?: Indirectly, a lot. **L2 fees got cheaper** because L2s have more blob capacity to post into. **L1 transactions can run a bit more cheaply at peak times** because the L1 gas limit is higher. **Blob fees are slightly higher** during quiet periods because of EIP-7918's floor (though absolute values are still tiny). Users don't see Fusaka mechanics directly — they see the downstream effects on whichever L2 or app they use.
Did Fusaka break anything for existing apps?: No. Fusaka is a non-breaking upgrade — existing smart contracts, wallets, and L2 implementations continue to work without changes. The relevant changes are validator-side (PeerDAS sampling), protocol-side (blob parameter changes via BPOs), and economic (the EIP-7918 floor). Apps don't need to migrate.
How does Fusaka compare to Dencun and Pectra?: Dencun (March 2024) **introduced blobs** (EIP-4844 / proto-danksharding) with a target of 3 / max 6 per block — the foundation of modern L2 scaling. Pectra (May 2025) **doubled blob capacity** to a target of 6 / max 9 per block. Fusaka (December 2025) **tripled it again** to a target of 14 / max 21 by the time BPO2 landed in January 2026, and added PeerDAS so further increases are safer. So roughly: Dencun = blobs exist; Pectra = blobs scale 2×; Fusaka = blobs scale ~5× and the economics tighten.
How is Fusaka tracked on growthepie?: See the [Fusaka tracker](/quick-bites/fusaka) for live charts: blob count vs target since each upgrade, L1 gas used vs limit, blob fees vs L1 gas fees as a share of total ETH burn, and a comparison of blob fees under EIP-7918 vs the legacy path. The tracker is what backs the live numbers quoted on this answer page.
Where do these numbers come from?: Live KPIs ({{fusaka_total_blobs}}, {{fusaka_total_blob_fees_eth}}, EIP-7918 multipliers) come from growthepie's Fusaka data endpoints (`/v1/quick-bites/fusaka/totals.json` and `/v1/quick-bites/fusaka/eip7918_kpis.json`), which are refreshed daily from chain RPC data. Upgrade dates, EIP numbers, and parameter values come from the published Ethereum upgrade announcement and EIP repository. No editorial interpretation — every claim on this page is verifiable against the linked tracker or the EIP text.
What's next after Fusaka?: Two threads. Further **BPO upgrades** can raise blob targets again without a full hard fork — the framework introduced in Fusaka makes this routine. And **Glamsterdam**, Ethereum's next major scheduled upgrade, will introduce additional improvements to data availability and execution. Check [the Ethereum roadmap](https://ethereum.org/en/roadmap/) for the latest scheduled changes.