🔥🔥🔥🔥🔥[GUNBOT] Trading Bot with 136 exchanges available!!!🔥🔥🔥🔥🔥

[Clannad]

Hi all

I got the following error while trying to start my first trades ... any idea ?

Code:

BTC_FCT === ERROR ===Permission denied
Undefined

I see the same in err.txt

I get the same error with any pair

I am on Win 10 64 Pro on an account with admin privileges and UAC disabled.
I have excluded Gunbot directory from Windows Defender
I have added gunbot.exe, engine.exe and 1000trades.exe to the firewall authorized apps

EDIT: Problem found !
I had my API Key restricted to trusted IP, but I forgot to set my IP
I was wondering wether I delete this post, but I thought it might help ppl encountering the same problem

[1713924527]

1713924527

[1713924527]

1713924527

[1713924527]

1713924527

[1713924527]

1713924527

[Gunthar]

1) I can see by default Security Margin is set to 2% (I remember it used to be set to 60% earlier). At 2% that doesn't leaves a lot of room for the coin to move. Don't you think it might result in a lot of sells at 2% loss ?

Use 2% only when you try to scalp coins like BBR, PINK, PASC or any other coin that can go +200% now and -500% in one hour: dare an higher GAIN on those coins too, like 3 or 4 %

All other coins i have security margin disabled (60%)

2) Is Max latest prices the number of 15 mins candles ? ie 300 = 75 hours of data ? Or is it the number of different tickers received (thus unknown time period) ?

it is the number of different tickers received you set in Time Delay Price

3) Could you store our credentials locally so we don't have to input them manually each time we start Gunbot ?

No 
Just leave the configurator open and change coin pairs then press the start gunbot button again: it will not ask again for your credentials.

[Clannad]

Thanks Gunthar for your detailed answers, much appreciated !

Ok here is my first feedback about Gunbot after a few hours using it.

My initial balance on 2017/02/14 at 07:00 is 0.62957643 BTC

I started Gunbot on five pairs on BTC Market: FCT, XMR, PASC, XRP and DASH

For this first test I set parameters on all pairs as:
Gain: 1%
Max Balance to Trade: 5% (I wanted to start with small amounts at first try)
Security Margin: 50%
Max Latest Prices: 300
EMA1: 2 - EMA2: 4
Minimum volume: 50
Minimum variation: 5%
Candlesticks : 15 mins

So far Gunbot bought on all five markets
It sold on XRP market with a profit of +0.00034497 BTC, my first earnings 
All other markets have Sell Orders placed.

PROBLEMS

1)  Problems with Max Balance to Trade:

Gunbot bought 0.09128849 worth of XMR which is 14.5% of my initial BTC balance, when it was set to 5%.

My remaining balance was then 0.53828794 BTC

Then Gunbot Purchased 0.04496919 worth of DASH, which is 8.35% of the remaining BTC balance, when it was set to 5%

My remaining balance was then 0.49331875 BTC

Then Gunbot purchased 0.08677201 worth of FCT, which is 17.59% of the remaining BTC balance, when it was set to 5%

My remaining balance was then 0.40654674 BTC

Then Gunbot purchased 0.05248306 worth of XRP, which is 12.9% of the remaining BTC balance, when it was set to 5%

My remaining balance was then 0.35406368 BTC

There were no SELLS between all these BUYS

Maybe I missunderstood something, or did something wrong, but it seems Gunbot trades (a lot) more than Max Balance to Trade.


2) I have no indication of the best pairs to trade according to the Minimum Volume (50) and the Minimum Variation (5%) I have set.


3) Nonce errors

After 6 hours of work, I have in my err.txt file more than 600 lines of this kind:

Code:

BTC_XMR === ERROR ===Nonce must be greater than 1903075251813002. You provided 1903075251813001.
BTC_PASC === ERROR ===Nonce must be greater than 1903075334489001. You provided 1903075334488001.
BTC_FCT *** POLONIEX CALLBACK | returnCompleteBalances ***Nonce must be greater than 1903075348338002. You provided 1903075348323001.
BTC_PASC === ERROR ===Nonce must be greater than 1903075375931002. You provided 1903075375931001.
BTC_XRP === ERROR ===Nonce must be greater than 1903075409270002. You provided 1903075409270001.
BTC_DASH === ERROR ===Nonce must be greater than 1903075410277001. You provided 1903075410275001.
BTC_DASH === ERROR ===Nonce must be greater than 1903075463360002. You provided 1903075463360001.
BTC_PASC === ERROR ===Nonce must be greater than 1903075468275001. You provided 1903075468274001.

Is this normal ?



SUGGESTIONS

1) I think it is not necessary to repeateadly display in the console these messages:

Code:

=== Checking pumps/dumps to not get entraped... BTC_XRP
 

=== Checking pumps/dumps to not get entraped... BTC_XRP
 

=== Checking BTC rallies to not get entraped... BTC_XRP
 

=== Checking BTC rallies to not get entraped... BTC_XRP

We know the script is doing this and it floods the console with useless info, I would rather indicate when the condition is met, like "Pump/Dump Detected, operations suspended..."


2) It would be good to have timestamps for all events in both log.txt and err.txt, makes it easier to follow what happens with the bot.



That's all for now... more to come

Oh wait ... Gunbot just made another cycle buy/sell on BTC_XRP, my profit is now +0.00057978 BTC 


Thanks again for your kind help and support, and keep on the good job !

[Gunthar]

~snip

Awesome test tx! Suggestion: raise "Time Delay Price", by the moment the bot sends the BUY order and the moment it is placed correctly on the order book, might pass a few seconds (especially if your original order is split in microorders) so, if the price stays cheap enough, the bot would keep buying over your Max Balance%, until the poloniex callback says us the orders are placed.
~Gun

[Clannad]

~snip

Awesome test tx! Suggestion: raise "Time Delay Price", by the moment the bot sends the BUY order and the moment it is placed correctly on the order book, might pass a few seconds (especially if your original order is split in microorders) so, if the price stays cheap enough, the bot would keep buying over your Max Balance%, until the poloniex callback says us the orders are placed.
~Gun

Thanks for this suggestion. I have set Time delay price to 60, which value would you suggest ?

And can I just stop all bots, change Time delay price, and restart the same pairs ? I actually have only SELL orders pending. Will the bots recover properly if stopped and restarted like this ?

[Gunthar]

~snip

Thanks for this suggestion. I have set Time delay price to 60, which value would you suggest ?

And can I just stop all bots, change Time delay price, and restart the same pairs ? I actually have only SELL orders pending. Will the bots recover properly if stopped and restarted like this ?

Personally i use 120 or 240 as time delay price so to give the bot enough time to receive callback from polo, avoiding to buy over the max % if the price stay cheap.
Yes you can stop and start safely: it will read from order book on next restart.
~Gun

[ewibit]

if you have much pairs open it seems that this will be as here:

most of my pairs have been

Code:

killed

last night

and in a few pairs I see

Code:

<--- Last few GCs --->

138502114 ms: Scavenge 1347.8 (1458.0) -> 1347.8 (1458.0) MB, 0.3 / 0 ms [allocation failure].
138502114 ms: Scavenge 1347.8 (1458.0) -> 1347.8 (1458.0) MB, 0.3 / 0 ms [allocation failure].
138502114 ms: Scavenge 1347.8 (1458.0) -> 1347.8 (1458.0) MB, 0.3 / 0 ms [allocation failure].
138503172 ms: Mark-sweep 1347.8 (1458.0) -> 1347.8 (1458.0) MB, 1057.2 / 0 ms [last resort gc].
138504231 ms: Mark-sweep 1347.8 (1458.0) -> 1347.7 (1458.0) MB, 1059.6 / 0 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x152223db4629 <JS Object>
    1: _extend [util.js:~770] [pc=0x201de0a9f4e2] (this=0x3ab888447811 <an Object with map 0x3441b83795e1>,origin=0x2c34d49980a1 <an Object with map 0x2d80f21b4ba9>,add=0x2c34d4997ee1 <an Object with map 0x2d80f21b4ba9>)
    2: connect [_tls_wrap.js:960] [pc=0x201de01a127d] (this=0xe4c6d126359 <an Object with map 0x3441b8341ea9>)
    3: arguments adaptor frame: 2->0
    4: createConnection [htt...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Abgebrochen

or

Code:

price target to sell: waiting for buy order to calculate sell price


<--- Last few GCs --->

41720609 ms: Scavenge 1343.2 (1458.0) -> 1343.2 (1458.0) MB, 0.3 / 0 ms [allocation failure].
41720609 ms: Scavenge 1343.2 (1458.0) -> 1343.2 (1458.0) MB, 0.3 / 0 ms [allocation failure].
41720609 ms: Scavenge 1343.2 (1458.0) -> 1343.2 (1458.0) MB, 0.3 / 0 ms [allocation failure].
41721731 ms: Mark-sweep 1343.2 (1458.0) -> 1343.1 (1458.0) MB, 1121.4 / 0 ms [last resort gc].
41722889 ms: Mark-sweep 1343.1 (1458.0) -> 1343.1 (1458.0) MB, 1158.2 / 0 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x111561bb4629 <JS Object>
    1: _onImmediate [/home/xxx/gunbot/node_modules/request/request.js:583] [pc=0x29ac717500f0] (this=0x9c6f37c8fb1 <an Immediate with map 0x317daa9e9bb1>)
    2: _immediateCallback(aka processImmediate) [timers.js:383] [pc=0x29ac7174f80a] (this=0x1f3cb9a1d301 <a process with map 0x242bb5d10f99>)

==== Details ================================================

[1]: _onImmediate [/home/xxx/gunbot/...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Abgebrochen

or

Code:

price target to sell: waiting for buy order to calculate sell price

*** POLONIEX CALLBACK | calcutating EMA1 *** BTC_MYR
statusCode 429

***GUNBOT is calculating pumps and dumps...please wait BTC_MYR



<--- Last few GCs --->

37365194 ms: Scavenge 1339.0 (1458.0) -> 1339.0 (1458.0) MB, 0.3 / 0 ms [allocation failure].
37365195 ms: Scavenge 1339.0 (1458.0) -> 1339.0 (1458.0) MB, 0.3 / 0 ms [allocation failure].
37365195 ms: Scavenge 1339.0 (1458.0) -> 1339.0 (1458.0) MB, 0.3 / 0 ms [allocation failure].
37366294 ms: Mark-sweep 1339.0 (1458.0) -> 1338.6 (1458.0) MB, 1098.8 / 0 ms [last resort gc].
37367398 ms: Mark-sweep 1338.6 (1458.0) -> 1338.8 (1458.0) MB, 1104.2 / 0 ms [last resort gc].


<--- JS stacktrace --->

==== JS stack trace =========================================

Security context: 0x192237eb4629 <JS Object>
    1: createConnection [https.js:~43] [pc=0x255814a38d5d] (this=0x61e86a32299 <an Agent with map 0x1a4839142ed1>,port=0xa6a9a76c199 <an Object with map 0x33c43aeb5339>,host=0x192237e041b9 <undefined>,options=0x192237e041b9 <undefined>)
    2: arguments adaptor frame: 1->3
    3: createSocket [_http_agent.js:~152] [pc=0x255814a2d15b] (this=0x61e86a32299 <an Agent with map 0x1a4839142ed1>,req=0x...

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory
Abgebrochen

 

[Gunthar]

~snip

uhm...

Code:

FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

what box is that? The raspbian?

[ewibit]

what box is that? The raspbian?

no

VPS, 8G RAM, quad core, Ubuntu 16.04

[Gunthar]

Updated stats of best coins to trade with the GUNBOT: https://docs.google.com/spreadsheets/d/1KxSmz6kiHMZUTFrPIy07GzutglsJkwrD2UXrUAgOv7Q/pubhtml

what box is that? The raspbian?

no

VPS, 8G RAM, quad core, Ubuntu 16.04

how many pairs?

[ewibit]

perhaps here to look for issue:

Code:

Looking for obsolete BUY orders. Ts:14/240 USDT_BTC

have set to 240 and sometimes its lookup every second...

Ts:240/240 is ready in ~300 sec...

[Gunthar]

perhaps here to look for issue:

Code:

Looking for obsolete BUY orders. Ts:14/240 USDT_BTC

have set to 240 and sometimes its lookup every second...

Ts:240/240 is ready in ~300 sec...

A loop that kills the ram, maybe. Let me see if i can reproduce this.
Thanks for reporting it!

[Clannad]

Yes you can stop and start safely: it will read from order book on next restart.
~Gun

This is just awesome !
Thanks Gunthar

[merlinsbeard]

I also bought this a few days ago, I am trading at a profit.

+1 for the suggestion to reduce the amount of clutter in the console box.

Also, this is really nitpicking but entrapped is with 2 p's, not 1 p.

=== Checking pumps/dumps to not get entraped... BTC_XMR
 

=== Checking BTC rallies to not get entraped... BTC_XMR

[Gunthar]

I also bought this a few days ago, I am trading at a profit.

+1 for the suggestion to reduce the amount of clutter in the console box.

Also, this is really nitpicking but entrapped is with 2 p's, not 1 p.

=== Checking pumps/dumps to not get entraped... BTC_XMR
 

=== Checking BTC rallies to not get entraped... BTC_XMR

lol thanks for the hint about the double "p".
Also, consider guys you prolly just bought the GUNBOT so you missed last couple months of development. There is an active group on Telegram that continuosly share opinions on how and what we should implement in the bot. I go ahead coding following that awesome group so i sometime add some more debug message that might appear annoying for those that didnt participate to suggest and develop "that" particular feature. I will do cosmetic soon or later on the bot, for now we are focused on the profit part

~Gun

[Tom0098]

I sent a PM about a possible GUNBOT test before buying and got no answers. It's started badly. 

[Gunthar]

Updated statistics for best coins to trade with GUNBOT https://docs.google.com/spreadsheets/d/16kDPLDc4yEEq4LCTx5gjSrFy04ETs5yztNs01y_7RuQ/pubhtml

Courtesy of FrilledShark's Excel SpreadSheet.

I sent a PM about a possible GUNBOT test before buying and got no answers. It's started badly.  

I hope it will get better. No trials for now tho, as stated in this thread multiple times.

[soyab0007]

Gunbot with some outstanding features..

It works great. It does exactly what it says. 24/7 trading bot, even when you sleep or not in front on Poloniex.

make sure you trade with high volume coins and one can easily gain min 1-3% profit daily..

Gunthar support has been very impressive, quick response and always available to resolve queries..

Gunbot is a must for those who are looking to snatch quick profit, without moving a fingertip..

[zedomingues]

@Gunthar

I sent you a PM.

When you can, please answer me.

tks

[spark.bet]

How much would you do to make a bot with a personal method ?