Share on Twitter
Share on Facebook
Share on Reddit
Share via Email
Share on LinkedIn
Share via RSS

Neo St. Petersburg Competence Centre (NeoSPCC) has released an updated version of neo-go, a node and SDK for the Neo blockchain created in Golang. The release adds a monitoring dashboard and new RPC functionality to neo-go nodes, allowing them to be leveraged for remote interaction with the Neo MainNet in new ways.

To help serve the Neo developer community, NeoSPCC has rolled out four of its own RPC nodes. A list of currently supported calls can be found here.

Go Client

Go is the fourth language to be used for a Neo node, joining the core C# client neo-cli, the Python client neo-python, and the JavaScript implementation offered by NEO-ONE. Having multiple node implementations—each developed by a different group—helps protect against network outages caused by a single point of failure.

The latest release, v0.62.0, may be downloaded here. Alongside a laundry list of improvements and bug fixes across the two latest releases, several new features have been implemented. These include changes made to bring neo-go in line with existing SDKs, but some unique functionality has also been added, such as the ability to compile native Go code into a smart contract.

Following the release of v0.62.0, NeoSPCC notes that all JSON-based tests for the Neo2 C# VM are running successfully against the neo-go VM. This helps ensure that contract creation, deployment, and invocation behaviour remains consistent across neo-go and neo-cli nodes.

Monitoring dashboard

Support for viewing important node and blockchain metrics was originally added in v0.61.0, using the open-source monitoring library Prometheus. The dashboard is intended to offer an accessible breakdown of pertinent data such as current node memory usage or the latest block height.

Future updates to the dashboard will add new metrics, such as mempool information. As for neo-go, NeoSPCC continues to add new RPC services and other improvements intended to bring it up to feature parity with neo-cli.

Another of these planned milestones is support for consensus participation, a feature that the team intends to achieve by the end of 2019. Once dBFT has been integrated and tested, NeoSPCC will switch its neo-cli TestNet consensus node over to neo-go.