[Update] Week #32: Latest Dev-Suite Updates

Latest Dev-Suite Updates


What we have focused on and working on lately was gathering all of the developer tools into one to form one powerful bundle, called the Development Suite or just Dev-Suite. Dev-suite aims to bring the ultimate experience for developers(having all of the tools and services in one place).
We believe that:
It should not be difficult to build a blockchain application (aepps) on aeternity

Our focus last weeks was on the upcoming token migration. The team together with some other aeternity blockchain engineers we involved in creating a solution for it. Fortunately, we all came up with one that will be easy to use for the community and of course secure. We also managed to make some improvements to the existing tools like Forgae and Playground.



We have investigated some issues with forgae working on windows. We have made some improvements there which will be available in the next release. We will also provide some updates in the documentation in which we will explain and support the Windows users.

Sophia Smart Contracts

The Date & Time library is finally merged with some fixes and updates. You can find it in the GitHub repository of the Sophia Examples.

Token Migration

Next weeks we will work on the token migration apps. Here is an overview of the solution that we will provide.

This solution will consist of several parts - migrator web-app, migration back-end app, and aeternity smart contracts.
The general idea is to allow the ethereum users to sign a message (their aeternity address and ethereum AE balance) with their private key and send it to an Aeternity smart contract. The Aeternity smart contract will recover the ethereum address of the signer and check whether this is a user that has a balance on the ethereum mainnet. If this is proven to be an ethereum AE holder, the smart contract will disburse the exact number of AE to the users AE address in the Aeternity network.

Obviously an aeternity smart contract cannot reach to the ethereum network. In order for the smart contract to check the balance, a list of all ethereum AE holder balances needs to be available. The sheer number of ethereum AE holders (20000+) makes the storing of such a list in the smart contract unfeasible.
To solve this problem we will introduce Merkle tree-based solution.

A backend app is going to create and maintain a Merkle tree of all ethereum AE holders and their balances. The merkle tree root hash will be stored in the Aeternity smart contract and through the use of hashing (and some additional data - index and intermediary hashes), the Aeternity smart contract will be able to check the validity of the migration claim by a given user. This back-end app will be open-source and can be run by everyone in multiple instances to ensure decentralization.

Change Log

  • Forgae version 3.0.0 released
  • Date&Time Library merged
  • Playground issues fixed

References and Relevant Links

Media Material


1 Like