Over the last two weeks we have seen some great progress towards the release of test-net1. We’re excited to be moving closer and closer to the point where it will be ready for release to the community and the public at large. Below are consensus and node progress since the last update. A lot of the code mentioned in previous updates has now been merged to master for further testing.

Consensus Updates:

Refactoring namespaces and file changes;

Coin validation before adding to memory pool;

Refactoring Blockmania and adding view change test;

test; Added Blockmania backing classes;

Updating backing classes and repository pattern;

Added Blockmania service and controller;

Adding interpreted callback and block graph repository pattern;

Increasing database container size;

Refactor block and coin controller;

Modified blockID class as immutable.

Other areas to consider:

Simplification to Tangram’s CLI wallet (Cypher) from the initial implementation with HashiCorp Vault Enterprise is ongoing. The reason for this is that we’ve noticed certain edge cases where the 4 keys generated may OR may not unseal the user’s wallet, among other uncomfortable scenarios; however, the first was sufficient to make the decision to opt for a different solution.

So, Cypher no longer starts Vault with Tor, instead using LiteDB for the installation. You will also notice that 4 keys are no longer required to be generated and saved when setting up your Cypher wallet. For those familiar with Cypher and creating multiple wallets, this means that for every wallet created, you will find a wallet db file in wallets > id_

This change can be found under nosql_embedded branch and will be merged to master shortly. Users will then be able to test the new process and familiarise themselves with the changes:

At a later stage (post-genesis) we may consider looking further into HashiCorp Vault Enterprise integration and the Vault Enterprise feature set.