-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
1 parent
2a312ac
commit 5b96378
Showing
2 changed files
with
76 additions
and
0 deletions.
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
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,14 @@ | ||
1. Currently, the trading pairs come from the configuration files: | ||
- `trading.yaml` has the main list of symbols (BTC/USDT, ETH/USDT, BNB/USDT) | ||
- `strategies.yaml` has pairs for inefficiency detection | ||
|
||
2. The system doesn't actually take trading pairs directly from clients. Instead: | ||
- The main system trades the pre-configured pairs from trading.yaml | ||
- The robo-advisor component manages client portfolios using these same pairs | ||
- There's no current mechanism for clients to specify custom trading pairs | ||
|
||
This could be improved by: | ||
1. Adding client-specific trading pair configuration | ||
2. Implementing validation for client-requested trading pairs | ||
3. Adding dynamic pair management | ||
4. Creating separate trading pair pools for system vs client trading |