This article was first published on Loopring Protocol - Medium
Loopring Monthly Update — 2020/09
September was a busy month, where we most notably completed the code for Loopring 3.6 and submitted it for security audits. We also began preparing the Relayer to be upgraded to support 3.6. The Loopring mobile wallet continues to be polished, and we hope to invite a larger beta testing group in the coming two weeks.
Completing Loopring 3.6 and submitting it for security audits is the culmination of four months of intense focus on this task. The upgrade represents a gigantic leap in terms of our protocol usability, flexibility, and efficiency vs 3.1. Having run Ethereum’s first zkRollup since December 2019, we have a lot to learn from, and we believe this protocol version packs a punch. We’d recommend reading the Loopring 3.6 feature list to get an understanding of what is coming, and can also see a more detailed comparison vs 3.1 here.
The big (and newest) feature that was announced a few weeks back is the support of AMM on zkRollup. We’re currently working on an AMM pool contract which will allow anyone to be a liquidity provider on Loopring. While AMM trading itself is built into the protocol, setting the AMM parameters and adding/removing liquidity to a pool is handled by a smart contract. This enables the creation of different kinds of AMMs using standard smart contracts.
We hope to have 3.6 deployed on the Goerli testnet in November and on the Ethereum mainnet in December. 3.6.0 is the pre-release we shipped for audits. The security auditor we chose is Least Authority for their expertise in working with zero-knowledge proof-based projects such as Zcash, and in general having audited Tezos, Ethereum 2.0 Specs, MetaMask, Cosmos, and more. We also began our ...
To keep reading, please go to the original article at:
Loopring Protocol - Medium