forked from across-protocol/relayer
-
Notifications
You must be signed in to change notification settings - Fork 1
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Move relayer inventory config to external json file (#45)
### What was the problem? This PR resolves LISK-885. ### How was it solved? - [x] Instead of using `RELAYER_INVENTORY_CONFIG` variable which has `json` string, `RELAYER_EXTERNAL_INVENTORY_CONFIG` is used containing file path to `json` file with a relayer inventory config. ### How was it tested? Run `yarn relay --wallet void --address <ADDRESS>`, after setting `RELAYER_EXTERNAL_INVENTORY_CONFIG` variable in `.env` file.
- Loading branch information
1 parent
8c76058
commit e5e56a0
Showing
2 changed files
with
42 additions
and
1 deletion.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,41 @@ | ||
{ | ||
"wrapEtherTarget": 0.1, | ||
"wrapEtherThreshold": 0.125, | ||
"wrapEtherTargetPerChain": { | ||
"1": 1 | ||
}, | ||
"wrapEtherThresholdPerChain": { | ||
"1": 2 | ||
}, | ||
"tokenConfig": { | ||
"WETH": { | ||
"1": { | ||
"targetPct": 100, | ||
"thresholdPct": 100, | ||
"unwrapWethThreshold": 0.5, | ||
"unwrapWethTarget": 1 | ||
}, | ||
"1135": { | ||
"targetPct": 30, | ||
"thresholdPct": 10, | ||
"unwrapWethThreshold": 0.025, | ||
"unwrapWethTarget": 0.1, | ||
"targetOverageBuffer": 1.5 | ||
} | ||
}, | ||
"LSK": { | ||
"1135": { | ||
"targetPct": 30, | ||
"thresholdPct": 10, | ||
"targetOverageBuffer": 2.5 | ||
} | ||
}, | ||
"USDT": { | ||
"1135": { | ||
"targetPct": 30, | ||
"thresholdPct": 10, | ||
"targetOverageBuffer": 1.5 | ||
} | ||
} | ||
} | ||
} |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters