You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: packages/loopring_v3/README.md
+11-6Lines changed: 11 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -1,6 +1,7 @@
1
1
# Loopring Protocol (V3) using zkSNARKs
2
2
3
3
## About
4
+
4
5
This is a very early version of Loopring's order-based DEX protocol (version 3.0). The code base is still being tested and is not production ready.
5
6
6
7
To understand several concepts introduced by the Loopring Protocol, such as order-ring, ring-matching, dual-authoring, free-burning, please read our [whitepaper](https://loopring.org/resources/en_whitepaper.pdf) for Loopring Protocol 2.x.
@@ -34,7 +35,6 @@ To understand the overall design for Loopring 3.0, including Ethereum smart cont
34
35
- Can switch to better hash function
35
36
- and more...
36
37
37
-
38
38
## Build
39
39
40
40
`npm run build // first time` or `npm run compile` or `npm run watch`.
@@ -48,12 +48,17 @@ make
48
48
```
49
49
50
50
## Run Unit Tests
51
-
* run `npm run ganache` from project's root directory in terminal.
52
-
* run `npm run test` from project's root directory in another terminal window.
53
-
* run single test: `npm run test -- transpiled/test/xxx.js`
54
-
* print info logs in tests: `npm run test -- -i`
55
-
* print more detailed debug logs in tests: `npm run test -- -x`
51
+
52
+
- run `npm run ganache` from project's root directory in terminal.
53
+
- run `npm run test` from project's root directory in another terminal window.
54
+
- run single test: `npm run test -- transpiled/test/xxx.js`
55
+
- print info logs in tests: `npm run test -- -i`
56
+
- print more detailed debug logs in tests: `npm run test -- -x`
56
57
57
58
Running all tests takes around 3 hours on a modern PC with a CPU with 4 cores. Creating proofs is computationaly heavy and takes time even when multi-threading is used. Run individual tests when you can.
58
59
59
60
Verifier/Prover keys are cached in the `keys` folder. When updating the circuits make sure to delete the keys of older circuit versions because this is not automatically detected.
61
+
62
+
## Contract Deployment
63
+
64
+
It's recommended to deploy the protocol with **UpgradeabilityProxy**. For more information, please see https://blog.openzeppelin.com/upgradeability-using-unstructured-storage and https://github.com/OpenZeppelin/openzeppelin-labs/tree/master/upgradeability_using_unstructured_storage.
0 commit comments