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 - Aitor

Pages: 1 [2] 3 4 ... 20
Technical Support & Development / Re: Gunthy-EXE Not starting
« on: October 26, 2020, 10:46:17 PM »
Hi guys,

I'm having an issue installing Gunbot. I'm renting a VPS, with a windows server 2016 Datacentre. I've tried the most recent release and the old stable versions, but I can't get gunthy-exe to execute.

Anyone have any ideas?

Try this:

Right click the file, properties, unblock. And ejecute as admin.

General Discussion / Re: Who is broken ? Binance ? Kraken ? or Gunbot ?
« on: October 18, 2020, 11:38:11 PM »
I would try to make a fresh install in a new directory and use Emotionless, it should start making trades.
Backtesting tool is very useful and it helps a lot to make an idea of how strategies perform and it's very useful to optimize strategies.

General Discussion / Re: Who is broken ? Binance ? Kraken ? or Gunbot ?
« on: October 11, 2020, 07:50:36 PM »

Long time user of Gunbot (and not really satisfied but that's another topic). Let's see what make me write this message :
Binance : 4 pairs, last transaction 08/30/2020 !
Kraken : 2 pairs, last transaction 01/09/2020 ! 50 transactions during August

Both exchange have not generated any trades since a month or more. I reboot every 2 days the VM hosting the bot to be safe. I've searched any reasons why the bot is not working but everyting is ok, still receiving tickers, no timeout. Just stopped working nearly the same day, both of them. Network is perfect too.

Any idea ?

Hi Signman, it looks like:

1- The bot made some trades and you don't have remaining funds in base coin, that is, the bot is waiting for selling back to BTC (or whatever base coin you are using).

2- You settings are so tight that the conditions to make a trade haven't been met. This can also happen if you add too many confirming indicators.

3- There is some kind of misconfiguration.

The best way for fix it is to contact directly with your reseller so he can take a deep look to your settings, as without seeing them, it's hard to figure out what's the exact problem.

Beginners & Help / Re: Reverse Trading and VET/USDT pair
« on: October 05, 2020, 07:47:27 PM »
Hi, I'm new to GunBot (super new) and I have been getting my ass kicked by VeChain since August.  I wasn't using GunBot, but I wanted to ask does anybody have a strategy to share that I can analyze for VET/USDT or VET/USD?

Also Second question:
Reverse Trading..........Where is the best spot to learn the best practices and setting for the GunBot.

Hi Michael, your reseller is the one who will help you with anything you need. Also always have an eye in the Wiki, as it has a lot of useful info:
Regarding Reversal Trading, if you are new to Gunbot, my advice is to forget about RT and use DCA instead. RT is not easy to understand and most of the times I have seen people getting undesired behavior using it.

Thank you!  I see where to download. I'm guessing it will ask for the license number when it opens.  I'm counting on my AWS disk image to contain my license info, as that was it's home before (i lost a disk with some info on it).  Will report back here when i have success with that but it might be couple weeks before get to that. 

Never heard of Gunthy wallet.  Will have to check that out, and the Android connection as well!

If you don't have a Gunthy wallet, most likely is because your license is old, and old license system didn't require Gunthy walletr. You can send me your api via PM to locate your license.

Technical Support & Development / Re:
« on: September 21, 2020, 10:29:29 PM »
Hello all,
Is anyone here having issues connecting to I tried both keys (V2 and V4) with no success. I'm getting "cannot read property 'trades' of undefined. Thebot's been running well with no issues with Binance, Kucoin, CoinEx and few others, it just won't pull data from Gate   :(

Any ideas are greatly appreciated.

Personally I have never used this exchange. I have seen other 2 users reporting the same error on
Note that this is a supported exchange but it's not certified. This means that it haven't been fully tested yet and it can have bugs like this one.

First of all, you can get latest stable versions here:

And in the case you don't have a Gunthy wallet created, you can check how to do it here:

I keep getting this error on my Gunbot install, I had to delete all my json files before and start again, this time it happened after I saved a trading config change through the GUI.

Using latest v18.8.8 from GitHub on a AWS linux box

Makes it unusable as just goes into a crash loop

0|gunthy-linux  | TypeError: Cannot read property 'split' of undefined
0|gunthy-linux  |     at module.exports.parseOpenOrders._.forEach.o (/snapshot/v18build/ctx/js/poloniex.js:0:0)
0|gunthy-linux  |     at arrayEach (/snapshot/v18build/node_modules/lodash/lodash.js:516:11)
0|gunthy-linux  |     at Function.forEach (/snapshot/v18build/node_modules/lodash/lodash.js:9342:14)
0|gunthy-linux  |     at Poloniex.parseOpenOrders (/snapshot/v18build/ctx/js/poloniex.js:0:0)
0|gunthy-linux  |     at Object.module.exports.fetchOpenOrders.poloniex.returnOpenOrders [as callback] (/snapshot/v18build/ctx/js/poloniex.js:0:0)
0|gunthy-linux  |     at isProcessing (/snapshot/v18build/node_modules/async/dist/async.js:2271:31)
0|gunthy-linux  |     at /snapshot/v18build/node_modules/async/dist/async.js:969:16
0|gunthy-linux  |     at Request._callback (/snapshot/v18build/ctx/helper/joaquin-plnx/lib/index.js:136:7)
0|gunthy-linux  |     at Request.init.self.callback (/snapshot/v18build/node_modules/request/request.js:185:22)
0|gunthy-linux  |     at Request.emit (events.js:159:13)
0|gunthy-linux  |     at Request.<anonymous> (/snapshot/v18build/node_modules/request/request.js:1161:10)
0|gunthy-linux  |     at Request.emit (events.js:159:13)
0|gunthy-linux  |     at IncomingMessage.<anonymous> (/snapshot/v18build/node_modules/request/request.js:1083:12)
0|gunthy-linux  |     at Object.onceWrapper (events.js:254:19)
0|gunthy-linux  |     at IncomingMessage.emit (events.js:164:20)
0|gunthy-linux  |     at endReadableNT (_stream_readable.js:1054:12)
0|gunthy-linux  |     at _combinedTickCallback (internal/process/next_tick.js:138:11)
0|gunthy-linux  |     at process._tickCallback (internal/process/next_tick.js:180:9) 'Uncaught Exception thrown'

Try this:

Stop the bot. Copy the files in the Json folder save them somewhere. Then delete al the files in the json folder.

Beginners & Help / Re: TSSL with trailme Sell
« on: September 06, 2020, 03:12:54 PM »
Do TSSL sell and trailme sell do the same thing?

Like if you are using TSSL to sell and select the trailme option, is it redundant?

Yes. it's redundant. You can use trailme "as an Addon" to other strategies. TSSL would be to use Trailme "alone".

With Uniswap suddenly surpassing Coinbase Pro in volume, is there a way to get Gunbot to trade there?

Uniswap  is not sopported at this moment. Maybe it will in the future. Anyway, there are a lot of popular exchanges with very high traffic supported. You have a lot to choose from  :)

General Discussion / Re: Issue with SMAcross/Gain
« on: August 29, 2020, 09:59:21 PM »
SMA-CROSS, the strategy you are running, makes multiple buys. It's the way it works. If you want to make just 1 buy / 1 sell, better run other strategy.

General Discussion / Re: Issue with SMAcross/Gain
« on: August 29, 2020, 04:08:53 PM »
I recommend you to set Trading Limit to something higher than the minimum. For example, if the minimum amount to trade is 0.005, I would set trading limit at least to 0.008 or 0.01 and min_vol_to_trade to something like 0.007

 Some exchanges like Binance leave dust and it's something "normal". What I do is, from time to time, to use Binance tool to convert all the dust to BNB and then convert BNB back to BTC.

Also it's important to note that the lower your trading_limit is, the higher the impact of the dust will be.

By default, orders are sent as market orders. When you want to send limit orders instead, disable "Use market orders" parameter. Buy orders are then sent at a limit price of the best bid order in the order book, sell orders are placed at the rate of the best ask price.

General Discussion / Re: Issue with SMAcross/Gain
« on: August 29, 2020, 12:21:53 PM »
Is it always exactly 0.2506%? What's your Trading limit?

Marketplace / Rules and how to sell second hand licenses
« on: August 28, 2020, 07:30:57 PM »
Looking to sell your Gunbot license? Looking to buy a second hand license? Look no further, you are in the right place. In the following lines we are going to explain how to buy or sell a second hand Gunbot license with an Official scrow that will assure the license is transferred in a safe way.

Before starting using this second hand buy & sell system, you need to fully understand how it works and follow these rules:

1- First of all, use this invitation link to join the official Gunbot second hand licenses channel:

2- Note that this isn’t a group, it’s a channel, that is, you can’t chat. In order to post your sale, you have to contact to one of the Official scrows via Telegram or via PM in this forum:

Aitor: Telegram = @AitorRuiz

Javier: Telegram = @JavierAlv

3- Once you contact one of the official scrows, your license will be verified and ready for being sold. At this moment, we will post your sale in our channel, so the potential buyers can see it.

Example 1:  Pro license – 0.05 btc – My telegram: @YourUsername

Example 2: Ultimate license + 25000 Gunthy tokens – 0.165 btc – My telegram: @YourUsername

5- As you can see, the sale include your Telegram username. This way the potential buyers will be able to contact you and get to an agreement.

6- Once you reach to an agreement, contact with one of the Official scrows via Telegram: @AitorRuiz or @JavierAlv, so the license transfer will be safe and successful.


Additional notes

– By default, the seller has to send the Gunthy tokens that comes with the license to the buyer. In the case he doesn’t, he must clarify it to the buyer before proceeding with the sale.

– By default, the price especified by the seller is the total price, including escrow fees. In the case the seller wants to apply escrow fees to the buyer, apart from the license price, he must clarify it to the buyer before proceeding with the sale.


Additional security tips

a) This is the official channel where buying and selling second hand licenses is allowed. Do not trade anywhere else or you will be exposed to a very high chance of getting scammed.

b) Contact the admins directly if you have any question or request.

c) Escrow is a must. If you trade without a scrow or use a scrow that is not listed in this post as Official Scrow, you will be scammed and we won’t be able to help you.

d) Watch out for impostors, always double check the Telegram username (every single letter) is a Official Escrow: @AitorRuiz or @JavierAlv . It’s recommended to click on a username to open a chat with the respective escrow yourself.

As you said, there isn't amount rate for selling. Anyway, once the selling conditions are met, the most logical move is to sell ALL. Personally that's what I do, and, tbh, if the selling conditions are met, I don't see the point on selling just a %, it just slows down the bot and would make things worse IMO.

Technical Support & Development / Re: Telegram No Bot token
« on: August 27, 2020, 12:41:11 AM »
I double checked and made sure the token id is correct.  I also put the id in the other two fields, even though I am not using them.  I still get the error no token.

If you are using only the main Telegram bot, then just fill the Token field and don't enable "Autoconfig alerts" and don't fill other tokens.
If you are running just the main Telegram bot and you are getting "Missing bot token" there can only be one reason: the token field is empty or the token is not valid. So just fill the main token and be sure you fill it like this:

Technical Support & Development / Re: Telegram No Bot token
« on: August 24, 2020, 09:03:00 PM »
The error can be caused just because you didn't copy / paste the token code properly in "Token" field. Even if this is ok, in the case you activated "Autoconfig Telegram bot Enabled" in v18 or  "Autoconfig Alerts"  in v19, you need to put the second token in the field: ""Token for BitRage & Autoconfig alerts", and in the case you don't, you get the error.

Haven't used gunbot in a while.
I own the old version, I think I went up to version 8 or 9.

In the old version, there was no gunthy wallet. Now there is.

I installed and got everything set up, key and secret etc, and set up the exchange.

I created a Gunthy wallet which is now empty.

I assume the coin paid for gunbot goes into this wallet?
Or is there something I am missing?

Anyway when I run gunthy-win.exe the text in the window continuously runs and returns this message...

"Failure to meet minimum Gunthy token balance requirement to operate the bot. Please purchase more tokens to run the bot..."

So, what do I need to do to get this version running?

First of all, create a Gunthy wallet, as new license system requires it:

Then send it to your reseller, so he can link your wallet to your api key.

Technical Support & Development / Re: Traiding pairs not showing up
« on: August 23, 2020, 04:17:16 AM »
Glad to hear you fixed it  :)

No offense but...This isn't really fixed, it's been worked around. The actual problem with v18 isn't solved.
I also receive this error using Binance. It runs one cycle of defined pairs and then starts giving back "Kicking Binance, receiving new tickers"
Debug switched on in the web interface does not give back more useful information on this.

Could this issue be addressed or somehow explained why this is happening?


Hi, note that exchanges sometimes make some upgrades / changes / maintenance that makes the bot to get some undesired errors. Despite v18.8.8 is the latest stable version, v19 beta fixes some of these issues and in some cases the update is necessary. In this case, the upgrade to v19 will fix the issue. For those who use ARM, considering that there isn't still v19 for ARM, I have seen that in some cases, the installation of 18.3.9 + remove JSON directory has fixed some issues like this one. Obv the best solution is to update to latest v19 version.

Pages: 1 [2] 3 4 ... 20