This article was first published on Loopring Protocol - Medium
-----
On October 9th, our team successfully submitted zkRollup AMM join, swap, and exit transactions on Ethereum’s Goerli network.
A few example transactions:
- https://goerli.etherscan.io/tx/0x76ea064ba3e4c85940748da165baabdad9af7a81c54e76eeb33073d113a5c5bf: a pool join transaction (add liquidity).
- https://goerli.etherscan.io/tx/0x3a589a0cdd0ca43b27ea13f28acb1cb9b11f11f7d783c35e309e106dacc52f8d: a swap transaction.
- https://goerli.etherscan.io/tx/0x61c3c89f309b3610fc857fe25e32eac9c3941def5a07e3e8210ea324b0db7862: a pool exit transaction (remove liquidity).
About Loopring’s AMM Design
An AMM swap circuit is now part of Loopring 3.6. The circuit implemented the Balancer curve:
Where
- t ranges over the tokens in the pool;
- Bt is the balance of the token in the pool;
- Wt is the weight of the token, upgradable by the AMM pool’s managing contract.
Various AMM pools can be implemented differently in their own smart contracts; all pool join and exit transactions are on layer-2 using Loopring’s Transfer transactions. The pool’s smart contract verifies join/exit transactions data onchain and manages pool token issuance; Loopring only facilitates swap transaction settlement. Therefore, AMM pool contracts are not considered as part of the Loopring protocol.
Loopring 3.6 will match regular orderbook orders with AMM pools natively without the need for extra funds to do arbitrage. Orders can be filled partially with other orders and partially with AMM pools....
-----
To keep reading, please go to the original article at:
Loopring Protocol - Medium
Comments (No)