Neo SPCC releases NeoFS Node v0.51.1 with new CLI tooling, storage fixes, and operational improvements

Neo SPCC has published NeoFS Node v0.51.1, a follow-up to the v0.51.0 release that shipped earlier this month. The update focuses on new administration and diagnostic tooling, several storage-layer bug fixes, and performance improvements to metabase resynchronization.

NeoFS Node v0.51.1

The v0.51.1 release introduces new CLI commands and a storage node observability metric alongside a set of targeted bug fixes and dependency updates.

On the tooling side, a new container policy check command allows operators to verify whether a container’s placement policy can be satisfied by the current network map, providing a quick diagnostic for policy misconfiguration. The neofs-adm utility gains two mainchain management commands: mainchain update for upgrading contracts and mainchain version for querying the deployed contract version, streamlining administrative workflows for node operators managing NeoFS infrastructure on the Neo mainchain.

A new policer consistency state metric has been added to storage nodes. The metric tracks whether the policer has completed a full cycle without performing any object relocations, effectively signaling that all objects on the node conform to their placement policies. Once a clean cycle completes the metric is set to true; any subsequent relocation resets it to false until another clean pass finishes. This gives operators a straightforward way to monitor cluster consistency at the node level.

On the performance side, metabase resynchronization has been accelerated through the use of batch operations, reducing the time required to rebuild the metabase when operators trigger a resync.

Storage nodes now retry notary requests when an insufficient amount of gas error is encountered, addressing a scenario where container deletion could fail due to transient gas shortages during contract execution. This resolves an issue that had been intermittently preventing container removal on the network.

Bug fixes in this release address several storage-layer issues. Compressed files in the FSTree are now properly closed after use, preventing resource leaks. A potential payload overflow when retrieving full objects from combined FSTree files has been corrected. The CLI’s default token timestamps have been adjusted to account for the network’s block time, resolving frequent token validity errors on TestNet and MainNet where the previous defaults were too tight. Repeated garbage collection attempts to delete objects that no longer exist are now suppressed, and address changes in the node configuration now correctly trigger a netmap update rather than being silently ignored. Finally, a billing fix has been applied for networks that migrated contracts from version 0.25.0 to 0.26.0, with the neofs-contracts dependency updated to v0.26.1 to incorporate the correction.

The NeoGo dependency has been updated to v0.117.0.

Upgrade guidance

NeoFS Node v0.51.1 is a straightforward update from v0.51.0 with no breaking configuration changes. Operators running v0.51.0 can upgrade in place. Those still on v0.50.x should follow the migration guidance published with the v0.51.0 release, including removing deprecated Inner Ring configuration options and completing any outstanding metabase migrations before upgrading.

The full changelog and release assets can be found at the link below:
https://github.com/nspcc-dev/neofs-node/releases/tag/v0.51.1