Author

Topic: 🔥🔥🔥🔥🔥[GUNBOT] Automatic Poloniex Profit Generator🔥🔥🔥🔥🔥 - page 176. (Read 508117 times)

sr. member
Activity: 504
Merit: 250
Hi.
Is it safe to provide API key?
Hope you wont be having an access to my poloniex history
hero member
Activity: 714
Merit: 501
Real Eyes, Realize, Real Lies.
i'm runnin this thing w 14 pairs at the moment, including btc/rep and xmr/rep at the same time and sometimes it will buy rep on btc and sell it on xmr and such things.

which is cool and all, but hard to figure if it's winning or losing.


how many pairs are you guys spanking?
You will only lose if your % of gain is under .5% or if your security margin is reached, otherwise if the pair is sold you profited the amount that you set % of gain.
member
Activity: 62
Merit: 10
liberty
i'm runnin this thing w 14 pairs at the moment, including btc/rep and xmr/rep at the same time and sometimes it will buy rep on btc and sell it on xmr and such things.

which is cool and all, but hard to figure if it's winning or losing.


how many pairs are you guys spanking?
hero member
Activity: 1498
Merit: 614
Liable for what i say, not for what you understand
Updated statistics of best coins i trade with the GUNBOT https://docs.google.com/spreadsheets/d/16kDPLDc4yEEq4LCTx5gjSrFy04ETs5yztNs01y_7RuQ/pubhtml

Great performance from highest volume coins again!




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

I dunno, try to PM me and explain what you need maybe
~GUn
full member
Activity: 155
Merit: 100
How much would you do to make a bot with a personal method ?
jr. member
Activity: 46
Merit: 22
@Gunthar

I sent you a PM.

When you can, please answer me.

tks
hero member
Activity: 560
Merit: 500
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..
hero member
Activity: 1498
Merit: 614
Liable for what i say, not for what you understand
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.  Undecided

I hope it will get better. No trials for now tho, as stated in this thread multiple times.
newbie
Activity: 15
Merit: 0
I sent a PM about a possible GUNBOT test before buying and got no answers. It's started badly.  Undecided
hero member
Activity: 1498
Merit: 614
Liable for what i say, not for what you understand
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.

Quote
=== 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 Wink

~Gun
member
Activity: 66
Merit: 10
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.

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

=== Checking BTC rallies to not get entraped... BTC_XMR
newbie
Activity: 23
Merit: 0
Yes you can stop and start safely: it will read from order book on next restart.
~Gun
This is just awesome !
Thanks Gunthar
hero member
Activity: 1498
Merit: 614
Liable for what i say, not for what you understand
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... Shocked

A loop that kills the ram, maybe. Let me see if i can reproduce this.
Thanks for reporting it!
legendary
Activity: 2955
Merit: 1049
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... Shocked
hero member
Activity: 1498
Merit: 614
Liable for what i say, not for what you understand
legendary
Activity: 2955
Merit: 1049

what box is that? The raspbian?
no

VPS, 8G RAM, quad core, Ubuntu 16.04
hero member
Activity: 1498
Merit: 614
Liable for what i say, not for what you understand
~snip

uhm...
Code:
FATAL ERROR: CALL_AND_RETRY_LAST Allocation failed - process out of memory

what box is that? The raspbian?
legendary
Activity: 2955
Merit: 1049
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
    1: _extend [util.js:~770] [pc=0x201de0a9f4e2] (this=0x3ab888447811 ,origin=0x2c34d49980a1 ,add=0x2c34d4997ee1 )
    2: connect [_tls_wrap.js:960] [pc=0x201de01a127d] (this=0xe4c6d126359 )
    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
    1: _onImmediate [/home/xxx/gunbot/node_modules/request/request.js:583] [pc=0x29ac717500f0] (this=0x9c6f37c8fb1 )
    2: _immediateCallback(aka processImmediate) [timers.js:383] [pc=0x29ac7174f80a] (this=0x1f3cb9a1d301 )

==== 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
    1: createConnection [https.js:~43] [pc=0x255814a38d5d] (this=0x61e86a32299 ,port=0xa6a9a76c199 ,host=0x192237e041b9 ,options=0x192237e041b9 )
    2: arguments adaptor frame: 1->3
    3: createSocket [_http_agent.js:~152] [pc=0x255814a2d15b] (this=0x61e86a32299 ,req=0x...

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

 Huh


hero member
Activity: 1498
Merit: 614
Liable for what i say, not for what you understand
~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
newbie
Activity: 23
Merit: 0
~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 ?

Jump to: