- NEO-CLI 2.9.0 is a core update that uses the Akka framework
- The update increases security and makes it more convenient for user to run their own node
- Optimisation of the consensus synching time is one of NEO’s primary goals
Erik Zhang, NEO’s core developer and founder has recently released version 2.9.0. of the NEO-CLI. The NEO-CLI client is a full node. In other words, it will not only synchronise but also store a full copy of the NEO blockchain directly.
While it can be used as a basic wallet client, it is typically used to run RPC or consensus nodes that communicate with other nodes on the network.
NEO-CLI 2.9.0 comes with new capabilities in the form of plugins that increase the stability of NEO nodes and improve security for the network.
The update also includes automated and simplified processes which used to be manual such as opening of the wallet, getting application logs, and choosing models. Overall, it makes deploying nodes easier and more convenient – crucil for decentralization.
Between releases, clients are informed of all noteworthy alterations through the NEO-CLI changelog. The most recent version has the following changes, fixes, and additions.
- Improved plugins system
- Significant stability improvements (Actor Model)
- New RPC command: getwalletheight
- New RPC command: getblockerheader
- Allow the wallet index directory’s location to be modified
- NEO-CLI would closed on ^D without errors (for Linux only)
CNEO and CGAS
As the NEO ecosystem evolves and continues to grow, it has also become more diverse. This is reflected in their tokens. In line with this, NEO Global Development (NGD) launched CGAS and CNEO. The 2 tokens are decentralised and open source and were created for community members who don’t fully trust NEO’s relatively centralised methods of mapping global assets just yet.
Both CNEO and CGAS can be used with any project and has no usage restrictions as far as mapping global assets is concerned. Tethered to NEO and GAS respectively, both can be exchanged for their counterparts at market rates.
One of the next goals NEO developers are eyeing is optimisation of the consensus synching time. Vitor Coelho of NeoResearch has proposed the implementation of something similar to a Kalman Filter. It will allow a consensus node to act as speaker and use its experience of previous consensus rounds to better gauge a timeframe for the next round of consensus.
Another urgent change they are looking into is the reintroduction of a third consensus stage. The omission of the third “commit” stage of consensus has created a slim chance for the NEO network to encounter a single block fork.