Dear members, welcome to the eighth edition of our bi-weekly development update. As you may recall, last time we spoke it was to provide news of the progress we’ve made on REMChain. Our proprietary blockchain is now ready for private testing and we’ve also made progress with Atomic Swaps. This will enable cross-blockchain token migration so that clients can use the REM token, which operates on the Ethereum network, on our own REMChain.

Now, with the introductions out of the way, let’s bring you up to speed on what else our dev team have been up to lately.

We’re pleased to report that REMME Core Alpha 0.4.0 has now been released on GitHub.

Added:

REST API:

-The endpoint for sending raw transactions. It’s now possible to build and sign a transaction and then submit it to the validator with the REST API without running a node while keeping your private keys secure.

-CORS support for REST API.

WebSockets for real-time tracking changes on transactions statuses. Other features are on the way.

Arrays of public keys in Account objects were introduced to easily track all of the certificates issued by a particular user. The list of certificates is accessible with the REST API endpoint. Please note that those changes are subject to future performance optimizations. Those changes would not affect the REST API interface, but the internals may be subject to change.

Optional feature to disable economy mechanism in private networks (REMME sidechains).

Specifications for transaction families are now publicly available in the repository.

More configuration options for nodes (see .env to find a full list of them).

Changed:

Token transaction family was renamed to Account.

Moved from storing certificates to storing and managing public keys. This has several important consequences:

GDPR compliance is ensured as no personal data accessible in a certificate is stored on the blockchain.

A wide range of supported containers for public keys. An ability to uncouple from X509 container and store any data hash, so the core storage is more flexible and doesn’t limit clients in data format. Note: Data hash is required for validating data integrity, while authentication is processing.

No dependency on Sawtooth API within REMME REST API. Previously the project used Sawtooth REST API to communicate with the core. Now it communicates with the core directly via ZMQ sockets.

Migrated to Python 3.6

Internal refactoring has been done for cleaner project structure.

The transaction processor is now called remme.tp instead of remme.

Swagger UI was updated to a newer version.

Check the latest release here.

More news:

#Dev talks. Anatolii, our Lead Engineer, answered the most popular community questions about our technology during the first live AMA session for our Tech community in Discord. Our CEO Alex also took part in a recent AMA which has now been transcribed and published in two parts. Due to time constraints, not all of the questions that were submitted in the AMA could be answered at the time, but Alex has now responded to them, so as a bonus you can find these answers too in the transcript of the chat. Read Part 1 and Part 2. Alex’s pitch on Webit.Festival Europe. One of the recent events we attended was in Bulgaria, where Alex showed the power of REMME’s blockchain-based Access Management platform to Founders Games, the startup competition that formed part of the program at Webit.Festival Europe. Lot of interesting talks and meetings with potential client and partners were also conducted.

4. REMME at the Blockchain Expo Europe. We also had the privilege of attending Blockchain Expo Europe recently, which was held in Amsterdam. There, Alex participated in a Cybersecurity & ID Management panel discussion, giving his thoughts on ways to bolster network security for enterprises. We also had a REMME exhibition stand in place at the Expo, which was flocked through both days of the event with potential clients, partners, and curious passersby, who we had some fruitful conversations with.

5. Hyperledger Hackfest

Our R&D team participated in a three-day event held by Hyperledger project in Amsterdam. The primary goal for a Hackfest is to facilitate software development collaboration and knowledge sharing between participants, with an eye towards reflecting all ideas and conclusions back outward to the public open source community afterwards. During this event we presented the REMME authentication solution as a real-world use case of the Hyperledger Sawtooth framework and presented REMChain Testnet to the developer community. It was absolutely amazing event where we collected valuable feedback from tech specialists and core developers of the Hyperledger project.

👋 Cheers, we’ll get back to you soon for another REMME tech update and a full progress report on our next sprint. Catch you then or see you at one of the blockchain events we’ll be attending later this month.