Exchange-specific Notes¶

This page combines common gotchas and informations which are exchange-specific and most likely don't apply to other exchanges.

Binance¶

Stoploss on Exchange

Binance supports stoploss_on_exchange and uses stop-loss-limit orders. It provides great advantages, so we recommend to benefit from it.

Blacklists¶

For Binance, please add "BNB/<STAKE>" to your blacklist to avoid issues. Accounts having BNB accounts use this to pay for fees - if your first trade happens to be on BNB, further trades will consume this position and make the initial BNB order unsellable as the expected amount is not there anymore.

Binance sites¶

Binance has been split into 3, and users must use the correct ccxt exchange ID for their exchange, otherwise API keys are not recognized.

binance.com - International users. Use exchange id: binance.
binance.us - US based users. Use exchange id: binanceus.
binance.je - Binance Jersey, trading fiat currencies. Use exchange id: binanceje.

Kraken¶

Stoploss on Exchange

Kraken supports stoploss_on_exchange and uses stop-loss-market orders. It provides great advantages, so we recommend to benefit from it, however since the resulting order is a stoploss-market order, sell-rates are not guaranteed, which makes this feature less secure than on other exchanges. This limitation is based on kraken's policy source and source2 - which has stoploss-limit orders disabled.

Historic Kraken data¶

The Kraken API does only provide 720 historic candles, which is sufficient for Freqtrade dry-run and live trade modes, but is a problem for backtesting. To download data for the Kraken exchange, using --dl-trades is mandatory, otherwise the bot will download the same 720 candles over and over, and you'll not have enough backtest data.

Bittrex¶

Order types¶

Bittrex does not support market orders. If you have a message at the bot startup about this, you should change order type values set in your configuration and/or in the strategy from "market" to "limit". See some more details on this here in the FAQ.

Restricted markets¶

Bittrex split its exchange into US and International versions. The International version has more pairs available, however the API always returns all pairs, so there is currently no automated way to detect if you're affected by the restriction.

If you have restricted pairs in your whitelist, you'll get a warning message in the log on Freqtrade startup for each restricted pair.

The warning message will look similar to the following:

[...] Message: bittrex {"success":false,"message":"RESTRICTED_MARKET","result":null,"explanation":null}"

If you're an "International" customer on the Bittrex exchange, then this warning will probably not impact you. If you're a US customer, the bot will fail to create orders for these pairs, and you should remove them from your whitelist.

You can get a list of restricted markets by using the following snippet:

import ccxt
ct = ccxt.bittrex()
_ = ct.load_markets()
res = [ f"{x['MarketCurrency']}/{x['BaseCurrency']}" for x in ct.publicGetMarkets()['result'] if x['IsRestricted']]
print(res)

Random notes for other exchanges¶

The Ocean (exchange id: theocean) exchange uses Web3 functionality and requires web3 python package to be installed:
```
$ pip3 install web3
```

Send incomplete candles to the strategy¶

Most exchanges return incomplete candles via their ohlcv / klines interface. By default, Freqtrade assumes that incomplete candles are returned and removes the last candle assuming it's an incomplete candle.

Whether your exchange returns incomplete candles or not can be checked using the helper script from the Contributor documentation.

If the exchange does return incomplete candles and you would like to have incomplete candles in your strategy, you can set the following parameter in the configuration file.

{

    "exchange": {
        "_ft_has_params": {"ohlcv_partial_candle": false}
    }
}

Danger of repainting

Changing this parameter makes the strategy responsible to avoid repainting and handle this accordingly. Doing this is therefore not recommended, and should only be performed by experienced users who are fully aware of the impact this setting has.