Neo SPCC resolves TestNet state differences in NeoGo v0.114.0 update

Neo SPCC has released NeoGo v0.114.0, an update that resolves a TestNet state difference at block 11,074,661 and introduces a broad set of compatibility, performance, and feature improvements.

State compatibility fix

The update corrects a state mismatch caused by improper handling of native NEP-17 token transfers, which could cause nodes to diverge during execution. It also resolves a deadlock that occurred when expired iterator sessions could not be terminated.

NeoGo v0.114.0 remains fully compatible with the C# node implementation from version 3.8 onward.

Neo SPCC noted that TestNet nodes may resynchronize or reset state to block 11,074,660, but this step is optional. State alignment resumes naturally from block 11,091,272, leaving only two application logs from two transactions at lower heights that are unlikely to affect most users.

Improvements and fixes

The release expands the Faun preview by adding local analogues of the System.Storage.* interop API, intended to support future enhancements to on-chain storage. The NeoFS block storage uploader now uses a single-threaded search model to simplify behavior and improve reliability, accompanied by refinements across related NeoFS components.

The NeoFS SDK for Go has been updated to RC15, and the release includes documentation updates, dependency upgrades, a new example of NeoFS usage within smart contracts, and improvements to the NeoFS audit tooling. Compiler updates add support for assignment operators such as &=, |=, >>=, and <<=.

Bug fixes target issues such as incorrect RPC bindings for NEP-22 and NEP-31, a compiler panic caused by missing external packages in imported modules, execution errors when iterating over nil slices, improper handling of negative NEP-17 transfers, and failures when terminating expired iterator sessions.

Removal of deprecated functionality

In accordance with the deprecation schedule, the release removes the math.Max and math.Min interop functions and eliminates the SessionExpirationTime RPC server configuration. Smart contracts or node setups relying on this functionality may require updates.

The default Prometheus and pprof ports in the MainNet configuration have also been changed, a modification that may affect operators using these monitoring services.

The full changelog can be found at the link below: