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

Pages: 1 ... 4 5 [6] 7
101
Technical Support & Development / Re: GunBot 3.3 can't start a pair
« on: June 03, 2017, 01:12:35 PM »
Hello,

I'm running version 3.2 fine and wanted to try 3.3 on VPS. But whenever I start a pair I am getting following errors:

Code: [Select]
0|BTC_BURS | [ --2017/06/03 07:37:41--poloniex--BTC_BURST  --  Gunbot v3.2 cycle #2 --------------- ]
0|BTC_BURS | ::::: collecting market data...
0|BTC_BURS | Unhandled rejection Error: statusCode 422
0|BTC_BURS |     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)
0|BTC_BURS |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:2243:31
0|BTC_BURS |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:906:16
0|BTC_BURS |     at Request._callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/plnx/lib/index.js:134:7)
0|BTC_BURS |     at Request.self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
0|BTC_BURS |     at emitTwo (events.js:106:13)
0|BTC_BURS |     at Request.emit (events.js:192:7)
0|BTC_BURS |     at Request.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1171:10)
0|BTC_BURS |     at emitOne (events.js:96:13)
0|BTC_BURS |     at Request.emit (events.js:189:7)
0|BTC_BURS |     at IncomingMessage.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1091:12)
0|BTC_BURS |     at Object.onceWrapper (events.js:291:19)
0|BTC_BURS |     at emitNone (events.js:91:20)
0|BTC_BURS |     at IncomingMessage.emit (events.js:186:7)
0|BTC_BURS |     at endReadableNT (_stream_readable.js:974:12)
0|BTC_BURS |     at _combinedTickCallback (internal/process/next_tick.js:74:11)
0|BTC_BURS |     at process._tickCallback (internal/process/next_tick.js:98:9)
0|BTC_BURS | Unhandled rejection Error: statusCode 422
0|BTC_BURS |     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)
0|BTC_BURS |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:2243:31
0|BTC_BURS |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:906:16
0|BTC_BURS |     at Request._callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/plnx/lib/index.js:134:7)
0|BTC_BURS |     at Request.self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
0|BTC_BURS |     at emitTwo (events.js:106:13)
0|BTC_BURS |     at Request.emit (events.js:192:7)
0|BTC_BURS |     at Request.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1171:10)
0|BTC_BURS |     at emitOne (events.js:96:13)
0|BTC_BURS |     at Request.emit (events.js:189:7)
0|BTC_BURS |     at IncomingMessage.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1091:12)
0|BTC_BURS |     at Object.onceWrapper (events.js:291:19)
0|BTC_BURS |     at emitNone (events.js:91:20)
0|BTC_BURS |     at IncomingMessage.emit (events.js:186:7)
0|BTC_BURS |     at endReadableNT (_stream_readable.js:974:12)
0|BTC_BURS |     at _combinedTickCallback (internal/process/next_tick.js:74:11)
0|BTC_BURS |     at process._tickCallback (internal/process/next_tick.js:98:9)
0|BTC_BURS | ***************************************************
0|BTC_BURS | Low BB:0.00000000 - High BB:0.00000000
0|BTC_BURS | ***************************************************
0|BTC_BURS | BB price to sell 0.0000000 -- GAIN price to sell NaN
0|BTC_BURS | +
0|BTC_BURS | Unhandled rejection Error: statusCode 422
0|BTC_BURS |     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)
0|BTC_BURS |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:2243:31
0|BTC_BURS |     at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:906:16
0|BTC_BURS |     at Request._callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/plnx/lib/index.js:134:7)
0|BTC_BURS |     at Request.self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
0|BTC_BURS |     at emitTwo (events.js:106:13)
0|BTC_BURS |     at Request.emit (events.js:192:7)
0|BTC_BURS |     at Request.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1171:10)
0|BTC_BURS |     at emitOne (events.js:96:13)
0|BTC_BURS |     at Request.emit (events.js:189:7)
0|BTC_BURS |     at IncomingMessage.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1091:12)
0|BTC_BURS |     at Object.onceWrapper (events.js:291:19)
0|BTC_BURS |     at emitNone (events.js:91:20)
0|BTC_BURS |     at IncomingMessage.emit (events.js:186:7)
0|BTC_BURS |     at endReadableNT (_stream_readable.js:974:12)
0|BTC_BURS |     at _combinedTickCallback (internal/process/next_tick.js:74:11)
0|BTC_BURS |     at process._tickCallback (internal/process/next_tick.js:98:9)
0|BTC_BURS | +
0|BTC_BURS | 2017/06/03 07:37:45 Error: statusCode 422
0|BTC_BURS | !!! Cycle 3 failed. Will repeat in 66s

Can anyone help me please?
Its just 422 error, just wait, bot handle w/ it.

102
I've updated the monitor
Version 0.0.25

Changelog

-    Default timing is 60s now.
-    Handle "EMFILE: too many open files, scandir".
-    Added profit behind the --profit (-P) flag.
-    Highlight 429 errors.



Update

Run
Code: [Select]
npm install -g gunbot-monitor to update/install it on your server.



Profit is back

You can activate the profit parsing again with the parameter '-P'.

Code: [Select]
gmon -P
THIS WILL SLOW DOWN YOUR SYSTEM. Please check your CPU load and increase the refresh time if the CPU load is to high, or do not activate the profit parsing.



Usage

All available options can be displayed with
Code: [Select]
gmon -h

Code: [Select]
  Usage: gmon [options]

  Options:

    -h, --help               output usage information
    -v, --version            output the version number
    -p, --path <path>        Path to the GUNBOT folder
    -c, --compact            Do not draw row lines
    -s, --small              Reduce columns for small screens
    -r, --refresh <seconds>  Seconds between table refresh. Min = 10, max = 600
    -P, --profit             Use to activate the parsing of the profit. I WILL SLOW DOWN YOUR SYSTEM!

You can also combine the options like:

Code: [Select]
gmon -csPr 120 -p /path/to/GB/
BK

All is good with last version. thx!

103
Technical Support & Development / Re: Linux swap file
« on: June 02, 2017, 09:25:00 AM »
U can it!
I did it and run 62 pairs all is good.
https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-16-04

Ok, so I have allocatd about 7GB swap (!!)....  DigitalOcean HDs are SSD so can be reasonably confident of performance.

My mem usage is at 94% used with 17 pairs but i would like to add more without upsizing....will it now blow up if I add more?   Does yours just sit pegged 100% mem usage constantly?

As i sad all works fine, 51 pairs runing in DO with 6G swap.

104
Technical Support & Development / Re: Linux swap file
« on: June 02, 2017, 12:21:58 AM »
Is there any way I can bolster my Digital Ocean 2GB droplet with liberal use of swap file?

I have 17 pairs running (2 stopped) which takes me up to 85% usage.....had some issues with the 1GB droplet with stability where all my pm2 sessions died....would be very keen to ensure no repeat of that!

U can it!
I did it and run 62 pairs all is good.
https://www.digitalocean.com/community/tutorials/how-to-add-swap-space-on-ubuntu-16-04

105
How to run it for 3.3 version?

106
General Discussion / Re: Poloniex vs Bittrex
« on: May 25, 2017, 12:58:53 PM »
Hi, I only tried bot on Poloniex, got Bittrex licence, just wonder what works better for you guys?

Polo or bittrex?

Thx
Bittrix, in my opinion, gives fewer errors then fu** polo =)

107
pls help, I'm losing a lot of trades... :(


Code: [Select]
var config = {
//  DEBUG
DEBUG_LOG:false,
I_REALLY_WANT_IT:false,
BUY_SMALL_PORTION:1,
INSUFFICIENT_FUNDS_ON_SELL_FIX: 0.0005,
INSUFFICIENT_FUNDS_ON_BUY_FIX: 0.0005,


//-----------------------------------------------
//   STARTUP OPTIONS
//-----------------------------------------------

SELL_ON_START:false,
CANCEL_SELL_ORDERS_ON_START:false,
CANCEL_BUY_ORDERS_ON_START:false,
CANCEL_OPEN_ORDERS_ON_START:false,



MAX_LATEST_PRICES: 300,// limit of latest prices to analyze to determine if price is growing or falling
MAX_LATEST_PRICES_TREND: 30,// 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',
//-----------------------------------------------
//  PRIMARY SETTINGS
//-----------------------------------------------
DEFAULT_MARKET_NAME:"poloniex",
DEFAULT_CURRENCY_PAIR:"BTC_ETH",   //  single pair format for all markets !
BUYLVL1: 3,
BUYLVL2: 12,
SELLLVL1: 2,
SELLLVL2: 70,
BUYLVL: 2,
SELLLVL: 2,
BUY_STRATEGY: "STEPGAIN", // accepted values BB or STEPGAIN or GAIN or PINGPONG
SELL_STRATEGY: "STEPGAIN", // accepted values BB or STEPGAIN or GAIN or PINGPONG
LOW_BB: 25,
HIGH_BB: 30,
PINGPONG_BUY: 0.001,
PINGPONG_SELL: 0.002,
BUY_LEVEL: 3, // If GAIN buy strategy is used, buy at this percentual below lower ema value
GAIN: 2, // If GAIN sell strategy is used, sell at this percentual above bought price
BTC_TRADING_LIMIT: 0.07,// 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
BITTREX_KEY:'',
BITTREX_SECRET:'',

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
KRAKEN_ASSET_PAIR:'XETHXXBT',

KRAKEN_KEY: '',
KRAKEN_SECRET: '',


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
POLONIEX_KEY: '***',
POLONIEX_SECRET: '***',


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 TIMINGS
//-----------------------------------------------
API_CALLS_DELAY:777,
BOT_SLEEP_DELAY:(1000)*23,// bot cycle delay (koef*sec)
BOT_MAX_LIFETIME:999999999,// overall bot lifetime(koef*min),
BOT_ON_FAIL_DELAY:(1000)*60, // bot repeat cycle delay if previous cycle failed  (koef*sec)
//-----------------------------------------------
// EMAIL
//-----------------------------------------------
ALERT_ON_NO_FUNDS:false,  // email on insufficcient funds
SMTP_EMAIL: '%40@gmail.com',
ALERT_EMAIL:'********',
SMTP_PASSWORD: '**********',
SMTP: true,
SMTP_PROTOCOL: 'SMTPS',
SMTP_HOST: 'smtp.gmail.com',

//-----------------------------------------------
//  OUTPUT
//-----------------------------------------------
MAX_LATEST_PRICES_SHOWN: 0, // limit of latest prices to show in console.log
SHOW_LASTEST_DIRECTIONS:false,  // show chart in console
MAX_LATEST_DIRECTIONS_SHOWN:0, // chart height
LASTEST_DIRECTIONS_LIST_WIDTH:0, // chart width

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



Change your SELLLVL2: 70 to 2.






108
does anyone have an example bat file we can use for multiple coins starting with 3.2 until the GUI comes out?
all the same.


statrt_All.bat
Code: [Select]

@echo off
start /min BTC_BLK.bat ^& exit
timeout 5
start /min BTC_BTCD.bat ^& exit
timeout 5
start /min BTC_EMC2.bat ^& exit
timeout 5/
...

start /min BTC_XRP.bat ^& exit
exit


Each pair BTC_XXX.bat for poloniex:
Code: [Select]
@echo off
TITLE strateg_BTC_XXX
gunthy.exe BTC_XXX poloniex

109
Technical Support & Development / Re: issue with start button
« on: May 15, 2017, 07:13:12 PM »
Install nodeJS or use 3.2 version with last patch

110
Technical Support & Development / Re: Gunbot Amazon VPS
« on: May 13, 2017, 04:32:05 PM »
Hello,

I downloaded the Gunbot on Amazon VPS and patch it but when I try to open the .exe is not starting...
Am I missing something to have it running?Or I need for the version with GUI?
Thank you!
In russian, but anyway.
[youtube]https://youtu.be/ALTYfDVISfg[/youtube]

111
For win we need something like Cryptowally's gunbot linux console:



 But on windows with couples of pairs, its will be good, coz hard watch for 8~16 pairs in cmd, they occupy the whole screen:


And, of course, we want a color console. ::) :)

112
Original:
https://github.com/GuntharDeNiro/BTCT/releases/tag/Core3.2

Minor white space and comment fixes. Tried to be more consistent about when to use white spaces and when not. Changes:
- generally use a white space after colon
- generally use a white space before // comments
- no duplicate white spaces
- no trailing spaces

Code: [Select]
var config = {
//-----------------------------------------------
//   DEBUG
//-----------------------------------------------
DEBUG_LOG: true,
I_REALLY_WANT_IT: false,
BUY_SMALL_PORTION: 1,
INSUFFICIENT_FUNDS_ON_SELL_FIX: 0.0005,
INSUFFICIENT_FUNDS_ON_BUY_FIX: 0.0005,

//-----------------------------------------------
//   STARTUP OPTIONS
//-----------------------------------------------
SELL_ON_START: false,
CANCEL_SELL_ORDERS_ON_START: false,
CANCEL_BUY_ORDERS_ON_START: false,
CANCEL_OPEN_ORDERS_ON_START: false,



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',

//-----------------------------------------------
//   PRIMARY SETTINGS
//-----------------------------------------------
DEFAULT_MARKET_NAME: "poloniex",
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
//-----------------------------------------------
BITTREX_KEY: '',
BITTREX_SECRET: '',

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
//-----------------------------------------------
KRAKEN_ASSET_PAIR: 'XETHXXBT',

KRAKEN_KEY: '',
KRAKEN_SECRET: '',

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
//-----------------------------------------------
POLONIEX_KEY: '',
POLONIEX_SECRET: '',

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 TIMINGS
//-----------------------------------------------
API_CALLS_DELAY: 777,
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)

//-----------------------------------------------
//   EMAIL
//-----------------------------------------------
ALERT_ON_NO_FUNDS: false, // email on insufficient funds
SMTP_EMAIL: '%40@gmail.com',
ALERT_EMAIL: '********',
SMTP_PASSWORD: '**********',
SMTP: true,
SMTP_PROTOCOL: 'SMTPS',
SMTP_HOST: 'smtp.gmail.com',

//-----------------------------------------------
//   OUTPUT
//-----------------------------------------------
MAX_LATEST_PRICES_SHOWN: 0, // limit of latest prices to show in console.log
SHOW_LASTEST_DIRECTIONS: false, // show chart in console
MAX_LATEST_DIRECTIONS_SHOWN: 0, // chart height
LASTEST_DIRECTIONS_LIST_WIDTH: 0, // chart width

//-----------------------------------------------
//   OTHER (might be deprecated/not in use)
//-----------------------------------------------
BTC_BALANCE: 2 // btc balance for test purposes,
};

module.exports = config;

Please take that version.

(It would be helpful to have the releases available in git. I am not proposing to publish the full cleartext gunbot source code. But the releases and config files would be useful to have in git to download releases and to send git pull requests for minor config fixes.)
U forget
MAX_LATEST_PRICES_TREND: 30

113
Thanks to both of you!

114
Technical Support & Development / Re: Bugs/Issues tracker v3.2
« on: May 12, 2017, 02:34:08 PM »
Double buy on
Code: [Select]
BUY_STRATEGY: "BB",
SELL_STRATEGY: "GAIN",
BTC_TRADING_LIMIT: 0.01




115
Found that to start a pair, it is desirable to first clean the entire file ALLPAIRS-params.js

116
General Discussion / Re: About to buy gunbot!!
« on: May 11, 2017, 09:02:48 PM »
What is the best strategy to use on Polo for someone that wants to risk .25 btc starting?  Any help would be appreciated and tips! thank you
I'm started from 0.05 =) Now its use 0.4 on 1 acc and 0.3 on second.
It all depends on experience.

118
hi

little improvement and compatibility with 3.x release :


change the grep command line to grep -qw (because pair like STR won't launch if pair STRAT is already running so the -w flag force a whole word match)

Code: [Select]
  screen -S $_namef -p 0 -X exec node $botfolder/index $_namef poloniex
Code: [Select]
screen -S $_namef -p 0 -X exec node $botfolder/stepgain $_namef poloniex
In my case.

119
Were the attached.zip?

120
Will it work if I have 2 folders of bot,
1 - I run mannualy and to 1 polo acc.
2 - I run with your start.sh to 2 polo acc?
Or I need to run only one of bot copy?

Pages: 1 ... 4 5 [6] 7