Neo SPCC has released new updates for NeoFS and the S3 Gateway, introducing various improvements and fixes. The team also patched NeoGo to resolve a TestNet state inconsistency.
NeoFS Node
Version 0.46.0 of the NeoFS node brings a range of performance and reliability improvements. A key update is the expanded support for Neo N3 accounts, which can now act as witnesses for container-level operations such as creation, deletion, and eACL changes. N3 accounts can also now be used for ObjectService requests and session or bearer token signatures.
Peapod storage has been fully deprecated in favor of the newer fstree storage engine, improving efficiency and reducing complexity. The release also includes metrics enhancements via write caching, full adoption of SearchV2, and a broad set of fixes targeting the CLI, storage node behavior, and inner ring node stability.
Additional improvements include the elimination of deprecated configuration options and tools, and fixes for race conditions that previously impacted system reliability.
https://github.com/nspcc-dev/neofs-node/releases/tag/v0.46.0
S3 Gateway
The new S3 Gateway release includes initial work toward updating object attribute mappings and makes changes to how bucket ownership is managed. Ownership settings have been relocated from extended ACLs to versioned bucket-setting meta objects.
Additionally, request-related metrics have been restructured into histograms to improve observability.
Version 0.37.0 also fixes an issue affecting the ownership of multipart upload metadata objects and ensures homomorphic hashing is disabled for a new bucket when the functionality is disabled on the rest of the network.
As part of related tooling updates, the reset-bucket-acl command in the authmate utility has been revised to remove redundant extended ACL entries. Users upgrading from v0.36.1 are advised to consult the changelog for the updated peer configuration format.
https://github.com/nspcc-dev/neofs-s3-gw/releases/tag/v0.37.0
NeoGo
Neo SPCC has issued a critical patch for NeoGo, releasing version 0.109.1 to resolve a consensus-breaking state difference observed at block height 5,894,663 on TestNet.
The issue stemmed from a discrepancy in how NeoGo and the reference C# node handled the GAS generation rule update following a council modification—specifically, whether the update should apply immediately within the same block or in the next one. The patch aligns NeoGo behavior with the expected protocol specification.
In addition, the update fixes an issue where a NeoToken.CommitteeChanged event was being emitted regardless of whether the Cockatrice hard fork was active. It also ensures that WebSocket subscription and unsubscription requests are handled sequentially to prevent race conditions.
TestNet node operators must resynchronize after applying the patch. As an alternative to a full resync, operators can run neo-go db reset to roll the node’s state back to height 5,894,662. MainNet nodes are unaffected.
