Messages

1

Technical Support & Development / Re: GB 20.7.5 and Kraken

« on: December 09, 2020, 08:40:34 PM »

Ok, I download v20.7.1 from Telegram, applied patch v20.7.5 and run my config. Result is not better (activated DEBUG to see if not missing important messages) :

Code: [Select]

Loading exchange - kraken
Loading data....
GBP-BTC@kraken trying to load state for GBP-BTC@kraken
GBP-BTC@kraken starting cl
GBP-BTC@kraken states loaded
GBP-BTC@kraken Awesome level 1 is working!!!
GBP-BTC@kraken checking balances
GBP-BTC@kraken checking positions
GBP-BTC@kraken calculating indicators
GBP-BTC@kraken Awesome level 3 is working!!!
GBP-BTC@kraken we got ema
GBP-BTC@kraken Awesome level 4 is working!!!
GBP-BTC@kraken we got bb
GBP-BTC@kraken we got rsi
GBP-BTC@kraken we got pair mfi
GBP-BTC@kraken we got XTrend
GBP-BTC@kraken we got smacross
GBP-BTC@kraken we got macd
GBP-BTC@kraken we got stoch
GBP-BTC@kraken Stoch buy: false
GBP-BTC@kraken Stoch sell: false
GBP-BTC@kraken we got stochRSI
GBP-BTC@kraken Stoch rsi: 0.12950832653222463
GBP-BTC@kraken we got atr
GBP-BTC@kraken we got ichimoku
GBP-BTC@kraken bull/bearish process
GBP-BTC@kraken checking history
GBP-BTC@kraken we got mfi btcusd
GBP-BTC@kraken we got forecast
GBP-BTC@kraken checking open orders
GBP-BTC@kraken canceling open orders
GBP-BTC@kraken starting pairs
GBP-BTC@kraken starting get prices loop
GBP-BTC@kraken calculated entry points

GB_20.7.5 GBP-BTC@kraken Round #1 2020/12/09 21:37:47
GBP-BTC@kraken skipped TakeProfit
GBP-BTC@kraken defined grid
GBP-BTC@kraken defined abp and available funds
GBP-BTC@kraken checked telegram alerts
GBP-BTC@kraken pre-grid
GBP-BTC@kraken end of grid parsing
GBP-BTC@kraken start strategies attempts
GBP-BTC@kraken refusing tests
GBP-BTC@kraken skipping smacross
GBP-BTC@kraken refusing MACD
GBP-BTC@kraken quote amount calculated
GBP-BTC@kraken keepsell
Error: Error: General:Invalid arguments:volume
    at errorHandler (/snapshot/test/Desktop/node14/ctx/js/kraken.js)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

┌───────────────────┬────┐
│ ɢՍΠßØŦ RT Edition │    │
├───────────────────┼────┤
│ Callbacks         │ {} │
└───────────────────┴────┘


2

Technical Support & Development / Re: GB 20.7.5 and Kraken

« on: December 09, 2020, 08:20:11 PM »

If only package got a numbering scheme on them....
Do you have a method to check that ?
My node is the old one (v10.19.0), I dont see any prerequisite for Gunbot installation (on Linux).
Or maybe Gunbot include his own version of Node.js ? But how to check it ?

3

Technical Support & Development / GB 20.7.5 and Kraken

« on: December 07, 2020, 02:53:24 PM »

Hi,

I get this error since GB 20.xxx series and still no hope to get it fixed.
Exchange : Kraken

Code: [Select]

GB_20.7.5 GBP-ETH@kraken Round #103045 2020/12/07 15:40:46
Error: Error: General:Invalid arguments:volume
    at errorHandler (/snapshot/test/Desktop/node14/ctx/js/kraken.js)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

┌───────────────────┬────┐
│ ɢՍÑɮØŁ RT Edition │    │
├───────────────────┼────┤
│ Callbacks         │ {} │
└───────────────────┴────┘

GB_20.7.5 GBP-BTC@kraken Round #103171 2020/12/07 15:41:05
Error: Error: General:Invalid arguments:volume
    at errorHandler (/snapshot/test/Desktop/node14/ctx/js/kraken.js)
    at processTicksAndRejections (internal/process/task_queues.js:97:5)

┌───────────────────┬────┐
│ ɢƱҊɃѺͳ RT Edition │    │
├───────────────────┼────┤
│ Callbacks         │ {} │
└───────────────────┴────┘
Does not work on any pairs I could try.

4

Technical Support & Development / Gunbot v20.4.5

« on: October 26, 2020, 08:06:03 PM »

Fresh install, 1st run on Linux :

Code: [Select]

root@gunbot-1:~/gunbot# ./gunthy-linux
Loading config...
{ Error: ENOENT: no such file or directory, open '/root/gunbot/logs/autoconfig-log.txt'
  errno: -2,
  code: 'ENOENT',
  syscall: 'open',
  path: '/root/gunbot/logs/autoconfig-log.txt' } 'Uncaught Exception thrown'
Loading config...

Then work normally. The autoconfig-log.txt is created. That message is just informative but maybe not necessary to be show.

5

General Discussion / TRADING_LIMIT

« on: October 23, 2020, 06:43:32 PM »

Hi,

I have a problem with the TRADING_LIMIT parameter on strategy.
Because I want to catch the best opportunities, I set up that parameter to 10 (base currency, and it's not BTC ). But then, most buy orders are just 10 currency and never go over. On very rare occasion, I see a 2nd buy with (again) 10 currency.

What I want is to buy a minimum of 10 base currency but not limiting to 10 (15, 30, 1000 if that's possible). How to achieve this goal ?

6

General Discussion / Re: Who is broken ? Binance ? Kraken ? or Gunbot ?

« on: October 23, 2020, 06:36:19 PM »

Thanks, problem is fixed, a script that generate my config files changed the decimal point from one place to the left...

7

General Discussion / Re: Who is broken ? Binance ? Kraken ? or Gunbot ?

« on: October 17, 2020, 08:16:01 PM »

Hi,

1- I have still some base coins on both Gunbot
2- That's the problem I think because no orders since 1st Septembre, but all the markets are active. BTW, that stop happened on both Gunbot, nearly at the same time (30 August / 1st September) and really suddenly; I have reset to standard "emotionless" since 15 days and still no orders.
3- Gunbot is missing some "paper trade" to validate a config or test if everything is all right. But I have no error on logs and nothing changed during that period.

Gunbot-1 (Kraken) is 19.1.5 and Gunbot-2 (Binance) is standard 18.8.8

Oh, and Gunbot is missing some way to limit the size of logs. Not very important for me (I'm under Linux and using log rotate) but it's annoying for others.

8

General Discussion / Who is broken ? Binance ? Kraken ? or Gunbot ?

« on: October 06, 2020, 07:27:47 AM »

Hi,

Long time user of Gunbot (and not really satisfied but that's another topic). Let's see what make me write this message :
Binance : 4 pairs, last transaction 08/30/2020 !
Kraken : 2 pairs, last transaction 01/09/2020 ! 50 transactions during August

Both exchange have not generated any trades since a month or more. I reboot every 2 days the VM hosting the bot to be safe. I've searched any reasons why the bot is not working but everyting is ok, still receiving tickers, no timeout. Just stopped working nearly the same day, both of them. Network is perfect too.

Any idea ?

9

Technical Support & Development / Re: Gunbot licence API

« on: April 23, 2020, 07:10:53 PM »

Fixed.

Thanks Aitor

10

Technical Support & Development / Re: Gunbot licence API

« on: April 23, 2020, 10:30:41 AM »

Excerpt form my config file :

Code: [Select]

"exchanges": {
        "kraken": {
            "key": "<Kraken API Key>",
            "secret": "<Kraken Private Key>",
            "masterkey": "<Kraken API Key>",
            "mastersecret": "<Kraken Private Key>",
            "type": "kraken",
            "delay": 10,
            "TRADING_FEES": "0.25",
            "HUSD": "",
            "BTC": "",
            "USDT": "",
            "USDC": "",
            "USD": "",
            "EUR": "",
            "GBP": "",
            "NZDT": "",
            "LTC": "",
            "ETH": "",
            "XMR": "",
            "DOGE": "",
            "BNB": "",
            "HT": "",
            "KCS": "",
            "filteredBase": [],
            "filteredQuote": [],
            "filteredPair": [],
            "includeCoins": [],
            "autoPairs": [],
            "tick_time": false,
            "tick_interval": 20
        }
    },
Im' not sure about the Delay parameter or if I should put something for Nonce on Kraken.

11

Technical Support & Development / Re: Gunbot licence API

« on: April 23, 2020, 10:21:49 AM »

Ok, now I think I have the good API but Kraken refuse to work :

Code: [Select]

Loading config...
   info  - socket.io started
GUI Server Deployed: http://localhost:5000

Your Gunthy token balance is: 1000 in wallet: 0x--------------------------------
Your license type is: V12 - STANDARD
Tradingview Plugin Access: false
Market Maker Plugin Access: false

Your user rank: 100

You can have up to 1 exchanges to run simultaneously

Your registered exchanges:
KRAKEN: ------------------------------------------

Loading exchange - kraken
Loading data....
{ ExchangeNotAvailable: kraken GET https://support.kraken.com/hc/en-us/articles/205893708-What-is-the-minimum-order-size- 403 Forbidden <!DOCTYPE html>
<html lang="en">
<head>
  <meta http-equiv="content-type" content="text/html; charset=UTF-8" />
  <title>Security check</title>
  <style>body{background:#03363d;color:#fff;font-family:system-ui,-apple-system,BlinkMacSystemFont,Segoe UI,Roboto,Oxygen-Sans,Ubuntu,Cantarell,Helvetica Neue,Arial,sans-serif;font-size:14px;font-style:normal;font-variant:normal;line-height:1.6;margin:1.6rem}h1{font-size:22px;line-height:1.4em;margin-top:0;padding-top:0}article,h1,p{margin:0}:link,:visited{color:#fff}.l-max-readable-width{max-width:40em}.l-centered{margin-left:auto;margin-right:auto}.l-v-padded{padding-bottom:.8rem}.l-top-padded,.l-v-padded{padding-top:.8rem}.l-padded-bottom{margin-bottom:.8rem}.err__page-heading{font-size:1rem;font-weight:400;padding-bottom:1.6rem}@media screen and (min-width:400px){.err__page-heading{font-size:1.6rem;font-weight:300}}@media screen and (min-width:520px){.err__page-heading{font-size:2rem}}.err__container{background:#fff;border-radius:.2rem;color:#012b30;padding:1.2rem 1.6rem}.err__container :link,.err__container :visited{color:#1f73b7}.err__additional-translation:before{background:#56777a;content:"";display:block;height:.4rem;margin:.8rem 0;overflow:hidden;width:2.4rem}.err__details-content h1{font-size:1em;font-weight:600;line-height:inherit}.err__details-content ul{margin-bottom:0;margin-top:0}.c-btn{-moz-user-select:none;-ms-user-select:none;-webkit-font-smoothing:subpixel-antialiased;-webkit-touch-callout:none;-webkit-user-select:none;background-color:transparent;border:1px solid #5293c7;border-radius:4px;box-sizing:border-box;color:#1f73b7;cursor:pointer;display:inline-block;font-family:inherit;font-size:14px;font-weight:400;line-height:38px;margin:0;min-width:8.57143em;overflow:hidden;padding:0 1.92857em;text-align:center;text-decoration:none;text-overflow:ellipsis;transition:border-color .25s ease-in-out,box-shadow .1s ease-in-out,background-color .25s ease-in-out,color .25s ease-in-out;user-select:none;vertical-align:middle;white-space:nowrap}.c-btn.c-btn--primary{background-color:#1f73b7;border-color:transparent}.c-btn.c-btn--primary{color:#fff}.c-btn.is-hovered.is-hovered,.c-btn:hover:hover{background-color:#5293c7;border-color:transparent;color:#fff;text-decoration:none}.c-btn.is-focused,.c-btn:focus:focus{box-shadow:0 0 0 3px rgba(31,115,183,.35);outline:none}.c-btn.is-active.is-active,.c-btn:active:active{background-color:#144a75;border-color:transparent;color:#fff;text-decoration:none;transition:border-color .1s ease-in-out,background-color .1s ease-in-out,color .1s ease-in-out}.u-fine-print-on-white{color:#2d5e64;font-size:.785rem}.u-centered{text-align:center}</style>
  <meta name="viewport" content="width=device-width">
</head>
[snip]
</html> (possible reasons: invalid API keys, bad or old nonce, exchange is down or offline, on maintenance, DDoS protection, rate-limiting)
    at kraken.defaultErrorHandler (/snapshot/v18build/node_modules/ccxt.pro/node_modules/ccxt/js/base/Exchange.js:582:19)
    at module.exports.handleRestResponse.response.text.then (/snapshot/v18build/node_modules/ccxt.pro/node_modules/ccxt/js/base/Exchange.js:619:18)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
  constructor: [Function: ExchangeNotAvailable],
  name: 'ExchangeNotAvailable' }
Error: Fetching my trades again.{"name":"ExchangeNotAvailable"}
    at errorHandler (/snapshot/v18build/ctx/js/kraken.js:0:0)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
Error: {}
    at errorHandler (/snapshot/v18build/ctx-wrapper.js:0:0)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)
Unable to connect to kraken
Please if this error persists, stop Gunbot, wait a few minutes and then start it again...



12

Technical Support & Development / Gunbot licence API

« on: April 17, 2020, 09:29:00 AM »

Hi,

I've made an error with my licence.
I swaped from Poloniex to Kraken but, despite what's written in the new version changelog, Kraken was not supporting shorter delay via websocket and that locked my API on Kraken.
My error was to delete the old API and create a new one... Of course, Gunbot licence was tied to the old API key and now, I"m stuck

Who can fix that ?

Thanks.

13

General Discussion / Re: Sell without buy again ?

« on: January 14, 2020, 07:52:55 PM »

Thanks a lot
Missed that option, I was searching something on global parameter, not on pair.

14

General Discussion / Sell without buy again ?

« on: January 11, 2020, 08:45:46 AM »

Hi,

I want to leave an exchange and searching for a way to sell everthing without buying again.
Is there a way to do that with Gunbot ? Sell as usual but not buying again ?

Thanks.

15

Technical Support & Development / Re: Binance can't sell

« on: June 30, 2019, 04:08:42 PM »

Try setting MIN_VOLUME_TO_SELL  and min_volume_to_buy at 0.001 for BTC-xxx pairs

This solved me sell problem on USDT-xxx pairs by setting it to 10 even if bot was selling more than 10 USDT.

Maybe bot is calling sell price with 1 FET which in your case is lower than the Binance minimum trade size of 0.001BTC.

I'm using the default "Emotionless" strat for that pair and MVB / MVS are set to 0.001.
It's really a hard-to-find bug, because the bot could sell any others pairs without problem and suddenly, it will stop and block on a random pair (not only FET) and block every sells, until I do the order manually.

16

Technical Support & Development / Binance can't sell

« on: June 27, 2019, 08:17:59 PM »

Be carefull, that thread is ignored many times by Gunthar on Telegram, that guy refuse to understand the problem...
Gunbot can't sell when he should, the error message is :

GBRT_v12.9.9.2 BTC-FET@binance Round #17 2019/06/27 19:11:36

2019/06/27 19:11:36: Entering sell cycle

entering sell

__________________________________________________________________________________________________________________
_ ______ RT Edition _ SMA        _ LowBB          _ HighBB         _ Last       _ FET     _ Last Buy   _ Pair    _
__________________________________________________________________________________________________________________
_ Sell cycle        _ 0.00001316 _ 0.000012345752 _ 0.000013968648 _ 0.00001383 _ 160.597 _ 0.00001253 _ BTC-FET _
__________________________________________________________________________________________________________________

l5694
[ minSize: undefined,
  precision: { base: 8, quote: 8, amount: 0, price: 8 } ]
Original price: 0.00001383
Original volume: 161
{ Error: binance Account has insufficient balance for requested action.
    at binance.handleErrors (/snapshot/gblackv12/node_modules/ccxt/js/binance.js:1285:27)
    at module.exports.handleRestResponse.response.text.then (/snapshot/gblackv12/node_modules/ccxt/js/base/Exchange.js:704:18)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7) constructor: [Function: InsufficientFunds] }
Error: Issue creating sell order:{}
    at errorHandler (/snapshot/gblackv12/ctx/js/binance.js:0:0)
    at <anonymous>
    at process._tickCallback (internal/process/next_tick.js:188:7)

2249

Many people stop on the message "insufficient balance" and dont go any further but :
- I could do the order manually myself on the Binance web site and get no error
- I have enough funds in BTC to SELL and pay the fees (if the fees are calculated in BTC, but it's not the case, they are in FET).
- And I have 160.597 FET, much more than the floor and more than dust of FET.

This error appear on EVERY SELLS, dont depend of the crypto.

17

Technical Support & Development / Re: GUNTHY wallet : the wrong idea ?

« on: May 14, 2019, 04:10:46 PM »

Ok, after many try, I switched to Telegram to get more help.
Aitor found me my reseller and all others problems were solved by creating a new API and switching back and forth. And using latest Gunbot version

18

Technical Support & Development / Re: TypeError: Parse buffer must be String or Buffer

« on: May 04, 2019, 07:36:08 AM »

Thanks for your answer.

But I dont think the source of the error is in the bot's configuration.
I have an old VM with a gunbot 12.8.3 working. I take all the directory and duplicate it on a new VM and got the previous error.
I've read the doc but I dont see any software requirements before running the bot.

No need to have node.js insalled ?

19

Technical Support & Development / Re: GUNTHY wallet : the wrong idea ?

« on: April 29, 2019, 09:43:16 PM »

when you purchased your gunbot license you should have received a few emails relating to the transaction.
check your spam folder, or cross-reference the website to the reseller list provided on the wiki.

Maybe I should be clearer....
I dont have any email or anything related to the first (initial) licence.
I just have information for the additional one.

20

Technical Support & Development / TypeError: Parse buffer must be String or Buffer

« on: April 28, 2019, 05:45:32 PM »

I was using Gunbot with no problem on that VM but I stopped it for licence problem (still not resolved, see my previous message, waiting for Aitor answer who got my key and wallet address...)
But now, trying to restart the program...

System : Ubuntu 18.04.2 LTS
Running Gunbot :

Code: [Select]

Loading config...
   info  - socket.io started
GUI Server Deployed: http://localhost:5000
TypeError: Parse buffer must be String or Buffer
    at Parser.parse (/snapshot/gblackv12/node_modules/node-expat/lib/node-expat.js:23:22)
    at Object.module.exports [as toJson] (/snapshot/gblackv12/node_modules/xml2json/lib/xml2json.js:172:17)
    at Request._callback (/snapshot/gblackv12/bot.gunbot.js:0:0)
    at Request.init.self.callback (/snapshot/gblackv12/node_modules/request/request.js:185:22)
    at Request.emit (events.js:159:13)
    at Request.onRequestError (/snapshot/gblackv12/node_modules/request/request.js:881:8)
    at ClientRequest.emit (events.js:159:13)
    at Socket.socketErrorListener (_http_client.js:389:9)
    at Socket.emit (events.js:159:13)
    at emitErrorNT (internal/streams/destroy.js:64:8)
    at _combinedTickCallback (internal/process/next_tick.js:138:11)
    at process._tickCallback (internal/process/next_tick.js:180:9) 'Uncaught Exception thrown'