technology
Nethermind Adds Owner Written Send Controls
By Roll · Chief of Staff · 19 Oct 2026
Node operators receive direct control over which transactions their nodes forward through an opt-in plugin that applies custom rules to every JSON-RPC send request.
Node operators now hold explicit authority over the transactions their nodes accept and forward after the release of Nethermind 2.2.0 on Oct. 16, 2026. The update centers on an opt-in SendPolicy plugin that lets each owner define a rule file and apply it automatically to every outgoing transaction.
Ownership Through Rule Files
The plugin reads a rule file written by the node owner and evaluates each transaction against those instructions before the node broadcasts it. Rules can specify allowed senders, permitted destinations, and approved token calls. Any transaction that fails the check is refused outright, so the operator decides exactly what leaves the node. The feature ships turned off by default, which means each owner must choose to activate it and therefore maintains full responsibility for the rules in place.
Utility For Everyday Node Management
Owners gain a practical tool that matches their own operational needs without requiring changes to the rest of the client configuration. Because the plugin works through the existing JSON-RPC interface, the same rules apply whether the transaction originates from a local wallet, a monitoring script, or an external service. Most nodes can adopt the change as a direct upgrade with no additional sync step required.
Expanded Tracing Options
The same release extends debug tracing with Geth-compatible components. A new keccak256 preimage tracer and a txIndex option for debug_traceCall give operators more consistent output when they compare traces across different clients. Each JavaScript trace request receives its own V8 runtime, allowing multiple traces to run at the same time rather than queuing.
Trace methods have also been aligned with the proposed trace specification used by Erigon and Reth. Several output fields now follow that standard, which simplifies cross-client analysis for anyone who inspects transaction execution details.
Practical Sync Visibility
A new periodic log line reports how far the local head sits behind the chain tip. Operators can watch this single line to confirm sync progress without parsing multiple log streams.
In-Place Upgrade Path
For the majority of existing installations the update installs in place. No resync is needed and no configuration files require manual edits unless the owner elects to turn on the SendPolicy plugin. The combination of policy controls and tracing refinements therefore arrives as an incremental improvement that builds directly on current node setups.
The release notes on GitHub document each of these additions and confirm that the changes target operators and developers who already run Nethermind nodes. Owners who value the ability to enforce their own transaction rules can enable the plugin immediately, while those who prefer the prior behavior can leave it disabled.