how to get Mandatory Update v.1.1.0.12
Write PM Gunthar or in Telegram @GuntharDeNiroIt is on githab, but I don't know, may I share the link or not...
Topic: 🔥🔥🔥🔥🔥[GUNBOT] Automatic Poloniex Profit Generator🔥🔥🔥🔥🔥 - page 181. (Read 508117 times)
It is on githab, but I don't know, may I share the link or not...
how to get Mandatory Update v.1.1.0.12
what about some closed slack or telegram group?
WE are on Telegram. Add me @GuntharDeNiro i give you the group 
what about some closed slack or telegram group?
Mandatory Update v.1.1.0.12 - Release name: "ClayBaron"
Changelogs:
- Do not buy on top of bullish trend (even if price is below EMA)
- Do not buy during a BTC/USD rally: we would sit days waiting for altcoins to recover
- Deprecated Bloody Mary: it wasnt the solution
- Fixing the issue of Windows 10 and Windows 2012 server users getting stucked on price updates: ECONNECT and Socket Hang Up are dealt as error and gracefully closed rather than waiting for poloniex to hang up our connection
- Minor fixes and code improvement.
I will start to deploy this by this afternoon UTC time.
~Gun
LOL, my own release version! Glad to see my criticism and suggestions inspired you. Keep up the good work Gun.
-Clay
It is a typo of the OP
it is nodemon not nodaemon
both not working... it is nodemon not nodaemon
~snip
npm install -g nodaemon
npm install -g nodaemon
you are right: it installs it as global in that way. Kudo!
Code:
npm install -g nodaemon
npm ERR! Linux 4.4.0-59-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "nodaemon"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/nodaemon
npm ERR! 404
npm ERR! 404 'nodaemon' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
It is a typo of the OP
it is nodemon not nodaemon
~snip
npm install -g nodaemon
npm install -g nodaemon
you are right: it installs it as global in that way. Kudo!
Code:
npm install -g nodaemon
npm ERR! Linux 4.4.0-59-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "-g" "nodaemon"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! code E404
npm ERR! 404 Registry returned 404 for GET on https://registry.npmjs.org/nodaemon
npm ERR! 404
npm ERR! 404 'nodaemon' is not in the npm registry.
npm ERR! 404 You should bug the author to publish it (or use the name yourself!)
npm ERR! 404
npm ERR! 404 Note that you can also install from a
npm ERR! 404 tarball, folder, http url, or git url.
~snip
npm install -g nodaemon
npm install -g nodaemon
you are right: it installs it as global in that way. Kudo!
Actually the error i'm seeing in case of a lost connection are ECONNECT and Socket Hang Up. I could try to handle the socket problem with node.js https parser and handle the ECONNECT error with a file change (for example) so nodemon would immediately restart it (even a dummy.js file would be good).
If you want to test it, you can install it with
Code:
npm install nodemon
Then launch the bot with
Code:
nodemon 1000trades.js
Then try to change any settings in config.js or params.js and you will see your bot auto-restarting
Code:
npm ERR! not a package /home/xxx/trade/gunbot/nodemon
npm ERR! addLocal Could not install /home/xxx/trade/gunbot/nodemon
npm ERR! Linux 4.4.0-59-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "nodemon"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! path /tmp/npm-29947-053bf887/unpack-aa5777fa/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-29947-053bf887/unpack-aa5777fa/package.json'
npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-29947-053bf887/unpack-aa5777fa/package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
npm install -g nodaemon
Actually the error i'm seeing in case of a lost connection are ECONNECT and Socket Hang Up. I could try to handle the socket problem with node.js https parser and handle the ECONNECT error with a file change (for example) so nodemon would immediately restart it (even a dummy.js file would be good).
If you want to test it, you can install it with
Code:
npm install nodemon
Then launch the bot with
Code:
nodemon 1000trades.js
Then try to change any settings in config.js or params.js and you will see your bot auto-restarting
Code:
npm ERR! not a package /home/xxx/trade/gunbot/nodemon
npm ERR! addLocal Could not install /home/xxx/trade/gunbot/nodemon
npm ERR! Linux 4.4.0-59-generic
npm ERR! argv "/usr/bin/nodejs" "/usr/bin/npm" "install" "nodemon"
npm ERR! node v4.2.6
npm ERR! npm v3.5.2
npm ERR! path /tmp/npm-29947-053bf887/unpack-aa5777fa/package.json
npm ERR! code ENOENT
npm ERR! errno -2
npm ERR! syscall open
npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-29947-053bf887/unpack-aa5777fa/package.json'
npm ERR! enoent ENOENT: no such file or directory, open '/tmp/npm-29947-053bf887/unpack-aa5777fa/package.json'
npm ERR! enoent This is most likely not a problem with npm itself
npm ERR! enoent and is related to npm not being able to find a file.
npm ERR! enoent
So the bloody mary strategy will be removed in the next patch? You're really producing so many updates, my friend. Maybe you should really consider that website I told you about. So everyone could be in the know. Anyway, always behind you bud! Looking forward to new update! 
Well these are user's generated patches and fixes, these are my favourite
originally i planned one update per month but as you can see...we always have nice ideas to improve the bot by talking here. I dont think a static website would give us such an opportunity...Not really for discussion on the website, just for a more centralized place to get the latest updates. I still like the thread for discussion too. Just that sometimes I have problems looking for the new updates on the thread, especially when there are plenty of people discussing the bot.
@Gunthar take your time! nobody expects the bot to be an "price predicting oracle"!-) certainly not me! This was very bad luck as well. now, I only start new pairs when they are in a "low". much better chances!
So the bloody mary strategy will be removed in the next patch? You're really producing so many updates, my friend. Maybe you should really consider that website I told you about. So everyone could be in the know. Anyway, always behind you bud! Looking forward to new update!
Well these are user's generated patches and fixes, these are my favourite
originally i planned one update per month but as you can see...we always have nice ideas to improve the bot by talking here. I dont think a static website would give us such an opportunity...
So the bloody mary strategy will be removed in the next patch? You're really producing so many updates, my friend. Maybe you should really consider that website I told you about. So everyone could be in the know. Anyway, always behind you bud! Looking forward to new update!
Mandatory Update v.1.1.0.12 - Release name: "ClayBaron"
Changelogs:
- Do not buy on top of bullish trend (even if price is below EMA)
- Do not buy during a BTC/USD rally: we would sit days waiting for altcoins to recover
- Deprecated Bloody Mary: it wasnt the solution
- Fixing the issue of Windows 10 and Windows 2012 server users getting stucked on price updates: ECONNECT and Socket Hang Up are dealt as error and gracefully closed rather than waiting for poloniex to hang up our connection
- Minor fixes and code improvement.
I will start to deploy this by this afternoon UTC time.
~Gun
may I...?!
~snip
this is how the bot gets "stuck"! and throwing more money at it by raising the % is not the answer I think! However, with XMR I still feel confident enough not to manually intervene and and just "ride it out"!
And I do hope that I dont have to live forever for this to happen!-)
PS. sorry, no 15min candles available in week view. and yes I have restarted gunbot on Feb/2
Yup!~snip
this is how the bot gets "stuck"! and throwing more money at it by raising the % is not the answer I think! However, with XMR I still feel confident enough not to manually intervene and and just "ride it out"!
And I do hope that I dont have to live forever for this to happen!-)
PS. sorry, no 15min candles available in week view. and yes I have restarted gunbot on Feb/2
Pushing a fix to that in a few hours
may I...?!
https://i.imgsafe.org/5bc461714e.jpg
this is how the bot gets "stuck"! and throwing more money at it by raising the % is not the answer I think! However, with XMR I still feel confident enough not to manually intervene and and just "ride it out"!
And I do hope that I dont have to live forever for this to happen!-)
PS. sorry, no 15min candles available in week view. and yes I have restarted gunbot on Feb/2
https://i.imgsafe.org/5bc461714e.jpg
this is how the bot gets "stuck"! and throwing more money at it by raising the % is not the answer I think! However, with XMR I still feel confident enough not to manually intervene and and just "ride it out"!
And I do hope that I dont have to live forever for this to happen!-)
PS. sorry, no 15min candles available in week view. and yes I have restarted gunbot on Feb/2
MINOR FIX AVAILABLE: for those running on windows 10 64 bit that are experiencing an issue that would stuck the bot making it not updating prices.
Please if you dont have this issue, you dont need this update. This update is for people like ewibin and/or others that reported their bot stucking at price updates.
PM me to get the patch.
Thanks!
~Gun
Please if you dont have this issue, you dont need this update. This update is for people like ewibin and/or others that reported their bot stucking at price updates.
PM me to get the patch.
Thanks!
~Gun
Gun, calm down buddy you are going to give you are self an aneurysm, lol.
You are prolly right and being 98yo is not a good thingYour, bot is still the best bot available for sale here, just trying to offer constructive criticism.
Yes it is: say it loudBack to work now:
First you never said 15 minute was ever the only profitable with the 2EMA
Yes it is specified in the Instruction manual on top of this thread but most pairs do perform better with 15 yes.
Yes they do: the 2EMA strategy works ONLY with a 15 minutes strategy because it needs the volume to work. A 5 minutes candlesticks has not enough volume to generate a responsive enough long and short EMA.My point with having you use the 5Min chart on tradingview strategy i put together, is how far back it goes on the 5 min chart for backtesting,
It is a false backtesting because you must do the backtesting with the same EMA period you use live but by all means use the 15Min chart you are going to end up with same situation of sitting for weeks.
In fact using the 15 min chart looking at the trade history on backtesting shows it would of been stuck waiting on XMR to recover from October 2 till December 27th. That is a ton of missed trade opportunities.
In fact using the 15 min chart looking at the trade history on backtesting shows it would of been stuck waiting on XMR to recover from October 2 till December 27th. That is a ton of missed trade opportunities.
Correct! That's why i deprecated the aggressive and moderate strategy to only allow the 1000trades: the difference is easy and straight:
You dont sit anymore missing trade opportunitise by the moment you place a sell order immediately allowing the bot to continue trading using the availabel balance that you still have. EVENTUALLY: only a small portion of your balance will get "stuck", not all yrou balance.
Today a user (i will find his name later and post here his questions) PMed me and told this situation.
Wanna knwo what is his limit indeed? Think abotu it for one moment: the REAL limit is the % of balance you allow the bot to trade per pair.
I could have suggested him to enable Bloody Mary! Sorry. it is against my principles lol, even if i coded it. So wanna knwo what i told that guy? I told him: stop yrou bot and raise your max % balance to 40%.
Look what he wrote me back after a while (found him while writing):
How long should you wait out this swing? Like I said in an earlier thread I have been testing this against a bot I wrote with autoview that is actually capable of taking small losses and moving on. Comparing the two accounts is a stark difference. My bot in autoview had long dug out of this latest swing while gunbot still has pairs hodl'ing.
Sorry i dont support the trade at loss: i understand the importance of it and i coded it in the bot upon users requests but here it is not a matter of creating liquidity by tradign at loss: raise your max% balance as only a small portion of yrou coins are being hold.it seems like the smarter move is to sell so as to continue trading.
As i said: no. Jump to: