Dear members, welcome to the first of our bi-weekly development updates! Every other Monday we will be posting an overview of the progress we’ve made over the last two weeks.

The next version of the REMME Public Key Infrastructure (d) protocol is live! We’re inviting everyone to track changes, test and contribute on GitHub.

Added

Entered parameters for certificate from CLI.

Continuous integrations setup.

Pushed release images to Docker Hub.

A separate setup for end users.

Started test coverage.

Added convenient way to generate a new genesis block.

A fixed amount of tokens is now burnt on a certificate issuance. This is to create a point of token utilization. In the next release, tokens that are burnt will now be transferred to masternodes (this is bound to the custom consensus implementation).

Changed

Transactions: unified data structures and transaction processors.

Faster startup in Docker containers for end users and separate Docker container for development purposes (instant source code updates).

Security

Reviewed and fixed security issues on token operations.

We’ve also started research on custom REMME consensus inspired by RBFT: Redundant Byzantine Fault Tolerance and are making final changes for the first stage of REMME Testnet (REMchain) development based on Kubernetes Engine.

More updates:

👋 Cheers, we’ll get back to you with more!