Neo SPCC has released NeoFS Node v0.50.0, introducing experimental erasure coding and a set of changes aimed at improving performance, configuration clarity, and compatibility.

Erasure coding

The update makes erasure coding available for NeoFS storage policies for the first time. Erasure coding is a data-protection method that breaks information into pieces and adds extra “repair” pieces, allowing the original data to be reconstructed even if some pieces are lost. In practice, it can offer the same reliability as full replication while using less storage.

The feature is disabled by default and must be enabled through the experimental.allow_ec option in the Inner Ring configuration. Operators upgrading from v0.49.1 can adopt the feature without further structural changes.

Streamlined configuration

A series of IR configuration options have been renamed to better match their function. New fields such as fschain.disable_autodeploy, mainnet.enabled, and mainnet.disable_governance_sync replace older parameters, several of which had inverted meanings. Neo SPCC noted that deprecated fields continue to work but will be removed in later releases.

Storage nodes also gain a new persistence layout, with session data moving to the node.persistent_state.path location. The previous path is now used only for migration.

Performance and stability fixes

The release addresses high CPU usage in the write cache, a garbage-collection loop caused by missing links in split objects, quota TTL issues, and a race condition in storage-node load reporting. It also fixes incomplete status handling in CLI commands and improves metadata indexing for certain nested root objects.

Nodes will now refuse to serve unpaid containers, aligning behavior with expected accounting rules.

Miscellaneous

Wallets using non-standard scrypt parameters are now supported after a compatibility fix. Legacy write-cache formats from before v0.46.0, however, are no longer supported.

Contract autoupdate no longer covers versions tied to NeoFS v0.43.0 or earlier. Operators upgrading from older deployments must first update through v0.49.1.

New neofs-adm commands provide load reporting and summary information for filesystem chain activity. Dependencies across NeoGo, the NeoFS SDK, and various Go libraries have also been updated.

The full release notes can be found at the following link:

https://github.com/nspcc-dev/neofs-node/releases/tag/v0.50.0

Tags: ,