Cryptrade’s Weekly Development Report — January 26, 2019

Cryptrade Exchange
2 min readJan 26, 2019

--

January 20, 2019 — January 26, 2019

Launch a registration bounty.

Through our hard work during this period, we have partially completed the development of the back-end system(The API service of Cryptrade DEX) and deployed the API service to the production environment too.

The whole API service is a huge system composed of many modules, like withdrawal, deposit, market, account, and interaction with bitshares. Now the deposit and withdraw are closed due to test, and other modules are ready already. So we launch a registration bounty for those who register a new bitshares account via out faucet.

More information about the registration bounty can be find here: https://medium.com/@cryptrade_io/cryptrade-account-registration-reward-8966da539d3

Release the API service.

As we mentioned above, we have partially completed the development of the back-end system(The API service of Cryptrade DEX) and deployed the API service to the production environment too.

Deploy a BTS node to production environment.

Completed, we deployed a trusted node and also a delayed node to the production environment. Our API services will interact with the bitshares network through these two nodes.

Test the Withdrawal and Deposits of the DEX.

Ongoing. And withdrawal and deposit will be opened in the near future.

Release and deploy the Frontend

Through our hard work during this period, we are very pleased to announce that we released the first stable version (cryptrade-ui v1.0.190125)of the frontend of Cryptrade DEX two days ago.

Release on Github: https://github.com/cryptrade-project/cryptrade-ui/releases/tag/v1.0.190125

At the same time, we have deployed the frontend to the production environment in the domain: https://dex.cryptrade.io

Fix issues with the Vote Bot

Vote bot was temporarily unavailable for several hours, and the issues have been fixed already.

Next Week

  1. Test the Withdrawal and Deposits of the DEX.
  2. Publish a clear schedule of the release of our DEX.
  3. Release an MVP of the DEX

--

--