On the official site of Jag (JagOBX / @JagOBX), this note covers Nethermind.
What does an Ethereum node operator actually receive when they choose to turn on the new controls in the latest client release?
Nethermind published Nethermind 2.2.0 on Oct. 16, 2026, an Ethereum execution client release that adds an opt-in SendPolicy plugin. NFA.
The core addition
The release notes describe the SendPolicy plugin as a tool that sits between the node's JSON-RPC endpoint and the transactions it would otherwise forward. An owner writes a rule file, and the plugin reviews every incoming request against those rules. Transactions that match the refusal conditions simply do not proceed.
The plugin stays off by default. Operators decide for themselves whether the extra layer fits their setup. Rules can address allowed senders, specific destinations, or particular token calls. The mechanism gives owners a direct way to shape what their node will handle without altering the broader client configuration.
Tracing updates included
Alongside the policy feature, the same release expands debug tracing options to include Geth-compatible pieces. A keccak256 preimage tracer appears, and a txIndex option becomes available for debug_traceCall. Each trace request receives its own V8 runtime, allowing JavaScript traces to run in parallel rather than waiting in sequence.
Trace methods now align with the proposed spec used by Erigon and Reth. Several output formats changed to match that standard. Operators who rely on trace data for monitoring or tooling will see these shifts after they upgrade.
Upgrade path details
The release notes note that most nodes can install the update in place. No resync is required, and existing configuration files remain valid. A new periodic log line reports how far the current head sits behind the chain tip, giving operators a simple status check without extra tooling.
What operators receive
The practical result is a choice. An operator who wants transaction-level rules now has a file-based method to enforce them at the JSON-RPC layer. Those who prefer the prior behavior can leave the plugin disabled. The tracing improvements arrive regardless, expanding compatibility with existing debug workflows.
The update stays focused on these operational points. No further claims appear in the release notes about broader network effects or required changes from other participants.