We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I've selected BCH and XRG as pairs. I've BCH balance but no order to buy XRG is created. I see no error or any indication of an issue.
I had orders to sell BCH for KMD when I added KMD as a pair but no for XRG.
{ "price_url": "https://prices.cipig.net:1717/api/v2/tickers?expire_at=600", "bot_refresh_rate": 180, "cfg": { "XRG/BCH": { "base": "XRG", "rel": "BCH", "base_confs": 3, "base_nota": true, "rel_confs": 3, "rel_nota": true, "enable": true, "price_elapsed_validity": 180, "check_last_bidirectional_trade_thresh_hold": true, "min_volume": { "usd": 1.0 }, "max_volume": { "usd": 200.0 }, "spread": 1.005 }, "BCH/XRG": { "base": "BCH", "rel": "XRG", "base_confs": 3, "base_nota": true, "rel_confs": 3, "rel_nota": true, "enable": true, "price_elapsed_validity": 180, "check_last_bidirectional_trade_thresh_hold": true, "min_volume": { "usd": 1.0 }, "max_volume": { "usd": 200.0 }, "spread": 1.005 } } }
The text was updated successfully, but these errors were encountered:
It could be the XRG electrums, they've been a little irregular https://stats.kmd.io/atomicdex/electrum_status/ The other reason it might not add orders is if it cant find a price for one of the coins in the pair, but I can see a price for XRG in https://prices.cipig.net:1717/api/v2/tickers?expire_at=600 so that doesn't seem to be the cause.
Sorry, something went wrong.
No branches or pull requests
I've selected BCH and XRG as pairs. I've BCH balance but no order to buy XRG is created. I see no error or any indication of an issue.
I had orders to sell BCH for KMD when I added KMD as a pair but no for XRG.
The text was updated successfully, but these errors were encountered: