Blacklist for futures dont work
Closed this issue · 19 comments
Hello! first thanks for your work!
Now I have to clarify that I have very basic knowledge but something I defend myself. Oh and I hope the translator is understood.
The bot works correctly, except for the blacklist in futures.
To confirm that I start a new clean task: I delete the previous galaxyscore.ini then I set the blacklist.txt,. And I run the galaxyscore.py again.
For example there is a pair in binance futures that was running continuously USDT_NEARUSDT and I had already put it in the blacklist.txt. Unfortunately the native 3commas blacklist does not omit these pairs and the bot places them the same, as my SO and BO is the minimum, the bot does not save the changes and does nothing showing me an insufficient funds error from the 3c-helper, since NEAR It asks for 17 dollars minimum to run.
I really don't know how to make the bot skip certain pairs from 3c cyber-bots helper
I hope you give me a hand, thank you!
edit:
Solution, correct sintax for futures (old):
USDT_BTC
USDT_SOL
USDT_UNI
....
USDT_XXX
edit2:
Now correct sintax (for futures) with the new update (~01/07/22)
USDT_BTCUSDT
USDT_SOLUSDT
USDT_UNIUSDT
....
USDT_XXXUSDT
#57 Should fix this i suppose.
#57 Should fix this i suppose.
Thanks for the help although I did not get any changes since I just changed those lines of code and it still gives me the same error: /
@dangalv what does your -d and or -b parameter look like?
@dangalv what does your -d and or -b parameter look like?
Sorry friend, I'm half green in terms of certain technicalities in this language, should I run that parameter in the console? How should i do it? thanks
@dangalv you want to use a blacklist, you have enabled it using the -b argument you give when executing the script.
So in short, with which command and arguments do you start the script above? ;-)
@dangalv quiere usar una lista negra, la ha habilitado usando el argumento -b que da al ejecutar el script. Entonces, en resumen, ¿con qué comando y argumentos inicias el script anterior? ;-)
I was run it directly without any argument, I was open the .py file and put the program to run from the compiler..
Now I run it from the console in the "main" part but it tells me that the -b parameter expects an argument. I have tried in different ways because I don't have a clear understanding of python apart from the logic of certain things in the program.
Edit: I just put only "/ galaxyscore.py -b blacklist" (I was trying to put the parameter and the argument with brackets so it didn't work for me, a novice syntax error I suppose) and it just started the program so I suppose it has taken it. I hope to have good news. Thanks
Yeah you have to run it as described... closing
Please read!!!!!!
It says it can't open the blacklist, thats whi I asked you to specify how you start it.
The blacklist is called blacklist.txt so you need to add -b blacklist.txt...
Please read!!!!!!
It says it can't open the blacklist, thats whi I asked you to specify how you start it. The blacklist is called blacklist.txt so you need to add -b blacklist.txt...
ok it's true some time ago I put the extension txt and I had been told that the file was not found so I discarded putting the extension.
Now the wizard read the blacklist but the skipped pairs are still being placed
Edit: I tried with the paper account and here the blacklist works fine.. But not from the real futures account
...
Someone else to help me with this problem that the wizard does not read the futures blacklist?
Did you try with -b blacklist.txt yet?
First you must get rid of the error opening the blacklist.
Did you try with -b blacklist.txt yet? First you must get rid of the error opening the blacklist.
Yes, as I said in the previous message it was able to read the blacklist, but the wizard seems to only execute the common pairs for example BTC_USDT but it does not execute the USDT_BTCUSDT futures pairs.
Tested on paper wallet (works) and then on real futures account (doesn't work)
Your base_order and safety_order values are too low, I cannot fix that since minimum base order value changes per pair, and even over time for same pair, this script only changes pairs not the other values, you need to change the bot settings I guess. So when the script changes the pairs, there can be another minimum value needed and the script just use the values from the bot which were in there already
Your base_order and safety_order values are too low, I cannot fix that since minimum base order value changes per pair, and even over time for same pair, this script only changes pairs not the other values, you need to change the bot settings I guess. So when the script changes the pairs, there can be another minimum value needed and the script just use the values from the bot which were in there already
It's precisely for that problem (base_order / safety_order values are too low) that I want to use the blacklist to be able to omit those pairs that need a high capital such as SOL, UNI, BTC, etc.
I understand, so USDT_UNIUSDT is on a line in the blacklist.txt right?
Can you set debug = True in your altrank.ini file and run again until error comes up, then copy last part of the logs/altrank.log showing what it does?
You can mask the botid's and other info you want to hide.
It seems that now it works, you just have to put the pair in the traditional way: "btc_usdt" instead of "usdt_btcusdt".
Since you remove the log I can't check why and fix it, or document it, but nice to hear it works.
Since you remove the log I can't check why and fix it, or document it, but nice to hear it works.
Ready! It seemed impossible but the correct syntax for futures is for example:
USDT_BTC
USDT_SOL
USDT_UNI
In this way, checked by me and with several pairs, there is no problem with the blacklist and futures.
thanks