Development

Protocol

On Ethereum: We have fixed two minor bugs in v1.3 and had a new v1.4 deployed:

The TokenFactory (previously named TokenCreator) is a utility smart contract that helps people quickly create their new ERC20 tokens and make them inherently tradable using Loopring Protocol. We have posted an article to explain how to use it — “Ready to issue your own tokens? Here is how you can do it within 1 minute”.

We have also started another performance optimization bounty and will reward each percent of gas reduction with 10,000 LRC tokens (USD$6,000). We have received 6 pull requests and are currently reviewing and evaluating these proposed optimizations. If you are experienced solidity programmers, please help us review and improve our smart contracts.

On NEO: We have deployed LRN, Loopring’s protocol token on NEO, on NEO mainnet: (Asset ID: 0x06fa8be9b6609d963e8fc63977b9f8dc5f10895f ). We are currently working closely with engineers from several exchanges who want to support LRN trading pairs.

The LRN airdrop smart contract has also been developed and tested. The outstanding challenge is that we haven’t found an NEO wallet that non-technical people can use to withdraw their rightful tokens from the airdrop smart contract. This will be a critical problem for most LRC token holders who are supposed to receive the LRN airdrop. We are evaluating alternative solutions.

We have also prototyped a simplified version of our protocol on NEO. Over the coming months, we’ll improve the implementation to make it on par with the smart contract on Ethereum.

Relay

Optimization, optimization, and optimization. We truly want to make our relay stable and perform well and there are 4 engineers improving the relay implementation:

We are using Redis more aggressively to avoid hitting our Ethereum nodes.

We are also improving the relay to make it possible to start multiple relay instances in a single cluster.

We have switched to Beanstalk+SVC+SNS on AWS to report relay healthy status and enable auto-starts of relay instance in case of server failure.

We have also implemented a per-order proof-of-work mechanism to prevent malicious users from spamming the servers by submitting a lot of orders.

Wallets

Web-based Wallet (loopr): We’ve submitted 300+ commits with many improvements to Loopr’s UI. What we did learn from this v2.beta1 is the workflow of order submission. However, we are still very unsatisfied with Loopr’s overall UI and our in-house UI designer has just started working on a new UI layout. We will release our Web Wallet Development Roadmap to give the community a better idea what is coming up next.

Besides UI improvements, we have also optimized notification, re-built the landing page, improved wallet creation/unlocking popups, and address binding functionalities for LRN/LRQ airdrops.

We have started testing Loopr v2.beta1 internally. Our goal is to release it to selected token holders (with at least X amount of LRC) on April 20th.

iOS Wallet App (loopr-ios): We have made a lot of progress on iOS app’s UI and functionalities. We will start test it through TestFlight very soon.

Based on the latest UI design, we have updated UI of creating a wallet, sending tokens, converting ETH to WETH, the wallet view and more. We have added a drop-down animation to show whether converting ETH to WETH succeeds or fails. Users can export private keys and keystore files in the wallet management view now. We have optimized functions to import keystore files and to store created wallets in the local storage. For relay API integration, we have developed convenient functions for block numbers, gas cost estimation, and transaction history. We have also implemented features to get data from relay API WebSocket and to display them in the wallet view and the market view.

Operation and Marketing