After some time off for the Lunar New Year holiday, the Loopring team returned in full force in mid-February. Now we are back in action and ready to rock. A talented and experienced UI/UX designer has joined us last week. Our global community hosted a few meetups in Australia and North America. We’ve made great Protocol and Relay progress, had a few deep dive interviews, and Polymath successfully trialed peer-to-peer trading of security tokens over the Loopring protocol.
The Protocol team has been working with the Relay team on integration testing in the past two weeks. We have completed testing for order parameters processing, encoding and decoding, signing transactions, order matching and event logs.
Having previously implemented support for the ST20 token standard, Polymath’s implementation of the ERC1400 security token standard, we have now successfully completed test trades. Whitelisted addresses were able to settle trades over the Loopring protocol, while non-whitelisted addresses failed. Coindesk writeup here.
Lightcone (Relay 2.0)
We have completed most of the functionalities for Relay 2.0, so we have started reviewing those functionalities and workflows to ensure the quality and the stability of the system.
Completed optimizations for wallet account management and updating order status.
Implemented processing of Ethereum fork.
Implemented web socket API, including monitoring pending trade.
Completed logging, deployment and system monitoring.
We have also written basic code for integration testing, preparing for more testings in the future.
Finally, we are working on refactoring event logs, wallet account activities and others.
Frontend & Product
iOS & Android
We have released version 1.6.2 and 1.6.3 of both iOS and Android apps. In Android development, we have fixed several bugs and re-launched app on Baidu App Store. In iOS development, we have updated the app enterprise certificates, allowing users to continue using enterprise iOS app. In addition, we have updated the trade order form to be closer to the UI of centralized exchanges. It makes it easier for new users to learn how to use our apps. At the same time, we have started researching wallet backup methods on third-party cloud platforms. We have investigated Google Drive, iCloud, Dropbox and other cloud platforms. We believe this feature will simplify workflows and we will continue the development.
We are happy to welcome a new designer to the team, Dennis Ge. Through our discussion, it’s clear he is super familiar with the main value proposition of our apps and many others in the space. We have been focusing on the core value of wallets, but also on the visual aesthetics and additional, interactive features. We have started designing an exciting new UI. In the next steps, we will present an initial plan, work with the team to make the new design goal and improve the products gradually. He will definitely make significant contribution and impact to our products.
Operations & Marketing
02/06/2019 — LRC is listed on Freewallet.
02/14/2019 — Ethfinex listed LRC on their platform and organized the Loopring AMA on the Ethfinex Telegram.
02/15/2019 — Dolomite Bi-Weekly Update
02/22/2019 — The Loopring Long Term Incentive Program begins the allowed withdrawal phase.
02/27/2019 — Loopring continues work with Polymath to further peer-to-peer trading of security tokens on a decentralized exchange.
Coming up this month, you can find Loopring around Hong Kong Blockchain Week, EthCC, ETHParis, and ETHUofT (University of Toronto). Reach out if you’re around! We will sponsor ETHUofT hackathon on March 8–10. Stay tuned for our imminent project request and prize!
Kriptomat will host a live video AMA with Loopring’s Matthew Finestone on March 7th.
To stay up-to-date with Loopring, please sign up for Loopring’s Bi-Weekly Update, and find us here:
⭑ Twitter: twitter.com/loopringorg
⭑ Reddit: reddit.com/r/loopringorg
⭑ Telegram: t.me/loopring_en & t.me/loopringfans (Chinese)
⭑ Discord: discord.gg/KkYccYp
⭑ StackOverflow: stackoverflow.com/c/loopring
⭑ Kakao: open.kakao.com/o/gJbSZdF (Korean)