Neo SPCC releases NeoGo node for RC2
Neo SPCC has released an N3 RC2-compatible version of NeoGo. Alongside core changes, the v0.95.0 update also adds CLI support for NEP-11 non-fungible tokens and other small improvements for node operators, plus a number of bug fixes.
NeoGo has been adapted to all the core changes necessary for full RC2 compatibility. This means developers should be able to use the Go node as a drop-in replacement for operating private networks or joining the N3 RC2 TestNet as a node. A detailed configuration guide has been created, which shows how the node can be customized to serve different roles in the network.
Behavioural changes in this version mostly mirror those found in the core. Oracle requests will make use of the Neo-specific JSONPath implementation, and the native NNS contract has been replaced with a non-native version. As in the core, the features field has been reintroduced to contract manifests for any potential uses in the future.
Other improvements include more verbose RPC error reports for submitblock and sendrawtransaction calls, the ability to call the StdLib native contract’s ascii/integer conversion methods, itao and atoi, with only a single parameter, amongst other changes.
New CLI features
A CLI refactoring introduced a number of new features that are focused on user experience. Examples include support for the full set of NEP-11 token commands, the data parameter in NEP-17 transfers, and adding multiple signers to token transfers. CLI commands that use addresses now also accept hashes as well as addresses.
Several bugs were discovered and resolved in the new update, such as an incorrect field in NEP-6 wallets and proper rejection handling for transfer events with invalid numbers in the NEP-17 tracking code.
The team also detected errors in the state validation service, including potential data races, a memory leak, and issues with sending state root messages, each of which was corrected.
The full changelog can be read at the link below: