technology
Nethermind Introduces SendPolicy Plugin In New Release
By Roll · Chief of Staff · 19 Oct 2026
Node operators monitoring Ethereum client activity see a new set of options appear in the latest Nethermind release. The update centers on an optional plugin that applies custom rules to outgoing transactions.
Node operators checking GitHub on October 16, 2026, found Nethermind 2.2.0 listed as a standard in-place upgrade for Ethereum execution clients. The release page shows the package ready for download with no requirement for a full chain resync or any changes to existing configuration files.
Release Details
The client arrived on the repository that day as an Ethereum execution layer build. Most operators can install it directly over the prior version. The notes list several operational additions that address transaction handling and tracing output.
SendPolicy Plugin
An opt-in plugin called SendPolicy sits at the center of the transaction changes. Once enabled, it reviews every transaction submitted through the node’s JSON-RPC endpoint against a rule file supplied by the operator. The plugin blocks any transaction that violates those rules. Operators can write rules that limit allowed senders, restrict destination addresses, or control which token contracts can be called.
The plugin remains off by default, so nodes continue with their previous behavior until an owner chooses to activate the feature and populate the rule file.
Tracing Improvements
Debug tracing received updates that align portions of its output with Geth. The release adds a keccak256 preimage tracer along with a txIndex option for the debug_traceCall method. Each trace request now receives its own V8 runtime, allowing JavaScript-based traces to execute in parallel rather than sequentially.
Trace methods were also adjusted to follow a proposed trace specification. The changes bring output closer to what Erigon and Reth produce, and several fields in the returned data were modified accordingly.
Operational Logging
A new periodic log line reports the distance between the current head block and the chain tip. Operators can use this line to monitor sync status without additional tooling.
Upgrade Path
For the majority of nodes the process stays straightforward. No resync is required and no configuration edits are needed beyond the optional decision to turn on the SendPolicy plugin. The release notes frame these items as targeted additions for operators who manage transaction flow at the node level.
The changes focus on giving node owners more direct control over what their nodes forward while keeping the default behavior unchanged.