2.2.0 brings node owners a new way to control what transactions their Ethereum nodes will process. Nethermind published Nethermind 2.2.0 on Oct. 16, 2026, an Ethereum execution client release that adds an opt-in SendPolicy plugin. NFA.
What operators receive
The release centers on an opt-in SendPolicy plugin. Node owners write a rule file that lists allowed senders, destinations and token calls. The plugin checks every transaction that arrives through the node's JSON-RPC interface. Transactions that break the rules are refused. The plugin stays off by default, so operators decide when to turn the controls on.
This setup gives owners direct say over the traffic their node forwards. They set the boundaries themselves rather than relying on defaults from the client. The result is a simple trust layer that matches the operator's own standards for which transactions should move through their hardware.
Additional tracing updates
Debug tracing received Geth-compatible additions. A keccak256 preimage tracer and a txIndex option for debug_traceCall now appear in the tools. Each request runs inside its own V8 runtime, which lets JavaScript traces run in parallel without shared state. Trace methods were updated to follow the proposed trace spec and now align with outputs from Erigon and Reth, though some fields changed in the process.
A new periodic log line reports how far the head sits behind the chain tip. Most operators can install the release in place. No resync is required and no config files need edits for the core functions to work.
Trust through owner control
The SendPolicy feature places rule writing in the hands of the person running the node. Owners can limit senders, block certain destinations or restrict specific token calls. Because the plugin is opt-in, the choice stays with the operator instead of being forced on everyone. This keeps the default behavior unchanged while offering an ethics tool for those who want it.
The changes stay inside the execution client itself. Operators who want the extra checks simply enable the plugin and maintain their rule file. The rest of the client continues to function as before. The design keeps the decision local and transparent.
Upgrade path
The release arrived on GitHub on Oct. 16, 2026. Release notes list the SendPolicy plugin, the tracing additions and the sync log line as the main items. For most nodes the move is straightforward. In-place installation covers the update without extra steps.
Owners who value transaction rules now have a built-in method to apply them. The plugin refuses anything that violates the file they write. That single point of control forms the core of what the release delivers to node operators.