This week, three goals were planned. The first one was to understand all consensus and PII steps and check them in the code. The second one was to improve monitoring UX. The last one was to create a procedure to add an host and a bot to an existing network.

In the web interface, a new tab “NeuroChain” has been added. It contains three sub-sections : “introduction”, “consensus” and “Proof of Involvement and Integrity (PII)”. “Introduction” helps to understand where NeuroChain differs from other blockchains. “Consensus” is a description of the assembly and election system invented by NeuroChain. It enable a bot to forge one block from different criteria, in particular with the Proof of Involvement and Integrity (PII) measure. “Proof of Involvement and Integrity (PII)” details mathematical steps to measure how reliable and active a bot is. Formula justifications can also be found in this web page. Each elements are located in the code so the development team can improve crucial key points like random seeding.

Monitoring visual has been updated. If a minimal of two following blocks have the same author, the latter is displayed in red so it catches the administrator eye. The same logic has been applied on the branch name, if it’s not the main one, the user is visually alerted. For previous block has, if the latter is correct then the hash is displayed in green. On the contrary, red is still the colour to show errors.

Before completing the procedure to add an host and a bot to an existing network, shell scripts have been created to make installation and automation easier. In summary, development team have developed tools to help themself administer network hosts and bots so the procedure will become as simple as clicking on a button. Tools democratization is still in progress and will be the priority for next week.

About git policy, a cleanup strategy is in discussion, so be prepared for modification the following month.

Comments are closed.