Nethermind Adds Policy Controls For Node Operators

Nethermind published Nethermind 2.2.0 on Oct. 16, 2026, an Ethereum execution client release that adds an opt-in SendPolicy plugin. NFA.

Release Overview

Nethermind 2.2.0 launched on GitHub on Oct. 16, 2026. The release focuses on tools that let node operators manage transaction behavior and improve trace compatibility with other clients.

SendPolicy Plugin

The opt-in SendPolicy plugin checks every transaction sent through the node’s JSON-RPC against a rule file written by the node owner. The plugin refuses transactions that break those rules. Rules can cover allowed senders, destinations and token calls. The plugin stays off by default.

Tracing Updates

Debug tracing gains Geth-compatible pieces, including a keccak256 preimage tracer and a txIndex option for debug_traceCall. Each request gets its own V8 runtime, so JavaScript traces run in parallel. Trace methods now follow the proposed trace spec and match Erigon and Reth, with several outputs changed.

Operational Improvements

A periodic log line reports how far the head is behind the chain tip. For most nodes the release serves as an in-place upgrade with no resync and no config change required.

Upgrade Path

Node operators can apply the changes directly from the release page on GitHub. The update separates the go-live date of Oct. 16, 2026 from any earlier labeled dates listed in the notes.

Plugin Defaults

The SendPolicy feature requires explicit activation. Without activation the node continues normal operation with no additional transaction checks applied.

Trace Compatibility

The added keccak256 preimage tracer and txIndex option bring debug_traceCall closer to Geth output. Parallel V8 runtimes allow multiple JavaScript traces to process at the same time without shared state.

Sync Reporting

The new periodic log line gives operators a clear view of chain tip distance. This line appears at regular intervals during normal operation.

In Place Upgrade

Most nodes complete the move without a full resync. Configuration files remain unchanged unless the operator chooses to enable the new plugin.

The release supplies these tools for node operators who want to define their own transaction rules while keeping the default behavior unchanged.