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

Pages: [1]
Beginners & Help / Historical Analysis
« on: September 04, 2018, 12:02:30 PM »
Is there an easy way to run the bot on historical data for each coin? I think some exchanges (binance allow you to download the candlestick data) could I then run the bot with my config and test it?

Beginners & Help / 2 orders, cancel one if the other fills
« on: September 04, 2018, 11:51:41 AM »

I want the ability to configure the bot to make 2 orders based on if a certain set of indicators cross or appear. The orders would be 1% stop loss orders too. That way if the market shoots either way I can catch it.  My question is.

1. How can i get the gun bot to place those future orders at the same time?
2. How are you able to place short orders on binance or poloniex?
3. How do you set a static stop loss of 1%, not a trailing stop loss.
4. How can I be sure it's cancelled the other order as soon as the first one fills?

Beginners & Help / Re: Gunbot Monitor - Oversee all GUNBOTs in one screen
« on: January 02, 2018, 12:37:23 AM »
Aww I just read that there is no way to get this to work with the new 7 version :(

Does Gbot now not save the logs? Because when i use the web interface i can still see the logging being created, it would be nice to have the option to output the logs again to enable this to work.  I really like the monitor as it really quickly helped me to see my overall position, whereas the other GUIs don't.

Would love to get it back working again!

Beginners & Help / New Linux Tutorial / Generator
« on: December 23, 2017, 02:18:53 PM »
Hi All,

Beer-K0in did an amazing generator for linux that worked on the old 3.3.2 version.  With all the recent updates I appreciate a lot has changed but is there a guide to follow to install and setup version 6 or 7 on a digital ocean box?  I would rather do that than the Amazon guide I found on here.

I have an issue where when I leave the bot and I stop them all, I can no longer then run the "ginit" or "gstart" command from my folder.  I have to run the Curl command to do the full install again and then the commands work again.

Code: [Select]
No command 'gstart' found, did you mean:
 Command 'rstart' from package 'x11-session-utils' (main)
 Command 'gkstart' from package 'gnukhata-core-engine' (universe)
 Command 'start' from package 'upstart' (main)
 Command 'kstart' from package 'kde-runtime' (universe)
 Command 'gstat' from package 'ganglia-monitor' (universe)

How would I be able to check and ensure the scripts are installed and loading correctly.

Seems like it might be buggy when moving from the old 3.3.2 file is that correct?

Also to upgrade gunbot, do you simply stop the old bot, overwrite the old gunbot folder with the newly donwloaded one and then restart the bot?

I keep getting the nasty error where the root user unattaches and i'm trying to use the gunbot proxy as I had a lot of issues with 422s.  Is there any way to secure the root user in a better way to try to prevent that?

Also is there any way you can add a helpful section to your initial post about installing gproxy ( as it really helps when you are running multiple pairs.  Currently i'm at a point where I have the bot working on it's own and the proxy working but then at some point the whole setup crashes and I have to restart leading to errors.  Any idea why?

Beginners & Help / Re: GUNBOT V3 FOR MAC OS X
« on: July 12, 2017, 12:46:06 PM »
I'm getting a very weird Error message that contains data that I didn't personally add.  This error occurs when I run glog and only on a single pair BTC_ETH which is in the "sweet" state

I don't know why or who this line is?
Code: [Select]
Here's the process as shown by pm2

Code: [Select]
Describing process with id 5 - name BTC_ETH_P
│ status            │ online                                                    │
│ name              │ BTC_ETH_P                                                 │
│ restarts          │ 0                                                         │
│ uptime            │ 87s                                                       │
│ script path       │ /opt/GUNBOT_v3.3.2_Poloniex_Bittrex_Patch/gunthy-linuxx64 │
│ script args       │ BTC_ETH poloniex                                          │
│ error log path    │ /root/.pm2/logs/BTC-ETH-P-error-5.log                     │
│ out log path      │ /root/.pm2/logs/BTC-ETH-P-out-5.log                       │
│ pid path          │ /root/.pm2/pids/                           │
│ interpreter       │ none                                                      │
│ interpreter args  │ N/A                                                       │
│ script id         │ 5                                                         │
│ exec cwd          │ /opt/GUNBOT_v3.3.2_Poloniex_Bittrex_Patch                 │
│ exec mode         │ fork_mode                                                 │
│ node.js version   │ N/A                                                       │
│ watch & reload    │ ✘                                                         │
│ unstable restarts │ 0                                                         │
│ created at        │ 2017-07-12T11:37:28.812Z

Here is the error with Glog

Code: [Select]
5|BTC_ETH_ | Unhandled rejection Error: Bad server answer
5|BTC_ETH_ |     at Object.console./snapshot/Users/Enrico/Desktop/xBot_v2.9.3/poloniex.js.module.exports.Market.getLastBuyRate.poloniex.returnTradeHistory [as callback] (evalmachine.<anonymous>:0:0)
5|BTC_ETH_ |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:2243:31
5|BTC_ETH_ |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:906:16
5|BTC_ETH_ |     at Request._callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/plnx/lib/index.js:138:7)
5|BTC_ETH_ |     at Request.self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
5|BTC_ETH_ |     at emitTwo (events.js:106:13)
5|BTC_ETH_ |     at Request.emit (events.js:192:7)
5|BTC_ETH_ |     at Request.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1171:10)
5|BTC_ETH_ |     at emitOne (events.js:96:13)
5|BTC_ETH_ |     at Request.emit (events.js:189:7)
5|BTC_ETH_ |     at IncomingMessage.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1091:12)
5|BTC_ETH_ |     at Object.onceWrapper (events.js:291:19)
5|BTC_ETH_ |     at emitNone (events.js:91:20)
5|BTC_ETH_ |     at IncomingMessage.emit (events.js:186:7)
5|BTC_ETH_ |     at endReadableNT (_stream_readable.js:974:12)
5|BTC_ETH_ |     at _combinedTickCallback (internal/process/next_tick.js:74:11)
5|BTC_ETH_ |     at process._tickCallback (internal/process/next_tick.js:98:9)

Waht does the phrase *NO LP FOUND* mean within the bot?

So i've been looking into the latest config which is helpfully labelled in the 3.3.2  version.   You can read Gunthy's post here -

What's not clear is exactly how the different buy or sell strategies actually work.  These are

BB (Bolinger Band)

You can then set these methods for both Buy or Sell.  Meaning in total you have 4x4 possibilities or 16.  The most common and recommended in BB and BB.  And this is what I have been using.

So from my understanding this is what I know

BB = Bolinger Band.  You set a % which is the size of the % underneath the top or bottom of the bollinger band.  The algorithm will buy at your chosen size if on an downtick it swings past the BUY BB % and then it will sell on an uptick that swings past the SELL BB%.  This makes sense, buy on the down swing, sell on the upswing.

Now I really don't understand how the other 3 work, could someone help explain with a little more clarity or example how the algorithms work based on Gunthys Description below.

Pure STEPGAIN: BUY_STRATEGY: 'STEPGAIN' and SELL_STRATEGY: 'STEPGAIN' in your config files, will give you the power to explore up and down until the bot finds the best price to buy and the highest price to sell (supergun trend watchdog applies with improved algo). All of this on all 3 markets: Bittrex, Kraken, Poloniex. We have now 2 levels of BUY and 2 levels of SELL only in config files, since the third has not been really useful. Set BUYLVL and SELLLVL to the right level you want to use. Example: if you have BUYLVL1 to 3 and BUYLVL2 to 5, set BUYLVL to 2 if you want to explore from to 5%to infinite, or set BUYLVL to 1 if you want to explore from 3% to infinite.

Pure GAIN: BUY_STRATEGY: 'GAIN' and SELL_STRATEGY: 'GAIN' in yoru config files will give you the power to explore from BUY_LEVEL % to infinite and from GAIN % to infinite. For example: if you set BUY_LEVEL to 3 and GAIN to 5, it will buy at 3% or more (supergun trend watchdog applies) and it will sell at 5% or more (again supergun trend watchdog applies). All of this in all markets: Bittrex, Kraken, Poloniex.

Pure PINGPONG: set a price to buy and a price to sell in PINGPONG_BUY and PINGPONG_SELL config values and your bot will continuosly buy at PINGPONG_BUY price or lower and sell at PINGPONG_SELL or higher. Supergun trend watchdog applies and this strategy is available in all markets: Bittrex, Kraken, Poloniex

This is the current code for the config for reference and so you can see where and what option you might set for each idea.

Code: [Select]
var config = {



MAX_LATEST_PRICES: 200,// limit of latest prices to analyze to determine if price is growing or falling
MAX_LATEST_DIRECTIONS:30,// limit of latest  price directions ,used in supergun detection
MAX_LAST_ORDERS:5,  // keeping last orders bought
PERIOD: 15,   // candlestick period

SAVEFILE_SUFFIX: '-save.json',
DEFAULT_CURRENCY_PAIR:"BTC_ETH",   //  single pair format for all markets !
BUYLVL1: 3, //buy when the price drops by this percentual or lower if BUYLVL is 1
BUYLVL2: 12, //buy when the price drops by this percentual or lower if BUYLVL is 2
SELLLVL1: 2, //sell when the price drops by this percentual or higher is SELLLVL is 1
SELLLVL2: 70, //sell when the price drops by this percentual or higher is SELLLVL is 2
BUYLVL: 2, //possible values 1 and 2 (if you want to buy at level 1 or level 2)
SELLLVL: 2, //possible values 1 and 2 (if you want to sell at level 1 or level 2)
BUY_STRATEGY: "BB", // accepted values BB or STEPGAIN or GAIN or PINGPONG
SELL_STRATEGY: "GAIN", // accepted values BB or STEPGAIN or GAIN or PINGPONG
LOW_BB: 5, //buy when the price is higher than low BB by this percentual
HIGH_BB: 5, //sell when the price is lower than high BB by this percentual
PINGPONG_BUY: 0.001, //price to buy (or lower) in the ping pong strategy
PINGPONG_SELL: 0.002, //price to sell (or higher) in the ping pong strategy
BUY_LEVEL: 0.1, // If GAIN buy strategy is used, buy at this percentual below lower ema value
GAIN: 0.1, // If GAIN sell strategy is used, sell at this percentual above bought price
BTC_TRADING_LIMIT: 0.01,// max amount of BTC balance to use for each pair
SECURITY_MARGIN: 60, // sell all balance if currency decreases x% after you bought it
MIN_VOLUME_TO_BUY: 0.0005,  // bitrex min volume


BITTREX_PRICE_METHOD:'ohlc',// ohlc OR vwa  "price to buy" definition method
BITTREX_VWA_1_INTERVAL: 10,// weighted average interval in minutes
BITTREX_VWA_2_INTERVAL: 120,// weighted average interval in minutes



KRAKEN_PRICE_METHOD:'vwa',// ohlc OR vwa  "price to buy" definition method
KRAKEN_VWA_1_INTERVAL: 1,// weighted average interval in minutes
KRAKEN_VWA_2_INTERVAL: 15,// weighted average interval in minutes


POLONIEX_PRICE_METHOD:'vwa',// ohlc OR vwa  "price to buy" definition method
POLONIEX_VWA_1_INTERVAL: 0.02,// weighted average interval in hours
POLONIEX_VWA_2_INTERVAL: 0.04,// weighted average interval in hours

BOT_SLEEP_DELAY:(1000)*10,// bot cycle delay (koef*sec)
BOT_MAX_LIFETIME:999999999,// overall bot lifetime(koef*min),
BOT_ON_FAIL_DELAY:(1000)*5, // bot repeat cycle delay if previous cycle failed  (koef*sec)
ALERT_ON_NO_FUNDS:false,  // email on insufficcient funds
SMTP_PASSWORD: '**********',
SMTP: true,

MAX_LATEST_PRICES_SHOWN: 0, // limit of latest prices to show in console.log
SHOW_LASTEST_DIRECTIONS:false,  // show chart in console

//   OTHER (might be deprecated/not in use)
BTC_BALANCE: 2// btc balance for test purposes,
module.exports = config;

Technical Support & Development / Re: Bugs/Issues tracker v3.3.2
« on: June 29, 2017, 10:06:01 AM »
Is there a potential in a future version to add the same GUI to the ubuntu / *nix version that could run on gnome or via VNC.  I'd like to be able to setup and manage via a gui as i'm having a lot of issues with the scripts on my unix box.

Tried running this on a fresh instance and there seems to be an issue in the script itself?  I get this error during fresh install on Digital Ocean

                    GUNBOT 3.3.2 SETUP started

                This will take a few seconds


 (1/6) Update the base system
 (2/6) Install nodejs 6.x
 (3/6) Install tools
bash: line 40:  3281 Killed                  npm install -g pm2 yo@1.8.5 generator-gunbot gunbot-monitor > /dev/null 2>&1
 (4/6) Install GUNBOT
 (5/6) Add GUNBOT aliases
 (6/6) Init generator


The script seems to be ok, but i've messed up my permissions on my npm install and it's now not working correctly.

Can anyone give me a link on how to either uninstall and then reinstall npm to correct the permissions?

Pages: [1]