Neo SPCC has published a coordinated release of NeoFS releases, starting with NeoFS Node v0.51.0. This enables protocol-level changes such as introducing mutable NEP-11 containers, synchronous container operations, and session token v2. The included NeoFS SDK Go v1.0.0-rc.17 provides the underlying library support for these features, and XK6-NeoFS v0.2.1 brings stability fixes and dependency upgrades to the load testing extension. The TestNet upgrade is complete and MainNet will follow in the coming days.
NeoFS Node v0.51.0
The NeoFS Node v0.51.0 release includes a number of important protocol changes. Containers are now represented as mutable NEP-11 tokens on-chain, and both storage nodes and inner ring nodes support new container contract methods, including: createV2 and getInfoand attribute management methods setAttribute and removeAttributeprovides a richer on-chain container management API. The corresponding CLI commands for setting and removing attributes are container section.
Container operation Put, Deleteand SetExtendedACL is now processed synchronously by the storage node, replacing the previous asynchronous flow. This change simplifies client-side logic by eliminating the need for polling and waiting for eventual consistency. You can also lock a container so that it cannot be deleted. __NEOFS__LOCK_UNTIL Attribute, storage node returns new attribute CONTAINER_LOCKED Status when attempting to delete a locked container.
Session token v2 is introduced throughout the stack. Both inner ring nodes and storage nodes now accept new token formats for container and object operations, and new CLI commands are available to generate v2 tokens. Lock and tombstone objects using API versions older than 2.18 are no longer accepted.
In terms of performance, metabase optimizations speed up object deletion by reworking the locking information scheme and removing the traditional graveyard structure. Object service improvements specifically target erasure-coded containers. EC parts are co-located, shard ordering is consistent between reads and writes, and raw data requests are supported in the EC container. Continuation of RANGE requests in multi-rule EC scenarios was also fixed. acquisition of $LINK Objects in EC containers are now supported, and sized objects are $LINK Object is unavailable. Object to shard placement has been optimized so that objects requested for deletion via the control service are immediately deleted instead of being queued for garbage collection.
Several deprecated internal ring configuration options have been removed. fschain_autodeploy, without_mainnet, governance.disable, fee.main_chainand contracts. Node operators upgrading from v0.50.2 must remove these options from the IR configuration file, as their presence prevents the node from starting. Automatic metabase migration from versions 3 and 4 has also been removed. Operators still using these versions should resync or migrate using NeoFS Node v0.50.2 before upgrading.
Bug fixes address inner ring panic during graceful shutdown, incorrect IR node list storage via netmap contract instead of RoleManagement, deadlock on storage node termination in rare garbage collection scenarios, and expired EC parts incorrectly persisted on storage nodes.
NeoFS SDK Go v1.0.0-rc.17
The SDK release provides a library-level foundation for protocol changes in Node v0.51.0 and is compatible with NeoFS API 2.21. Session token v2 support is fully implemented, allowing clients to create and use new token formats for both container and object operations.
The new container attribute management API introduces methods for setting and removing container attributes, along with a set of new well-known attribute names. The container API itself is synchronized as node behavior changes. Connection pools now use a sliding window for error counts, improving load balancing decisions under intermittent failure conditions.
The object creation API has been refactored to: object.New It is more specialized in creating new objects, and is more specialized in creating new objects than previous InitCreation Method has been removed. A three-way comparison method has been added to the OID, CID, and Address types, providing more expressive sorting and ordering operations.
This release also fixes incorrect status handling for incomplete responses and updates NeoGo dependencies to v0.116.0.
XK6-NeoFS v0.2.1
The NeoFS load testing extension for k6 receives a maintenance release that addresses stability and fairness. A panic that occurred during S3 testing has been resolved and a false checksum warning that appears during test runs has been eliminated.
Load distribution between target nodes is now fairer, reducing the impact of hotspots during benchmark execution. Build requirements have been increased to Go 1.24, and dependencies have been updated across the board, including the NeoFS SDK Go to v1.0.0-rc.17, the AWS SDK to v1.39.0, and the k6 framework itself from v0.51.0 to v1.3.0.
Upgrade guidance
Node operators should follow the TestNet upgrade and prepare for the expected MainNet deployment soon. Inner Ring operators should audit their configuration files and remove the deprecated options listed above before upgrading to v0.51.0. Storage node operators still running metabase version 3 or 4 must complete their migration via v0.50.2 before this upgrade because the automatic migration path has been removed.
The complete changelog and release assets are available at the link below.
https://github.com/nspcc-dev/neofs-node/releases/tag/v0.51.0
https://github.com/nspcc-dev/neofs-sdk-go/releases/tag/v1.0.0-rc.17
https://github.com/nspcc-dev/xk6-neofs/releases/tag/v0.2.1
