neo-sharp

In June, the neosharp team, consisting of 8 members, continued to build out the platform particularly around cryptography, network messaging, and persistence.

A major milestone was met as the team achieved generation of the Genesis block and began testing the persistence of blocks from both testnet and mainnet sources. There were also continued efforts around network messaging, unit test coverage, and updates to contribution guidelines and best practices to enable new contributors to participate in the project and get the codebase ready for the sprint in Shanghai to work alongside NGD resources.

In July, the rubber really started to hit the road with neosharp and the Shanghai sprint. The team gained 5 new contributors and had almost 100 pull request / commits in the month of July.

Major areas of focus in this month were integration of wallet features, application and console features, addition of the task scheduler framework, RPC implementation, VM integration, block processing / persistence, and unit test coverage. The framework was also upgraded to dotnet core 2.1 and the Shanghai sprint was a success as the beginning of NGD resource integration into the neosharp development efforts, with expectations of deeper integration and resource allocation to the project in the coming months.

In August, the contributor base grew further to a total of 13 regular contributors / participants in the design, testing and implementation of neo-sharp. The project management was moved to use Github issue tracking and project management, sunsetting the legacy Trello board used by early contributors.

There was also an increased focus on test coverage, with a new initiative started to leverage containers to facilitate functional testing of nodes in a network configuration. The use of dynamically allocated containers will enable developers to the ability to test nodes in a way that has yet to exist in the NEO community to date.

In addition to testing, persistence was further implemented, bringing the Redis DB persistence module functionally up to part with the RocksDB implementation, and the first JSON persistence module was implemented using Redis to allow for more convenient third party interop and debugging for developers.