Username: Password:

Show Posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.


Messages - cryptkeeperxxx

Pages: [1]
1
Yes, please spread the word by forwarding this to the developers. If you and others forward this to @gunthardeniro on telegram, then it might get prioritization and implementation.

2
Thanks for the support! I just saw a message from Gunthar and he said he would give it a look. So, it looks like great stuff might be on the way.

3
Thanks for joining with support for the cause :). Please, spread the word to developers every way you can (telegram, discord, github https://github.com/GuntharDeNiro/BTCT/issues/358 and so on for prioritization. It's up to us to get the word out to get this implemented.

4
Welcome here and thanks for the positive support. I followed oldskoolnix's advice and posted on github, too. If you'd like to maximize opportunity with exchanges, Binance in particular, then I encourage you to join in and offer this solution to the developers for the benefit of everyone. Gunbot and its developers are excellent, so let's see what we can do to make things the best they can be :)

5
Thanks buddy. I'll check that out.

6
Hi everyone,

I have a solution to offer for a Binance problem that deactivates trading on Gunbot. I reached out to multiple Gunbot workers many times, but it seems they haven't been able to get to it, since I imagine they are very busy. So please, let's all pass this along to the developers to prioritize implementation.

Binance terminates Gunbot trading when the secondary currency in a pair sells down to dust levels (below 0.01 or 0.001 equivalence, depending on the currency).

Manually fixing the dust (manually buying more) works for a while, but even with fixing dust and starting fresh with MIN_VOLUME_TO_BUY and MIN_VOLUME_TO_SELL (neither of which seem to consistently work with Binance) set at good levels (even extreme levels for the sake of testing), dust eventually results and terminates Binance trading with Gunbot, even with v.7.0.2 stable.

So, my suggestion and request to fix this Binance issue would be the implementation of a FUNDS_RESERVE for the secondary currency in a pair--not the primary currency, since we already have the current FUNDS_RESERVE helping with that. It could be called SECONDARY_FUNDS_RESERVE or something like that and it would effectively set the secondary currency base level at a Binance acceptable level to keep trading active without fear of entering dust levels and deactivating trading over time.

Another benefit of what would be something like SECONDARY_FUNDS_RESERVE is that it would function to allow portions of secondary currencies to act as longer-term hold investments--not actively traded--while portions of that same secondary currency are open to active trading investments.

This is especially useful for currencies with private wallet issues like, for example, IOTA, which currently has the 7th largest market capitalization of all cryptocurrencies, and since its tangle network currently lacks mature development, many people are circumstantially inclined to use exchanges as hold wallets for it. If people want to hold a set portion of it and actively trade another portion of it at the same time, their options are currently limited, barring making separate accounts, which can present other issues. So, a secondary funds reserve function would solve this for everyone.

Please, let's all pass this along to the developers to prioritize implementation and thanks so much!

7
Thank you for the reply. I tried that on other instances and still nothing, but I sincerely appreciate the feedback.

8
SOLVED


I just had to run on another machine. For whatever reason, that fixed things. I hope this helps others with similar circumstances.

Pages: [1]