Neo SPCC ships NeoFS Node and SDK Go RC23 updates with ReplicateV2 and URI network maps
Crypto News reports Neo SPCC shipped a NeoFS Node and SDK Go RC23 update adding ReplicateV2, S3 credentials and URI-style network map endpoints.
Why it matters
The release changes how node addresses appear in network maps and tightens metabase migration requirements, so NeoFS node operators may need a two-step upgrade or a metabase resynchronization. Crypto News attached no trading or market figures to the release.
Key facts
Neo SPCC released a NeoFS Node update together with NeoFS SDK Go RC23 and Panel changes covering storage reshaping, ReplicateV2 and S3 credentials.
Reported by Crypto News (CryptoNews.net)
NeoFS SDK Go RC23 adopts NeoFS API 2.27 as the default protocol version, up from the API 2.26 default set in RC22.
Reported by Crypto News (CryptoNews.net)
The node release removes the GetRange object service method, completing a deprecation that began in Node v0.53.0, so applications must use parameterized Get for range operations.
Reported by Crypto News (CryptoNews.net)
Container revisions are now supported, aligning the node with the versioning semantics of SDK RC23 and the NeoFS API.
Reported by Crypto News (CryptoNews.net)
Storage nodes push URI-style endpoints into the network map instead of multiaddr, which remains accepted by the inner ring and storage nodes until removal in the next release.
Reported by Crypto News (CryptoNews.net)
The neofs-adm CLI adds a fschain netmap command for fetching current and historical network maps.
Reported by Crypto News (CryptoNews.net)
Reliability fixes cover EC object GET operations that broke when all data parts were missing and a buffer race condition in EC part range request handling.
Reported by Crypto News (CryptoNews.net)
The Metabase v10 migration path was removed, operators on versions earlier than v0.56.0 must upgrade to v0.56.0 or resynchronize metabases, and Metabase v12 migrates automatically on startup.
Reported by Crypto News (CryptoNews.net)
What happened
Crypto News reports that Neo SPCC shipped a NeoFS Node release alongside NeoFS SDK Go RC23 and Panel updates covering storage reshaping, ReplicateV2 and S3 credentials. The SDK makes NeoFS API 2.27 its default protocol version, up from 2.26 in RC22, and the node drops the GetRange object service method to finish a deprecation that began in Node v0.53.0, which leaves applications to use parameterized Get for range operations after RC22 already removed GetRangeHash. Storage nodes now push URI-style endpoints into the network map rather than multiaddr; Crypto News says multiaddr is still accepted by the inner ring and storage nodes but is due for removal in the next release, and that maps containing v0.56.0+ nodes may look different because of that conversion. Container revisions are now supported, the neofs-adm CLI gained a fschain netmap command for current and historical maps, and reliability fixes cover EC object GET operations where all data parts were missing plus a buffer race condition in EC part range handling. Operators on builds older than v0.56.0 must upgrade to v0.56.0 first or resynchronize their metabases, since the Metabase v10 migration was removed while v12 migrates automatically on startup, and no other outlet covered the release.
How the story developed
- First report
First report by Crypto News (CryptoNews.net)
Neo SPCC updates NeoFS Node, SDK, Panel with storage reshaping, ReplicateV2, S3 credentials
- Update
Crypto News reports Neo SPCC released NeoFS Node and SDK Go RC23 updates
The single reported account describes ReplicateV2, S3 credentials, URI-style network map endpoints, the GetRange removal, EC reliability fixes and the Metabase v12 migration requirement.
Affected entities
Original sources
| Publisher | Report | Role | Published |
|---|---|---|---|
| Crypto News (CryptoNews.net) Aggregator | Neo SPCC updates NeoFS Node, SDK, Panel with storage reshaping, ReplicateV2, S3 credentials | Original |