Neo SPCC shipped three coordinated NeoFS updates on May 21, covering the storage node, web management panel, and developer SDK. NeoFS Node v0.53.0 “Sido” leads the release with performance optimizations, ranged GET support, and several legacy API removals, while NeoFS Panel v0.9.0 introduces account-scoped file sharing and a simplified session token model. NeoFS SDK Go RC19 provides the library-level foundation for both, adding API 2.23 compatibility and deprecating multiple legacy methods.
The three releases form a dependency chain – Node v0.53.0 requires SDK RC19, which in turn requires NeoGo v0.119.0, covered by NNT earlier this month. The coordinated release follows a similar pattern from April, when Neo SPCC bundled Node v0.52.0 “Woodo” with SDK RC18.
NeoFS Node v0.53.0
The NeoFS Node release targets performance and maintenance across several areas of the storage node.
Database operations that modify state, previously batched only for PUT requests, are now batched across all regular operations. The metabase storage layer has been updated to store associated object IDs as raw bytes instead of Base58-encoded strings, triggering a schema migration to metabase version 11 on first startup. Operators running large shards should plan for downtime during this migration, as it may take considerable time to complete.
Search performance in erasure-coded containers has been improved by reducing the number of nodes contacted during SEARCH operations, and SearchV2 integer comparisons have been optimized. GET, HEAD, and RANGE request forwarding has also been streamlined.
The release adds ranged GET support, allowing clients to retrieve specific byte ranges of an object’s payload through the standard GET method. This consolidates object retrieval into a single API, with the legacy RANGE method marked for future removal. The change mirrors the ranged GET capability introduced in SDK RC19.
Node v0.53.0 also adds sd_notify support for both storage nodes and inner ring nodes, enabling operators to use Type=notify in their systemd unit files for more reliable service management.
On the removal side, several legacy APIs have been cleaned up. The GetRangeHash method has been removed from storage nodes, along with the corresponding neofs-cli object hash command. The deprecated Search method has been removed in favor of SearchV2, and homomorphic hash search has been stripped from both the CLI and node implementations. The policer.max_workers configuration option, already a no-op since v0.52.0, has also been removed.
Notable bug fixes include a correction to the policer, which previously allowed redundant local shard copies to remain on disk indefinitely. A session token storage epoch parsing panic has been resolved, compressed object GET failures have been fixed, and meta resync issues on case-insensitive filesystems have been addressed.
NeoFS Panel v0.9.0
The Panel release delivers the most user-facing changes in this batch, including multiple features that have been requested since early 2024.
Account-scoped file sharing allows users to share files with specific Neo account addresses rather than generating public links accessible to anyone. The feature gives container owners granular control over who can access shared objects, moving beyond the previous all-or-nothing sharing model.
Session management has been simplified through an all-in-one master session token that replaces the previous system of multiple separate tokens. Users now sign once per session instead of authenticating separately for different operations – a UX improvement that requires session token v2 support from neofs-rest-gw v0.16.0.
The release adds full support for creating and editing numeric comparison filters in extended access control lists, along with a new interface for managing verified node domains. Both features extend the Panel’s capability as a management tool for NeoFS infrastructure.
On the wallet side, NEP-21 compatibility has been added, with testing confirmed on NeoLine 5.8.5+ and OneGate 2.0+. O3 wallet support has been removed following the wallet’s discontinuation.
A bug that caused file uploads exceeding 700 MB to fail due to a missing Content-Type header has been fixed, along with an issue where the FilePath attribute was not being set automatically on uploads, rendering files invisible in the tree view.
Panel v0.9.0 is already deployed to the public instance.
NeoFS SDK Go RC19
The 19th release candidate continues the SDK’s path toward a stable v1.0.0 by adding API 2.23 compatibility and removing legacy methods.
Ranged GET requests, the library-level counterpart to Node v0.53.0’s ranged GET support, allow developers to retrieve specific byte ranges through the standard Get call. In parallel, both GetRange and GetRangeHash RPCs have been deprecated, with clients expected to compute hashes locally rather than relying on server-side computation.
The Tillich-Zémor homomorphic hash has been deprecated as NeoFS API 2.23 no longer supports it. Object payload readers now implement the io.WriterTo interface, reducing data copies during object downloads and lowering memory allocations for applications handling large payloads.
The full release notes for NeoFS Node v0.53.0, NeoFS Panel v0.9.0, and NeoFS SDK Go RC19 can be found at the links below:
https://github.com/nspcc-dev/neofs-node/releases/tag/v0.53.0
https://github.com/nspcc-dev/panel-fs-neo-org/releases/tag/v0.9.0
https://github.com/nspcc-dev/neofs-sdk-go/releases/tag/v1.0.0-rc.19
About The Author: Dean Jeffs
Dean is a digital project manager who has worked extensively with start ups and agencies in the marketing space. Fascinated by the potential applications of blockchain technology, Dean has a passion for realising the new smart economy.
More posts by Dean Jeffs