Neo SPCC has released NeoGo v0.116.0, a critical update that activates the Faun hard fork on MainNet and TestNet, introduces P2P-level optimizations, and resolves a state synchronization bug introduced in the previous release. The update is fully compatible with C# node version 3.9.2.

Faun hard fork activation and Gorgon preview

The Faun hard fork, previously gated and inactive, is now enabled for public networks. On N3 MainNet, Faun will activate at block 8,800,000, while TestNet activation is scheduled for block 12,960,000. For NeoFS networks, the fork will activate at block 19,725,000 on MainNet and block 19,340,000 on TestNet.

Node operators must upgrade their nodes before the designated Faun activation height to avoid requiring full database resynchronization. The release notes emphasize the urgency of upgrading in advance to ensure seamless network participation after the fork.

In addition to enabling Faun, NeoGo v0.116.0 introduces preview support for the next hard fork, Gorgon, in an experimental capacity. Details on Gorgon’s features and activation timeline have not yet been disclosed.

New features and behavior changes

The Faun hard fork brings several new protocol-level features. A new recoverFund method has been added to the native Policy contract, allowing for the recovery of funds under specific conditions. The update also implements NEP-30 support for native contracts, enhancing compatibility with the broader Neo ecosystem.

Changes to the contract fee whitelist storage scheme improve data organization and efficiency. Additionally, NeoFS state object witnesses are now attached conditionally, optimizing synchronization workflows and reducing unnecessary computational overhead.

Critical bug fixes

NeoGo v0.116.0 addresses a critical state synchronization issue at block 2,940,927 of N3 MainNet. This bug, introduced by the Faun preview in v0.115.0, was caused by a missing fork switch in the Policy contract’s blockAccount handler. Nodes that did not resynchronize after upgrading to v0.115.0 may safely skip resynchronization for this release, as the fix corrects the state difference going forward.

Additional bug fixes include resolution of a panic condition triggered by premature channel closure in the RPC Waiter component, and correction of a premature Close() call in the NeoFS pool, which previously caused connection handling issues.

P2P and RPC improvements

The release optimizes P2P-level processing of P2PNotaryRequest payloads, building on the concurrency improvements introduced in v0.115.0. The node now exhibits increased tolerance for non-critical P2P errors, reducing unnecessary disconnections and improving network stability.

RPC functionality has been enhanced to accept native contract names directly in getstorage* and findstorage* handlers, simplifying query construction and reducing reliance on contract hash lookups.

Upgrade guidance

Node operators on N3 MainNet and TestNet should upgrade to v0.116.0 before the Faun activation heights to avoid service disruption. Operators who upgraded to v0.115.0 without resynchronizing may skip resynchronization for this release.

The full changelog and release assets can be found at the link below:
https://github.com/nspcc-dev/neo-go/releases/tag/v0.116.0

Tags: