Ability to set a custom fee for dry-run trading #3696
Comments
|
What would be the reason for this? Freqtrade is assuming the exchange's default fee for trades in dry-run (so for binance, thats 0.1%). Apart from that - Especially when aiming for very minimal profits per trade, you must be very careful how you price your trades (which side of the orderbook, which order type, ...) - as dry-run will always assume that an order fills within seconds - which in live may not the case if the order is priced poorly. |
I think it would help with consistency between hyperopt, backtest and dry-run.
I agree, in the meantime I've set a 0.2% fee to account for that. Maybe this could be mentionned in the docs? If you think this is not a useful improvement feel free to close the ticket :) |
|
by setting fees to 0.2% - the effective fees will be 0.4% (0.2% for open, 0.2% for close). I'm indecided on this - if someone feels like doing a PR for it i'm sure to look at it, but personally, i see no benefit - so myself i don't think i'll implement this any time soon. |
|
@xmatthias I would like to take this issue up. I will look to set up the custom fee for dry run |
|
sure, go for it I think it shouldn't be "too" hard - best look at the methods The setting (fee) should already be there for backtesting, so there's not "too much" additional setup required. If you need any help, best submit a PR with "what you got" at that point - so we can look at it together. |
|
@xmatthias that sounds great, thanks!! |
Describe the enhancement
Hi, just registered on github for a quick suggestion. I think it would be great to have an option to set a custom fee when running
tradewithdry-runenabled in the JSON config.As for the parameter
dry_run_wallet, I'd love to be able to set an option likedry_run_fee.My strategy is based on small profits, and while I can set the fee in backtesting/hyperopt (with the
--feeparameter), I didn't find a way to do it with the dry-run mode, and my strategy runs poorly.What do you think?
The text was updated successfully, but these errors were encountered: