-
-
Notifications
You must be signed in to change notification settings - Fork 5.7k
New issue
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
possibility to add custom pairlist filters and protections without changing the freqtrade sourcecode #4477
Comments
well the point on having a fixed list is to allow config validation - to tell you if you misspelled a protection, or whatever. removing that is a possibility - but currently, plugins are not meant to be user-extended on purpose. Especially for protections - it's still marked as beta feature - which means the interface to these methods can change at any time. I also don't think that writing custom protections / filters is something people will do very often - and the documentation for doing so is in the developer / contributor section - so when writing it, contributing it to freqtrade should clearly be the goal (i don't think you can do too many "secret sauce" things to either of the two which would put you at a disadvantage if you shared it). |
Actually I've just written a Pairlist plugin (nothing special, binance specific, but attached just in case somebody is looking for it) after some discussion in #strategy-chat. It would be really nice to be able to have some working plugin mechanism there. https://gist.github.com/bzed/84775b495d553130cc2e0655a4d92306 |
Simillary, if there was a turnover pairlist it would be great, taking into account the volume and the traded price. |
+1 I think the filter is important. can select the right pairs to trade. |
That would be cool for blacklisting new announced delisting pairs |
Its not really practical to add custom pairlist filters to freqtrade sources (ie: freqtrade/constants.py).
There should be the possibility to add custom pairlist filters and protections without changing the freqtrade source.
I suggest to add a new folder user_data/plugins for custom plugins.
The text was updated successfully, but these errors were encountered: