Messages

1

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

« on: August 16, 2017, 06:59:59 AM »

4.0.3 polo

pair BTC/NAUT is still averaging even though double up property  is set to false (log below)
same goes for BTC/NXT


on related note I noticed, that when the bot prints to the console the BB output, the table header string differs between different coins.  Sometimes there are different characters in the string "ɢƱΠβѺŦ ", sometimes there is an extra space. It seems like you are handling different coins by different code. Might be pain to manage.  Maybe because of that when if you are fixing something in the code, you need to fix that separately for each coin, which is of course a space for error. I marked the section I meant in the red below.


...
 ɢՍƝɮםŁ v4.0.3  Tips&Tricks: BTC_NAUT can be averaged!!!
 ɢƱƝƁ۝Ł v4.0.3  Tips&Tricks: BTC_NAUT can be bought!!!
2017/08/16 04:08:37: There are some trading opportunities for BTC_NAUT at poloniex. Scanning Trade History
2017/08/16 04:08:37: Last Bid price BTC_NAUT: 0.000036 | Last Ask: 0.00003609
2017/08/16 04:08:37: Balance BTC: 0.01110775
2017/08/16 04:08:37: Balance NAUT: 12.72808472
2017/08/16 04:08:37: On Orders NAUT: 0.00000000
Processing strategy BB for BTC_NAUT on poloniex
┌───────────────┬─────────────┬────────────────┬────────────────┬────────────┬────────────┬─────────────┬──────────┐
│ ɢƱΠβѺŦ v4.0.3 │ LowBB       │ HighBB         │ Buy at         │ Last       │ BTC        │ NAUT        │ Pair     │
├───────────────┼─────────────┼────────────────┼────────────────┼────────────┼────────────┼─────────────┼──────────┤
│ Buy cycle     │ 0.00003262  │ 0.00004157     │ 0.000036200494 │ 0.00003609 │ 0.01110775 │ 12.72808472 │ BTC_NAUT │
├───────────────┼─────────────┼────────────────┼────────────────┼────────────┼────────────┼─────────────┼──────────┤
│ Callbacks     │ Time to buy │ 0.000036200494 │ BTC_NAUT       │            │            │             │          │
├───────────────┼─────────────┼────────────────┼────────────────┼────────────┼────────────┴─────────────┴──────────┤
│ BOUGHT!!!     │ Amount:     │ 27.70850700    │ Rate:          │ 0.00003609 │                                     │
└───────────────┴─────────────┴────────────────┴────────────────┴────────────┴─────────────────────────────────────┘
...


Have a nice day.

2

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

« on: August 12, 2017, 09:00:06 AM »

Hello Gunthy, reporting double buy at Poloniex, btc/dbg pair, sold correctly, then bought again but double. Two identical buys.
Nice weekend to you all.

3

Technical Support & Development / Re: Bugs/Issues tracker v3.3.5

« on: August 02, 2017, 09:38:33 AM »

Thank you for response, beer-k0in.
There is no LSK leftover currently, but I found the problem, I was experimenting with ETH/LSK pair previously. That is the culprit,
Have a nice day!

 

4

Technical Support & Development / Re: Bugs/Issues tracker v3.3.5

« on: August 02, 2017, 07:50:16 AM »

Hello, I encountered sale at a loss:



Buys were done by 3.3.4, sale by 3.3.5

settings (I forgot to put {"HIGH_BB": 40} in override for this pair, if it makes difference?)
...
"BTC_LSK"  : {"strategy": "bb","override": {}},
...
"bot": {
      "debug": true,

      "period_storage_ticker": 300,
      "interval_ticker_update": 10000,

      "timeout_buy": 60000,
      "timeout_sell": 60000,

      "MIN_VOLUME_TO_BUY": 0.0005,

      "WATCH_MODE": false
   },

   "strategies": {
      "bb": {
         "BTC_TRADING_LIMIT": 0.001,
         "PERIOD": 15,
         "BUY_LEVEL": 0.1,
         "GAIN": 0.6,
         "HIGH_BB": 60,
         "LOW_BB": 40,
         "PANIC_SELL": false,
         "DOUBLE_UP": true
      }
   }