// inside head tag
Ethereum’s Fusaka upgrade, activated on 3 December 2025, reinforces the network’s position as the primary public settlement environment for tokenized assets, rollups, and institutional-scale activity.
For most investors, banks, and asset managers, Fusaka is not about new jargon. It is about whether Ethereum can handle growing Layer 2 activity, tokenized assets, and higher transaction volumes without introducing new fragility. It reduces node overhead, improves data handling for rollups, and makes settlement more predictable.
Behind these changes lies work that often goes unnoticed in headlines. Ethereum’s behavior is defined and delivered by its client teams. In Fusaka, Nethermind engineers co-authored a majority of the execution layer proposals and helped design the benchmarking framework that underpins safe gas limit increases. This work quietly forms the foundation for institutional adoption.
Fusaka is often described as a “data availability” and “scaling” upgrade. In institutional terms, three themes matter.
Most Ethereum activity now flows through Layer 2 rollups. These systems post compressed transaction data to Ethereum in the form of “blobs”. Until now, validators had to download and verify entire blobs, which added bandwidth and storage pressure.
Fusaka introduces Peer Data Availability Sampling (PeerDAS). Instead of handling all data, each node verifies small, randomly assigned slices. Data is encoded so that the full blob can still be reconstructed if a sufficient share of slices is available. For institutions that run validators or nodes, this means:

Cheap transactions are useful. Predictable transaction costs are more important for institutional planning. Fusaka delivers this through three mechanisms:
The result: a fee environment that behaves more consistently under load, which is what matters when running production systems.

Institutions care about transaction finality and thepredictablility of that path. Fusaka improves this by:
These are not headline features, but they are the kind of refinements that reduce edge cases and operational surprises.
Ethereum upgrades are not decided in a vacuum. They are proposed, tested, and refined by the teams who implement the protocol in clients. For Fusaka, Nethermind engineers helped shape the execution layer at the specification level, not just in code.
Nethermind’s contributions cluster in three areas that matter for institutions.
One of the most visible changes is the removal of unnecessary data from Ethereum’s networking messages. Over time, nodes were regenerating, and shipping fields that syncing peers immediately discarded. This was wasting hundreds of gigabytes of bandwidth per sync.
Nethermind engineers co-authored the proposal that simplifies these receipts and introduces “history serving windows”, which let nodes advertise which parts of history they hold. This supports the network’s long-term move to more efficient history storage and reduces the cost of running infrastructure today.
Ethereum can only raise its gas limit if every client can handle worst-case blocks. If one implementation falls behind, the network as a whole is at risk.
Nethermind originated Gas Benchmarks, a framework that builds blocks out of single operations or precompiles, then measures how fast each client can process them under stress. This work started as a Nethermind experiment funded by a Worldcoin grant and is now a common standard used by the Ethereum Foundation and all major client teams.

The first major outcome was ModExp repricing. Tests showed that certain cryptographic operations were much slower than their gas costs implied, across all clients. The result was a protocol change, coordinated optimisations in implementations, and a clear, data based path to higher gas limits. That process now underpins decisions around moving from 36 million to 45 million gas, and toward 60 million and beyond.
Gas limit changes are now grounded in shared, repeatable benchmarks, rather than intuition. Nethermind played a central role in establishing that standard.
Several Fusaka proposals authored or co-authored by Nethermind engineers shape how Ethereum behaves under load and how applications can reason about settlement.
These details matter because they translate into fewer failure modes, more transparent pricing, and a smoother experience for applications built on top.
Fusaka arrives at a time when tokenized real-world assets on Ethereum have surpassed the multi-billion-dollar mark, and large asset managers are expanding their on-chain activities. At the same time, most user transactions are moving to rollups that rely on Ethereum for settlement and data availability. For these users, “scaling” is not an abstract goal. It is a requirement for:
Fusaka strengthens Ethereum’s position in this environment. It enables more rollup activity at lower infrastructure costs, improves fee behavior, and refines the mechanics of settlement. It also demonstrates that upgrades are informed by data and operational experience, rather than solely by theory.
The next stages of Ethereum’s roadmap, including further rollup scaling and forms of parallel execution, will only increase the demands placed on execution clients. Each step will require the same combination of research, specification work, benchmarking, and careful implementation that defined Fusaka.
Nethermind is one of the teams doing that work. By co-authoring core proposals, running and sharing benchmarks, and shipping a production-grade client, the team helps ensure that Ethereum grows in ways that institutions can rely on.
Fusaka is not just a code change. It is evidence that Ethereum’s infrastructure is being engineered and validated with the level of discipline that long-term capital expects, and Nethermind is one of the primary architects behind that shift.