Messages

1

Technical Support & Development / Re: Feature request: Limit the risk of monster bags by double up

« on: September 04, 2017, 08:51:23 AM »

+1

2

Technical Support & Development / Re: Feature request: Multiple API keys

« on: August 21, 2017, 04:14:39 AM »

1. This is not a must have feature. It can very well go to the very bottom of the features-to-be-implemented list, and be forgotten there

2.

Why? this is soooo pointless, you can already do this yourself

The command line argument is sooooo irrelevant... Think about it: Running 1 instance, instead of running 3 instances... what is better?

3

Technical Support & Development / Re: Feature request: Multiple API keys

« on: August 20, 2017, 07:57:08 PM »

Sorry for the delay in replying; I was on vacation 

I like to group the coins I'm trading. Let's say the groups are
1. High volume coins
2. Low volume coins
3. Newly introduced coins

To trade them, I use 3 different accounts, and each group/account has a different strategy, so I can easily change the strategy of a group, or move coins in/out of a group.

The benefit is just ease of use, and not having to run 3 instances of GUNBOT

4

Technical Support & Development / Re: Bugs/Issues tracker v4.0.4

« on: August 18, 2017, 07:28:41 AM »

4.0.4 sold with loss (a lot of it) -- See attached screen capture

All previous versions were just trying to average down, without selling with loss

I gave this a second thought, and GUNBOT is probably doing what it's supposed to do:
I had set the STOP_LIMIT to 80 (I thought I had set it to 99, in order to only sell at loss when the coin has "died"), and it actually sold when my loss exceeded 80%.

Can someone confirm that it actually did what it was instructed to do, and that this was not a bug?

5

Technical Support & Development / Re: Bugs/Issues tracker v4.0.4

« on: August 17, 2017, 07:26:36 PM »

4.0.4 sold with loss (a lot of it) -- See attached screen capture

All previous versions were just trying to average down, without selling with loss

6

Technical Support & Development / Feature request: Multiple API keys

« on: August 11, 2017, 04:43:22 PM »

It would be nice to be able to use multiple keys per exchange, as in the example below, in order to avoid running multiple instances of GUNBOT.
This way we can have all the coins in one configuration, use one account for de-bagging, another for high volume coins, a third one for low volume ones, etc., manage all of them in one configuration, and move them around as needed, but still keep separate profiles/accounts with different targets and trade scenarios.

 "poloniex-bags": {
                        "exchange": "poloniex",
                        "key": "KEY 1",
                        "secret": ""
                },
 "poloniex-high-vol": {
                        "exchange": "poloniex",
                        "key": "KEY 2",
                        "secret": ""
                },
 "poloniex-low-vol": {
                        "exchange": "poloniex",
                        "key": "KEY 3",
                        "secret": ""
                },

7

Technical Support & Development / Websockets API

« on: August 02, 2017, 07:51:20 AM »

@Gunthar
Do you have an ETA?

8

General Discussion / Re: Release Candidate v3.3.3 - Poloniex/Bittrex - All OS - Code name: "Autopilot"

« on: July 26, 2017, 01:56:04 PM »

<snip />

can i change this figure when doing normal trading (no bag)? or is that on purpose?

also now it's always the taker not maker of orders which means the fee is higher. how to change that?

Gunthar has spent a lot of time explaining every setting, and he has also written (at least) one topic on how he runs the bot.
The answers to your questions are in there.

If you don't have the time to read, there are members of this forum that provide configuration services. See 'Services & Third Party plugins

9

General Discussion / Re: Release Candidate v3.3.3 - Poloniex/Bittrex - All OS - Code name: "Autopilot"

« on: July 26, 2017, 08:29:52 AM »

This looks like a major release!  Wow!

But can someone post or attach a simple example config file with a few pairs in it so us noobs can figure out what it's supposed to look like (take out your keys of course).

Great job to the devs!!  Thank you!

Make sure you match opening and closing curly braces.
Every group of similar sections or fields is separated by a comma. The last one (section or field) does not have a comma after it...
The indentation helps you visually understand the grouping of sections and fields

{
  "pairs": {
    "poloniex": {
      "BTC_BTS": {
        "strategy": "bb",
        "override": {}
      },  // <-- comma after each similar section, i.e. what is enclosed in curly braces
      "BTC_XEM": {
        "strategy": "bb",
        "override": {}
      },  // <-- comma after each similar section, i.e. what is enclosed in curly braces
      "BTC_BURST": {
        "strategy": "bb",  // <-- comma btween fields
        "override": {}   // <-- NO comma as it is the last field before the closing curly brace
      }   // <-- NO comma after final secction
    }
  }
  "exchanges": {
    "poloniex": {
      "key": "ABC",
      "secret":"DEF"
    },
    "kraken": {
      "key": "",
      "secret":""
    }
  },
  "bot": {
    "period_storage_ticker": 300,
    "interval_ticker_update": 10000,
    "timeout_buy": 120,
    "timeout_sell": 60,
    "BTC_TRADING_LIMIT": 0.05,
    "MIN_VOLUME_TO_BUY": 0.005,
    "WATCH_MODE": false
  },
  "strategies": {
    "bb": {
      "PERIOD": 15,
      "BUY_LEVEL": 0.1,
      "GAIN": 0.6,
      "HIGH_BB": 60,
      "LOW_BB": 40,
      "PANIC_SELL": false
    }
  }
}

10

General Discussion / Re: Release Candidate v3.3.3 - Poloniex/Bittrex - All OS - Code name: "Autopilot"

« on: July 26, 2017, 08:14:46 AM »

Are all the files of the previous releases needed, or can they be safely deleted?

I'm talking about all the
*-config.js
*-log.js
*-port.js
*-save.js
*-token.js
*-trades.js
*-worker.js

11

General Discussion / Re: Release Candidate v3.3.3 - Poloniex/Bittrex - All OS - Code name: "Autopilot"

« on: July 26, 2017, 06:28:43 AM »

Been running the new version for 9 hours, with the purpose of first get rid of my bags, and then re-start using it as expected.

Results/impressions so far:
1. Pretty fast
2. No errors
3. Very low CPU/Memory usage
4. Very aggressive, compared to what I was used to seeing... Now I see lots of Bought/Sold/Not enough BTC
5. Did not sell any of my bags yet, but I'm already making profit (some peanuts, due to my de-bagging settings) from other pairs

Feature request: An option in config.js to disable a pair, instead of having to remove the pair from the configuration file

All in all, great work!!!

12

General Discussion / Re: Release Candidate v3.3.3 - Poloniex/Bittrex - All OS - Code name: "Autopilot"

« on: July 25, 2017, 06:28:58 PM »

You just made me smile 
Thanks!

13

Technical Support & Development / Re: Linux Connection Throttler/SSL proxy for Poloniex

« on: June 25, 2017, 07:12:05 PM »

error

::::2017/06/25 16:59:10   Error Error: connect ECONNREFUSED 127.0.0.1:443

::::2017/06/25 16:59:11   Error Error: connect ECONNREFUSED 127.0.0.1:443

haproxy is doing what it's supposed to do: accepting 3 simultaneous connections and rejecting the rest (read the conf you just copied and pasted)

14

Beginners & Help / Re: Gunbot Monitor - Oversee all GUNBOTs in one screen

« on: June 24, 2017, 07:57:56 AM »

Getting this strange thing going on now with the monitor with nothing showing

Specify the path using -p, or start gmon from within the directory where the Gunbot files are

15

Technical Support & Development / Re: License Issue

« on: June 18, 2017, 04:59:25 PM »

I had the same issue.
My problem/solution was that a tab was inserted after the API key, so I just removed it. You cannot see it in the GUI, but if you place the cursor at the end of the API key, and press the left arrow on your keyboard, you can see that the cursor does not move.

Check the XXX-config.js file to see if there is any trailing whitespace in your API key.