technology
Nethermind Supplies Rule Plugin For Node Operators
By Scarlett · Chief of Staff · 19 Oct 2026
Node operators who run Nethermind receive an opt-in tool that lets them define which transactions their nodes accept. The feature arrives in the 2.2.0 release published on GitHub on October 16 2026.
Node operators who run Nethermind receive an opt-in tool that lets them define which transactions their nodes accept. The feature arrives in the 2.2.0 release published on GitHub on October 16 2026.
Transaction Control For Operators
The SendPolicy plugin forms the main addition for those who operate nodes. Each transaction sent through the JSON-RPC interface passes through a rule file written by the node owner. Rules can specify allowed senders, permitted destinations, and token calls that the node will process. Any transaction that fails a rule is refused before it leaves the node. The plugin stays off by default, so operators choose when to activate it.
Upgrade Path For Existing Nodes
Most operators can install the release as an in-place update. No resync is required and no configuration changes are needed for the base client. A periodic log line now shows how far the head block sits behind the chain tip, which helps operators monitor sync status during normal operation.
Tracing Updates Included
Debug tracing receives several Geth-compatible additions. A keccak256 preimage tracer is now available along with a txIndex option for debug_traceCall. Each trace request receives its own V8 runtime, which allows JavaScript traces to run in parallel. Trace methods follow the proposed trace specification used by Erigon and Reth, and several output formats have changed to match that standard.
Practical Steps For Node Owners
An operator who wants the new controls downloads the 2.2.0 binary from the release page. The SendPolicy plugin is then enabled through the configuration file or command-line flag. Once active, the rule file is placed in the expected location and the node enforces the listed conditions on every outgoing transaction. No other client components require adjustment for the plugin to function.
The release notes list all changes in one place. Operators who prefer the previous behavior can continue without the plugin because it remains optional. The tracing improvements apply automatically once the update is complete. This structure keeps the upgrade straightforward for the majority of node operators while giving those who need transaction rules a direct method to implement them.