Neo SPCC has released NeoGo v0.107.1, featuring a new NeoFS-based solution for synchronizing blocks. The release remains compatible with Neo C# v3.7.5, the current version on the Neo MainNet, and does not require database resynchronization, offering a straightforward upgrade process for node operators.
NeoFS-based synchronization
The NeoFS BlockFetcher service is the primary addition to this release, which acts as an alternative to the peer-to-peer block synchronization mechanism. BlockFetcher enables nodes to download, verify, and synchronize block dumps stored in NeoFS.
The feature, supported by the new upload-bin command-line utility, can be activated through the configuration file. As part of this release, Neo SPCC will begin maintaining block dumps for both N3 and NeoFS public networks.
This enhancement was made as part of a proposal to store blocks and state snapshots on NeoFS. This could allow nodes to only store recent chain data, reducing the amount of data that needs to be stored locally while speeding up the process of joining the network for new nodes.
Other improvements
The update introduces several enhancements aimed at improving the functionality and development experience for NeoGo users. These include support for the NEP-24 standard at the compiler and bindings generator levels, updates to the RPC actor/invoker, neotest, and unwrap packages, and fixes for the NeoGo VM uncovered via differential fuzzing.
Additional changes include new tools for the command-line interface, notification parameter filters for the WebSocket notification system, and support for the upcoming Echidna hardfork, which is not yet enabled. Deprecated functionality has been removed; existing NeoGo users should check the list of behavior changes in the release notes to ensure compatibility.
Patch release
These updates were originally released in NeoGo v0.107.0. However, a patched release, v0.107.1, has been distributed to fix an issue with the NeoFS BlockFetcher shutdown procedure. The bug caused intensive CPU usage, restricting node functionality. Node runners are recommended to upgrade to the latest release as soon as possible to restore expected behavior. No configuration change or resynchronization is needed.
The original v0.107.0 changelog may be read at the following link:
https://github.com/nspcc-dev/neo-go/releases/tag/v0.107.0
