-
-
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
UserPairlist handler to manage "Manual" pairlists #4493
Comments
@xmatthias
|
I guess this approach could work (assuming you have no bugs) - but it's not what this issue is about, but about providing a way to manage the pairlist "online" - either via API or via telegram. Investigating why your code will or will not is however clearly not part of this issue. |
The dream would be to have full (and easy) programmatic freedom. But I wonder if a good first version is an |
Describe the enhancement
we could have a
UserPairlist
(name to define - this one is probably not good) pairlist, which will either provide a full pairlist (simliar to staticpairlist) - or inject additional pairs to the pairlist.This
UserPairlist
get's the pairlist from a (new) database table - allowing full control to RPC by adding and removing pairs from this userpairlist at will (it's empty by default, but persisted across restarts by beeing in the database).as the pairlist is refreshed quite often (once every iteration, unless the pairlist implements some caching) - users could simply add / remove your pair, and it'd magically appear without changing configuration or whatever.
obviously blacklist (and such) will still apply as usual, so you can't whitelist pairs that are in a blacklist - but that shouldn't really be a problem i'd hope.
It can act as both a "generator" (first position of the pairlists) - or as filter (which will add the pairs in it's list).
The text was updated successfully, but these errors were encountered: