File tree 1 file changed +14
-4
lines changed
1 file changed +14
-4
lines changed Original file line number Diff line number Diff line change @@ -3,9 +3,9 @@ Gravity Node Data Extractor
3
3
4
4
[ ![ Build Status] ( https://drone.gravityhub.org/api/badges/Gravity-Tech/gravity-node-data-extractor/status.svg )] ( https://drone.gravityhub.org/Gravity-Tech/gravity-node-data-extractor )
5
5
6
- ## Common prerequisite
6
+ ## Abstract
7
7
8
- You need to have valid Binance API key data reading. (--api param)
8
+ This package represents working example of Gravity Data Extractor.
9
9
10
10
## I. Running public Docker image
11
11
@@ -15,14 +15,24 @@ You need to have valid Binance API key data reading. (--api param)
15
15
docker pull gravityhuborg/gravity-data-extractor:master
16
16
```
17
17
18
- ### 2. Run it
18
+ ### 2. Run
19
19
20
- For example, on port 8090
20
+ You can run SuSy dApp extractor
21
21
22
22
```
23
23
docker run -itd -p 8090:8090 gravityhuborg/gravity-data-extractor:master
24
24
```
25
25
26
+ ### 2.1 Run SuSy dApp extractor for EVM-based or WAVES-based chains
27
+
28
+ Currently, extractor supports only ` EVM-chain<->WAVES ` direction.
29
+ So we in order to add new custom(non-EVM) chain we need to provide 4 additional params
30
+ and 2 bridge implementations as well - for direct and reversal swaps.
31
+
32
+ So, for EVM-based tokens we run ` --waves-based-to-eth-direct ` and ` --waves-based-to-eth-reverse ` .
33
+ For WAVES-based tokens we run ` --eth-based-to-waves-direct ` and ` --eth-based-to-waves-reverse `
34
+
35
+
26
36
## II. Running the binary
27
37
28
38
### 1. Install Go
You can’t perform that action at this time.
0 commit comments