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
{{ message }}
This repository has been archived by the owner on Feb 1, 2024. It is now read-only.
When using ccxt via DATA_FEED_B_URL="ccxt-poloniex/ETH/USDT" in buysell.cfg, kelp's logs are showing 2019/02/21 00:56:42 price from exchange feed (ccxt-bittrex/ETH/USDT): bidPrice=147.0000000, askPrice=148.0000000, centerPrice=147.5000000, which seems to be overly rounded, whereas querying ccxt directly results in correct/more-precise prices.
Expected behavior
kelp should pull in (and use) more accurate prices when possible (for example, when using sdex)
Frequency
Seems to be always
Steps To Reproduce
Set up ccxt via DATA_FEED_B_URL="ccxt-poloniex/ETH/USDT" in a buysell.cfg
With too low a precision value there are many cases where no trades will ever be made even though there could be a ~1% difference in certain assets (for example, with ETH)
The text was updated successfully, but these errors were encountered:
Describe the bug
When using ccxt via
DATA_FEED_B_URL="ccxt-poloniex/ETH/USDT"
in buysell.cfg, kelp's logs are showing2019/02/21 00:56:42 price from exchange feed (ccxt-bittrex/ETH/USDT): bidPrice=147.0000000, askPrice=148.0000000, centerPrice=147.5000000
, which seems to be overly rounded, whereas querying ccxt directly results in correct/more-precise prices.Expected behavior
kelp should pull in (and use) more accurate prices when possible (for example, when using sdex)
Frequency
Seems to be always
Steps To Reproduce
Set up ccxt via
DATA_FEED_B_URL="ccxt-poloniex/ETH/USDT"
in a buysell.cfgYour Environment
version: fixed_fee:v1.4.0-3-ga0362947
git branch: fixed_fee
git hash: a036294
build date: 20190220T231403Z
GOOS: linux
GOARCH: amd64
Context
With too low a precision value there are many cases where no trades will ever be made even though there could be a ~1% difference in certain assets (for example, with ETH)
The text was updated successfully, but these errors were encountered: