Messages

1

General Discussion / performance of gunbot emotionless strategy in this bear market Mai - June 2018?

« on: June 30, 2018, 07:00:14 AM »

Mai 2018, June 2018... Strong bear market.

How's your performance been using gunbot emotionless strategy?

2

Beginners & Help / Can I buy / sell at fixed prices?

« on: December 20, 2017, 08:22:17 PM »

Can I configure the bot somehow to say buy a coin always at 5 USD and sell always at 6 USD?

3

Beginners & Help / Re: Generator-Gunbot - Setup GUNBOT v3.3.2 in less than 5 minutes (linux)

« on: June 10, 2017, 12:24:49 AM »

Either instructions on generator-gunbot script is missing.

sudo apt-get install curl

This was hard to find out since all script output is hidden as well, so the script lacks error handling as well.

Thank you for all your work!

4

Technical Support & Development / Re: Gunbot 3.2 config white space and comment fixes

« on: May 14, 2017, 05:00:29 AM »

U forget
MAX_LATEST_PRICES_TREND: 30

(Not my mistake. From https://github.com/GuntharDeNiro/BTCT/releases/tag/Core3.2 I copied the config below "Here are the values in config and a brief explanation:". And did whitespace / comment fixes only to keep it simple. You're right in so far that MAX_LATEST_PRICES_TREND is missing from the original config. But that's something only gunthar can fix. I intentionally did not make any other changes. Just wanted to get this small improvement in before perhaps suggesting something else small step by step.)

Thanks to both of you!

I am happy if I my post would lead to an improvement.

I like densmirnov's version even more than my own version. It also has MAX_LATEST_PRICES_TREND and looks really clean. Would be cool if gunthar would add this improved config in the next version.

5

Technical Support & Development / Gunbot 3.2 config white space and comment fixes

« on: May 12, 2017, 01:45:53 AM »

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.)

6

Technical Support & Development / feature request: reload config on SIGHUP / CONFIG_FS_WATCH:false

« on: May 02, 2017, 10:38:52 PM »

I am running many instances of gunbot to have gunbot work with many currency pairs. The config files are just copies with different names for different pairs.

When I change a value in all config files at once (using sed or so), I am running out of RAM on my VPS. This is because during automatic config reload by gunbot, it will require more RAM. This could get one or another gunbot killed by the kernel or wreck the whole system.

It is also very usual for a linux daemon to automatically reload its config if the config file changed on the disk. Perhaps I was just saving my temporary progress and did not want to apply that config yet. I understand that you implemented this to better suit Windows users.

It's not great, so I cannot test my changes locally using git and then git fetch the repository on the remote. I had to write a script that slowly copies and wasted one config after another.

Could you please kindly add the following config option as a new feature?

Code: [Select]

CONFIG_FS_WATCH:true, // When true (default), automatically reload config when config file was changed on disk.

And second, could you please make gunbot to reload it's config when it receives signal SIGHUP?

The way to send SIGHUP so the daemon reloads its config on linux is. Note: No, this does NOT kill the process.

Code: [Select]

kill -HUP <processID>

Since many might not know this... A few more examples on the usage of the kill command on linux.

To politely ask a process to properly shut down and terminate, one would use sigterm.

Code: [Select]

kill -sigterm <processID>

To immediately kill a process without giving it proper notice or any chance to properly shut down (useful in case the process did not shutdown using sigterm or hangs).

Code: [Select]

kill -sigkill <processID>

Could you pleases implement CONFIG_FS_WATCH:true/false and SIGHUP support?