-
Notifications
You must be signed in to change notification settings - Fork 740
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
Quote Currency #376
Comments
I haven't done this myself, but I believe others are doing this in the current code base - without modifications. |
@hebawom Thanks. I tried a bot setup for YFI-BTC and got it to successfully trade...Yay. However, I am really wanting to set up for XLM-BTC and I'm getting errors:| Python Crypto Bot || Release : v2.45.1 || Market : XLM-BTC |
|
I see what the problem is here. XLM is a really low cost crypto and BTC is really high priced. So the cost of XLM in BTC is a lot less than 0.0001. Probably just need to adjust in the validation. How much XLM are you trying to buy and how much is that in BTC? At least that will give us an indication of what sort of precision we need. |
@whittlem Thanks for considering adding this. I have 0.0123 BTC (~$400) that I'm trying to start the bot with, using 100% of the BTC to buy XLM. |
@whittlem binance provides the limits and precisions for all tradable pairs, we don't have to guess, just request that information from the exchange and use it. |
@whittlem I'm running into a similar problem on Coinbase using SHIB-USD. Looks like the current trading price for SHIB is 0.00001047 USD. How can I work around this with PyCryptoBot? |
I am unable to get a bot to work using the crypto markets. Would it be possible to make some code changes to allow for the "quote currency" to be set to something other than the fiat currency markets? It would be nice to be able to set up a bot for YFI-BTC or ADA-ETH. This would also make it possible to run multiple bots in the same coinbase portfolio as long as the base currencies are different and the quote currencies are different.
The text was updated successfully, but these errors were encountered: