This article was first published on Loopring Protocol - Medium
Loopring Bi-Weekly Update — 12/22/2018
Our security audit for Loopring Protocol 2.0 has successfully completed, and we have deployed 2.0! We will publish a separate post reviewing all of 2.0 functionality shortly. Our mobile apps saw meaningful updates, including a contact list for addresses. These past 2 weeks also saw a few updates on how Loopring is working with cross-chain projects for interoperability.
The security audit for protocol 2.0 is complete. The report can be found here: (http://loopring.org/resources/loopring_protocol_v2_audit_report_EN.pdf).
Shortly afterwards, we deployed protocol 2.0 to main net (https://github.com/Loopring/protocol2/blob/23bbb4e567d0ae32bf370c86a061d7adf145782a/deployment.md)!
In the coming days, we will provide an overview of exactly what 2.0 enables — from a technical POV, as well as a feature and user-facing POV.
The bug and optimization bounty program we launched in late October ended. We approved one optimization proposal that gave a minor reduction in gas consumption.
We finished work updating our code base to Truffle 5.0 with solidity 0.5 and web3 1.0. The final release version of Truffle fixed all stability issues we had with the beta releases....
To keep reading, please go to the original article at:
Loopring Protocol - Medium