NeoFS Node gets administrative upgrades and bug fixes
Neo SPCC has rolled out NeoFS Node v0.51.1, which builds on the previous v0.51.0 release from earlier this month. This update brings several practical improvements for operators, focusing mainly on better administration tools and fixing some storage-layer issues that have been causing headaches.
I think what stands out here is the new CLI tooling. There’s a container policy check command that lets operators verify whether a container’s placement policy can actually be satisfied by the current network map. That’s useful because it gives a quick diagnostic for policy misconfiguration before things go wrong.
Mainchain management gets easier
The neofs-adm utility now has two mainchain management commands: mainchain update for upgrading contracts and mainchain version for checking deployed contract versions. This should streamline administrative workflows for node operators managing NeoFS infrastructure on the Neo mainchain. It’s one of those quality-of-life improvements that doesn’t sound exciting but actually makes daily operations smoother.
There’s also a new policer consistency state metric on storage nodes. This tracks whether the policer has completed a full cycle without performing any object relocations. When a clean cycle finishes, the metric sets to true. Any subsequent relocation resets it to false until another clean pass completes. It gives operators a straightforward way to monitor cluster consistency at the node level, which I think is more helpful than it might sound at first.
Performance and storage improvements
On the performance side, metabase resynchronization has been accelerated through batch operations. This reduces the time needed to rebuild the metabase when operators trigger a resync. It’s not a revolutionary change, but it’s the kind of incremental improvement that matters when you’re dealing with large datasets.
Storage nodes now retry notary requests when encountering insufficient gas errors. This addresses a scenario where container deletion could fail due to transient gas shortages during contract execution. That resolves an intermittent issue that had been preventing container removal on the network.
The bug fixes in this release are worth noting. Compressed files in the FSTree are now properly closed after use, preventing resource leaks. There was also a potential payload overflow when retrieving full objects from combined FSTree files that’s been corrected.
Configuration and billing fixes
The CLI’s default token timestamps have been adjusted to account for the network’s block time. This resolves 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 node configuration correctly trigger a netmap update rather than being silently ignored.
There’s also a billing fix 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 bumped to v0.117.0 as well.
For operators, NeoFS Node v0.51.1 is a straightforward update from v0.51.0 with no breaking configuration changes. Those running v0.51.0 can upgrade in place. Operators still on v0.50.x should follow the migration guidance published with the v0.51.0 release, which includes removing deprecated Inner Ring configuration options and completing any outstanding metabase migrations before upgrading.
The full changelog and release assets are available on GitHub for those who want to dig into the technical details.
