================== Nethermind initialization completed ===================

RPC modules: Eth, Net, Parity, Personal, Proof, Rpc, Subscribe, Trace,
TxPool, Web3
Mem est tx : 82MB
Mem est DB : 0MB
JSON RPC : http://127.0.0.1:8545 ; http://localhost:8551
Genesis hash : 0xd4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3
Client id : Nethermind/v1.17.3+671d60ad/windows-x64/dotnet7.0.4
Chainspec : chainspec/foundation.json
Chain ID : MainnetChain head : 16974933 (0x63593f...d919f0)

==========================================================================

nethermind ethereum client

The Ethereum Execution Client Built on .NET

Nethermind is the fastest Ethereum execution client on independent benchmarks, and the most configurable on how you sync and extend it. Written in C# on .NET. Run the node that answers your own queries, holding only the history your policy requires, with every answer checkable against the chain.

Download Client

Client docs

Nethermind Client is the engineering foundation of Bedrock, Nethermind's institutional infrastructure. Learn about Bedrock

RPC modules: Eth, Net, Parity, Personal, Proof, Rpc, Subscribe, Trace, TxPool, Web3
Mem est tx : 82MB
Mem est DB : 0MB
JSON RPC : http://127.0.0.1:8545 ; http://localhost:8551
Genesis hash : 0xd4e56740f876aef8c010b86a40d5f56745a118d0
906a34e69aec8c0db1cb8fa3
Client id : Nethermind/
v1.17.3+671d60ad/windows-x64/dotnet7.0.4
Chainspec : chainspec/foundation.json
Chain ID : Mainnet
Chain head : 16974933

3x

faster block processing than Nethermind Client V1

2019

In production on Ethereum mainnet

~30%

of visible Ethereum execution nodes, per ethernodes.org

2 PoCs

compliance controls validated at the node with UBS

Sole

execution client through the Gnosis Chain merge

What is an Ethereum execution client?

Every Ethereum node runs two pieces of software. The consensus client follows the proof-of-stake chain and decides which block comes next. The execution client holds the state, runs transactions through the Ethereum Virtual Machine, and answers queries about what the chain contains.

Nethermind is an Ethereum execution client. Run it alongside a consensus client and you have an Ethereum node.

What's in Nethermind 2.0.0

Version 2.0.0 is a major release with breaking changes. Archive operators, teams running custom configurations, and plugin authors should read the upgrade guidance before updating. Nethermind is ready for the current Fusaka fork and the upcoming Glamsterdam fork. Nethermind engineers co-authored seven of the 12 EIPs included in Fusaka and five in Glamsterdam.

Release notes

Why choose Nethermind

Nethermind is built for speed at the tip, history you can size, and extension without forking.

performance

Faster blocks without bigger hardware

Nethermind 2.0.0 processes the average block around three times faster at the tip of the chain than V1, and the slowest blocks improve most, around eight times faster at the 99th percentile.

The flat database layout is what makes it possible. Full measurements are in the 2.0.0 benchmark post.

3x

faster block processing than V1

history

History that fits the use case, and proofs to match

Historical state used to be all or nothing. You either ran a full archive node and paid for the disk, or you rented access to someone else's. Nethermind serves it four ways: a full archive, history from a block you name forward, a rolling window, or deeper history only for the contracts you query. All built through ordinary syncing, all verifiable against block headers. Version 2.0.0 also serves historical eth_getProof, on a flat archive, with proof depth configurable rather than all or nothing: full-chain coverage, or recent epochs only, sized to the disk you want to spend. In our testing across 25 block heights, Nethermind returned proofs around 6x faster than Erigon while running on half the CPU and memory.

6x

faster than Erigon

JSON-RPC

RPC that holds up when the traffic arrives

If you answer other people's queries, the tail is what they notice. A node that handles the median request quickly and the slow one badly still reads as a slow node. Version 2.0.0 improves tail latency more than it improves the mean. Twenty-four JSON-RPC modules, ten enabled by default and tracing among them, with lower allocation on hot eth_call paths and faster eth_getLogs at scale.

24

modules, 10 on by default

Extensibility

Extend it without forking it

Most teams that need something specific from a client end up maintaining a fork of it, and then maintaining that fork forever. Plugins mean you add what you need and still take every upstream release untouched. Supported types cover RPC, block tree visitors, devp2p, state visitors, configuration, the transaction pool, tracers, and the CLI. Support and maintenance are available for enterprise users.

8

plugin extension points

Compliance

Infrastructure you can answer for

Banks, custodians, asset managers and compliance providers face a question most node operators do not: where did this answer come from, and can you evidence it later.

Running your own node answers it. Nethermind is written in C# on .NET, the same stack many financial institutions already build on, and it returns verifiable responses for state, receipts, logs, and history queries, each checkable against the relevant block header rather than taken on a provider's word. Teams that want this operated rather than built in house can use Bedrock, Nethermind's institutional infrastructure, or our managed node operation.

2

proofs of concept with UBS

client diversity

A bug in one client should not be able to stop Ethereum

When a single implementation runs most of the network, its bugs stop being that client’s problem and become everyone’s. Which client you run is a decision with consequences past your own node.

Nethermind runs approximately a third of visible execution nodes, and was the sole execution client that carried Gnosis Chain through its move to proof of stake.

~1/3

of visible execution nodes

Nethermind Ethereum client features

Snap sync and snap serving

Sync to the tip without downloading every state node, and serve snap data so other nodes can sync from yours.

Archive and windowed history

Keep only the history you actually query, from a full archive down to selected contracts.

JSON-RPC

Serve your own applications from your own node. Twenty-four modules, ten on by default.

Plugin framework

Extend the client without forking it: RPC, devp2p, tracers, txpool, and CLI.

Monitoring

See what your node is doing, through Grafana dashboards, Seq logging, and durable sync-time metrics.

Platform support

Run it on hardware you already have: Linux, Windows, and macOS, on x86-64 and ARM64.

History expiry

Prune local history and re-import any block range from a verified archive.

Hardened networking

Your node checks what a peer sends before acting on it, and caps what one connection can cost.

Tested at production scale

Our full CI matrix performs over 2.3 million test executions per full CI run, covering unit tests, Ethereum fixtures, and end-to-end scenarios across multiple platforms and configurations.

Which Ethereum execution client should you choose?

Most of the decision comes down to seven questions, and they are worth asking of any Ethereum execution client you consider.

?

What runtime does it use, and does that match your stack?

Nethermind is written in C# on .NET, which matters if your team already operates .NET infrastructure or wants to read and extend the client itself.

?

Will your existing tooling work against it?

Nethermind's JSON-RPC matches Geth's behavior, so tools and libraries written against Geth work unchanged.

?

Can it serve other nodes, not just sync from them?

Nethermind does both, so your own nodes can bootstrap from each other instead of depending on public peers.

?

Does it serve the history you need?

Nethermind serves four shapes of history, and historical eth_getProof across three of them, as described above.

?

Can you extend it without forking it?

Nethermind's plugin framework covers the extension points listed above.

?

Where will it run?

Linux, Windows, and macOS, on x86-64 and ARM64.

?

Who maintains it, and how much of the network runs it?

Nethermind is maintained independently of the dominant implementation.

Who runs Nethermind

Node operators and stakers

Sync to the tip, stay current through forks, and keep the number of moving parts small.

RPC providers

Tail latency improves more than the mean, which is what your users feel during a spike.

Data and indexing teams

Keep the history your pipeline actually reads instead of provisioning a full archive for every workload.

Layer 2 and app-chain teams

A maintained client with a plugin model. For client work beyond the standard model, our Blockchain Core Engineering team takes it on directly.

Institutions and enterprises

Evidence where every answer came from, and shape retention around your obligations.

Networks

Ethereum mainnet and the public testnets, plus Gnosis Chain, XDC and OP Stack chains.

Frequently asked questions

Common questions about running the Nethermind Ethereum client.

Does Nethermind support archive nodes?

Yes. A full archive, history from a block you name forward, a rolling window, or deeper history only for the contracts you query. All on the flat database layout.

What networks does Nethermind support?

Ethereum mainnet and the public testnets, plus Gnosis Chain, XDC, and OP Stack chains. Nethermind also runs networks that need client-side features outside the standard Ethereum execution model. For the full set, see Blockchain Core Engineering.

Is Nethermind the fastest client?

Yes, on independent measurements. Block processing across execution clients is measured continuously on identical hardware by parties we do not control, and Nethermind leads on most of those measurements as of September 2026. We publish our own benchmark configuration and costs alongside every gain we claim, so the numbers can be checked rather than taken on trust.

Is Nethermind open source and free to run?

Yes, and free to run. The source is on GitHub under LGPL-3.0. We also offer managed node operation for teams that would rather not run it themselves.

Latest articles

Ethereum

nethermind ethereum client

The Ethereum Execution Client Built on .NET

Nethermind is the fastest Ethereum execution client on independent benchmarks, and the most configurable on how you sync and extend it. Written in C# on .NET. Run the node that answers your own queries, holding only the history your policy requires, with every answer checkable against the chain.

3x

2019

~30%

2 PoCs

Sole

What is an Ethereum execution client?

What's in Nethermind 2.0.0

Why choose Nethermind

3x

6x

24

8

2

~1/3

Nethermind Ethereum client features

Snap sync and snap serving

Archive and windowed history

JSON-RPC

Plugin framework

Monitoring

Platform support

History expiry

Hardened networking

Tested at production scale

Which Ethereum execution client should you choose?

?

What runtime does it use, and does that match your stack?

?

Will your existing tooling work against it?

?

Can it serve other nodes, not just sync from them?

?

Does it serve the history you need?

?

Can you extend it without forking it?

?

Where will it run?

?

Who maintains it, and how much of the network runs it?

Who runs Nethermind

Node operators and stakers

RPC providers

Data and indexing teams

Layer 2 and app-chain teams

Institutions and enterprises

Networks

Frequently asked questions

Latest articles

Our Open Source Response to AI

Flat DB: A New State Storage Architecture in Nethermind

Why Large-Scale eth_getLogs Queries Are Slow and How Log Index Fixes It

Architecting Ethereum’s Future: Fusaka, Institutions, and Nethermind’s Role

Getting Ethereum Ready for GigaGas

Verifiable Autonomy: Building Ethereum's Agentic Infrastructure

Measuring Ethereum's Execution Limits: The Gas Benchmarking Framework

Shaping Fusaka: Nethermind’s 7 EIPs for Ethereum’s Next Upgrade

Road to ZK Implementation: Nethermind Client’s Path to Proofs

Run it, break it, tell us what happened

Nethermind is built in the open, and operator feedback shapes what ships next. Come tell us how your node is running.