Dear members, welcome to the sixth edition of our bi-weekly development update! Every other Monday we will be posting an overview of the progress we’ve made over the last two weeks. Here’s a quick summary of our major updates during this sprint.

Integration Libraries.

We’ve now implemented v0.1.0 integrations libraries for .NET and JS. This will allow applications which use that technology stack to easily integrate REMME business logic into projects. It provides the ability to interact with the REMME Node internal REST API. There are methods for:

Token — GetBalance, Transfer.

Certificates — CreateAndStore, SignAndStore, CheckStatus, Revoke.

Batch — GetStatus.

Note: Write operations to REMChain require transaction signing.

In 0.1.0 version of Libraries, transactions are signed by the REMME node the client interacts with, so the owner of the stored information will be the REMME Node admin. As a consequence, the current library is suitable only for local usage. In future releases the ability to sign transactions on the client side will be implemented. The client interface will not be changed, though the internal logic of the client interface will have a slightly different implementation.

REST-API:

Fixed CSRs: now CSR API endpoint processes validate dates in the same way as when uploading a ready certificate.

Web sockets allow developers to track changes in states in real-time which gives faster response in applications.

REMChain.

We’ve finished the REMchain side of the atomic swap protocol. This protocol enables users to transfer REM tokens between REMchain and the Ethereum blockchain so they can utilize tokens to manage certificates. UI and Ethereum side are on their way.

REMCore.

Storing an array of certificates per user allows certificates to be quickly found that were issued by a particular user and thus improves performance in applications.

Scientific research activities

Within the roadmap of the REMME Research Lab, we’ve been carrying out research on the existing families of the consensus algorithms in order to find the optimal algorithm for developing the REMСhain consensus for the public version of our blockchain. In the first stage we provided a brief review of the main classes of consensus algorithms. This research will be published soon.

As a result we narrowed the focus of our research to BFT (Byzantine Fault Tolerance) protocols, executed a technical overview, study their math models and compared the technical specifications. Finally, we identified three main algorithms: Honey Badger BFT, SBFT and Algorand’s protocol, which we have subjected to deep analysis and implementation to allow further all-around benchmark tests.

More updates:

- The REM token has moved from a time-limited trading region to Gate.io’s main trading region for long-term support. At the same time, a USDT market has been added. Read the official announcement here.

- REMME has been shortlisted for ‘ICO: Zero to Hero 2018’ nomination at The Block Awards 2018. Check all nominees here.

- One of our fabulous community members has created a great guide on how to test REMME WebAuth demo on Windows OS, check it out. Haven’t tried our demo yet? Try it here.

- With over 8,400 attendees and 200+ sponsors, this was the largest Consensus conference to date. And we’re proud to have been named a two-block sponsor of Consensus 2018. Check the video overview from our team members here. We also want to congrats the three winners of our special cometition for Consensus 2018 attendees.

- Finally, we’ll sign off with an update on what the media have been saying about REMME. Our passwordless authentication system is featured in depth in Entrepreneur, and we surface in another article in Finance Magnates, also about passwords and how REMME is developing a more secure alternative.

Catch you again in a fortnight for the latest tech developments from REMME HQ!

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