Weekly Dev Update #5

Overview

BEPSwap Development

The team are working on 5 parallel streams of effort to deliver BEPSwap, which remains the primary focus.

1. Cosmos-powered SDK StateChain
2. Cross-chain infrastructure
3. Threshold Signature Scheme implementation
4. Front-end Integration for BEPSwap
5. Other development activities

The theme of the week was to upgrade the frontend for API integration, upgrade the Observer with BFT characteristics and optimise/benchmark the TSS signer in a networked environment.

StateChain

A testnet was successfully delivered with a continuous TX Spammer deployed to mock user transactions. The testnet is a single-node network.

• Refactors: rename poolstruct → pool, rename TxHash → TxIn, removing deadcode
• API: API documentation, Events API
• Statechain: Issue51 — make swap target price optional as well as destination address, Issue53 — Implement withdraw basis points
• Memo: remove memo from swap tx, Add/Gas memos
• BFT: majority rules with admin configs, BFT observations

Cross-chain Infra

• Issue16 — parse the tx field in tx search result to get the tx detail
• Add more unit tests to block scanner
• issue15: remove fasthttp, it is not a good library , has data race…
• config: update config to use viper, as in statechain cosmos, and tendermint ,…
• Statechain logging and fix observed panic.
• Issue14 — refactor binance chain
• Issue13 — work on signer also refractor some code so signer and observe can share some components

Threshold Signatures

• Optimised TSS signer on a remote network.
• Benchmark and test for continuous multi-send transactions — signing speed less than 1 second.

Front-end Integration

• Complete structuring of redux with saga for API integration
• Begin API work

Other Development

Work is ongoing with the BEP2Bot for BEP2 projects:

• News
• Wallet monitoring
• Address registration
• Price alerts.

Upcoming

This week has the following activities planned:

• Statechain: deploy a BFT environment, integrate TSS signer.
• Cross-chain infra: begin scoping out a block explorer.
• Frontend: Integrate API.
• Bep2Bot: prepare for community launch

Timelines

The team are working for these milestones. These timelines are indicative, but it is important for the team to deliver with high productivity and constant community feedback.

Other Development:

• RUNEVault: July 2019 shipped
• Telegram Bot: August 2019 shipped
• Bep2Bot: August 2019 on-time

BEPSwap:

The team have decided to factor in 4 weeks of September for auditing the code, thus mainnet will be pushed back to October.

• Testnet: August 2019 on-time
• Audit: September 2019 on-time
• Mainnet: October 2019 on-time

THORChain:

• Testnet: Q1 2020 on-time
• Mainnet: Q2-Q3 2020on-time

Community

To keep up to date, please monitor community channels, particularly Telegram and Twitter:

• Twitter: https://twitter.com/thorchain_org
• Telegram Community: https://t.me/thorchain_org
• Telegram Announcements: https://t.me/thorchain
• Reddit: https://reddit.com/r/thorchain
• Github: https://github.com/thorchain
• Medium: https://medium.com/thorchain