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

Pages: [1] 2
1
Beginners & Help / Re: Emotionless getting too emotional
« on: December 21, 2017, 08:05:55 PM »
yeah it's not selling anything since 7.0.1 is out  :-\

2
Technical Support & Development / Re: BTC Surge Protection
« on: December 08, 2017, 04:14:07 PM »
Same here, Surge Protection did not really work

3
Use the default settings and fine tune them. Yours don't make sense at all.

4
Technical Support & Development / Re: 4.0.5 definitive settings?
« on: September 07, 2017, 10:19:12 AM »
Shouldn't EMA1 be higher than EMA2? (see https://github.com/GuntharDeNiro/BTCT/issues/54)

5
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 20, 2017, 11:41:15 PM »
After a while GB 4.04 seems to run VERY high on CPU usage - as high as up to 99 - 100% and stays here...



EDIT
It went  down again to normal amounts of CPU usage, but nevertheless there seems to be something wrong. maybe it has to do with those undefined function errors @bbstepgain

EDIT2
and up again to 100% ...

I can confirm 99% percent of CPU usage while processing strategies. Processing a strategy takes a lot of time as well, up to 5 minutes. Maybe this is related to much higher values for "period_storage_ticker" and "interval_ticker_update" than for previous versions? EDIT: Changing the values did not change much. But it does seem like the bot is becoming slower. So maybe there's some kind of memory leak. Right now it takes almost 50 minutes to process all my pairs (12). This results in missed trades.
EDIT2: The processing time for BB strategy is directly related to the volume on polo. BCH ( 16696.89084128 BTC) takes forever. ZEC (1109.02534245 BTC) takes only a few seconds. Thus the higher processing time is probably due to the much higher number of trades.

6
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 20, 2017, 08:57:10 PM »
I just added some funds. And the bot immediately did this again:

XMR/BTC   Buy   Exchange   0.01321202   4.31982929   0.01079957 XMR (0.25%)   0.05707367 BTC   2017-08-20 19:45:00

EDIT: I noticed that the bot is still trying to average XMR. So it's not about ignoring the BTC_TRADING_LIMIT setting but rather that "DOUBLE_UP: true" uses all my funds. I never bought more XMR than for 0.02 BTC so it does not make sense that the bot now buys XMR for more than 0.1 BTC.

EDIT2: For debugging. This is my complete XMR history.

   XMR/BTC   Buy   Exchange   0.01321202   4.31982929   0.01079957 XMR (0.25%)   0.05707367 BTC   2017-08-20 19:45:00
   XMR/BTC   Buy   Exchange   0.01315680   0.39629882   0.00099075 XMR (0.25%)   0.00521402 BTC   2017-08-20 19:15:42
   XMR/BTC   Buy   Exchange   0.01315679   1.76631909   0.00441580 XMR (0.25%)   0.02323908 BTC   2017-08-20 19:15:42
   XMR/BTC   Buy   Exchange   0.01317402   0.66149623   0.00165374 XMR (0.25%)   0.00871456 BTC   2017-08-20 19:11:57
   XMR/BTC   Buy   Exchange   0.01317000   0.42116605   0.00105292 XMR (0.25%)   0.00554675 BTC   2017-08-20 19:11:57
   XMR/BTC   Buy   Exchange   0.01617000   0.54200865   0.00135502 XMR (0.25%)   0.00876427 BTC   2017-08-01 21:08:42
   XMR/BTC   Buy   Exchange   0.01843920   0.25591084   0.00038387 XMR (0.15%)   0.00471879 BTC   2017-07-07 08:00:12
   XMR/BTC   Buy   Exchange   0.01843920   0.28691203   0.00043037 XMR (0.15%)   0.00529042 BTC   2017-07-07 07:59:59
   XMR/BTC   Sell   Exchange   0.01941000   0.52596473   0.00002552 BTC (0.25%)   0.01018345 BTC   2017-07-07 01:42:57
   XMR/BTC   Buy   Exchange   0.01900220   0.02428154   0.00003642 XMR (0.15%)   0.00046140 BTC   2017-06-20 19:59:52
   XMR/BTC   Buy   Exchange   0.01900220   0.50247331   0.00075371 XMR (0.15%)   0.00954809 BTC   2017-06-20 19:59:49
   XMR/BTC   Sell   Exchange   0.01939989   0.53105101   0.00002576 BTC (0.25%)   0.01027657 BTC   2017-06-13 19:18:55
   XMR/BTC   Buy   Exchange   0.01882003   0.53184878   0.00079777 XMR (0.15%)   0.01000940 BTC   2017-06-12 11:26:17
   XMR/BTC   Sell   Exchange   0.01957599   0.52030127   0.00002546 BTC (0.25%)   0.01015995 BTC   2017-06-11 13:36:38
   XMR/BTC   Buy   Exchange   0.01918997   0.52160528   0.00130401 XMR (0.25%)   0.01000958 BTC   2017-06-10 10:50:54
   XMR/BTC   Sell   Exchange   0.01829999   0.56952328   0.00002606 BTC (0.25%)   0.01039621 BTC   2017-06-06 22:40:47
   XMR/BTC   Buy   Exchange   0.01753000   0.57095065   0.00142738 XMR (0.25%)   0.01000876 BTC   2017-06-06 16:58:15
   XMR/BTC   Sell   Exchange   0.01759003   0.58383106   0.00002567 BTC (0.25%)   0.01024393 BTC   2017-06-05 05:39:34
   XMR/BTC   Buy   Exchange   0.01710003   0.58529429   0.00146324 XMR (0.25%)   0.01000854 BTC   2017-06-03 15:03:37
   XMR/BTC   Sell   Exchange   0.01870000   0.54582937   0.00002552 BTC (0.25%)   0.01018148 BTC   2017-05-30 12:12:46
   XMR/BTC   Buy   Exchange   0.01831001   0.54664934   0.00081997 XMR (0.15%)   0.01000915 BTC   2017-05-30 09:55:40
   XMR/BTC   Sell   Exchange   0.01973500   1.83402720   0.00005429 BTC (0.15%)   0.03614023 BTC   2017-03-30 11:55:31
   XMR/BTC   Buy   Exchange   0.01319477   1.00000000   0.00250000 XMR (0.25%)   0.01319477 BTC   2016-10-04 07:31:47
   XMR/BTC   Buy   Exchange   0.01345098   0.51273103   0.00128183 XMR (0.25%)   0.00689673 BTC   2016-10-02 20:34:40

7
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 20, 2017, 08:41:01 PM »
I can confirm ignoring of trading limit.

I have it set to 0.01 BTC and the bot did this today:

   XMR/BTC   Buy   Exchange   0.01315680   0.39629882   0.00099075 XMR (0.25%)   0.00521402 BTC   2017-08-20 19:15:42
   XMR/BTC   Buy   Exchange   0.01315679   1.76631909   0.00441580 XMR (0.25%)   0.02323908 BTC   2017-08-20 19:15:42
   XMR/BTC   Buy   Exchange   0.01317402   0.66149623   0.00165374 XMR (0.25%)   0.00871456 BTC   2017-08-20 19:11:57
   XMR/BTC   Buy   Exchange   0.01317000   0.42116605   0.00105292 XMR (0.25%)   0.00554675 BTC   2017-08-20 19:11:57

8
Technical Support & Development / Stepgain 4.0.4
« on: August 20, 2017, 08:18:34 PM »
Can somebody please explain the new stepgain strategy? If I set Buylvl and Selllvl to 3 the bot ignores the first two levels. Where is the point then?

My stepgain config is for example:

      "PERIOD": 15,
      "BUYLVL1": 2,
      "BUYLVL2": 10,
      "BUYLVL3": 30,
      "SELLLVL1": 3,
      "SELLLVL2": 9,
      "SELLLVL3": 25,
      "BUYLVL": 3,
      "SELLLVL": 3,
      "LASTPOINTS": 5,
      "AVGPOINTS": 250,
      "AVGMINIMUM": 0.00000001,
      "EMA1": 2000,
      "EMA2": 1000,

And the bot won't buy BCH until the 30% drop is reached:

Processing strategy STEPGAIN for BTC_BCH on poloniex
┌───────────────┬──────────────────────────────────────┬────────────┬─────────────┬───────┬────────────┬────────────┬─────────┐
│ ɢƱͶƁʘŁ v4.0.4 │ EMA1                                 │ EMA2       │ Buy at      │ Last  │ BTC        │ BCH        │ Pair    │
├───────────────┼──────────────────────────────────────┼────────────┼─────────────┼───────┼────────────┼────────────┼─────────┤
│ Buy cycle     │ 0.18745546                           │ 0.18786848 │ 0.131218822 │ 0.177 │ 0.03195458 │ 0.00000000 │ BTC_BCH │
├───────────────┼──────────────────────────────────────┼────────────┴─────────────┴───────┴────────────┴────────────┴─────────┤
│ Callbacks     │ Waiting to buy: price is too high!!! │                                                                      │

9
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 18, 2017, 02:48:46 PM »
Randomly prints huge json results from poloniex.

Looks like this:

84411","amount":"0.00001147","total":"0.00000062"},{"globalTradeID":211296205,"tradeID":7189987,"date":"2017-08-18 08:05:35","type":"buy","rate":"
0.05484411","amount":"11.57632956","total":"0.63489349"},{"globalTradeID":211296204,"tradeID":7189986,"date":"2017-08-18 08:05:35","type":"buy","r
ate":"0.05484411","amount":"4.18815282","total":"0.22969551"},{"globalTradeID":211296203,"tradeID":7189985,"date":"2017-08-18 08:05:35","type":"bu
y","rate":"0.05461758","amount":"0.01850753","total":"0.00101083"},{"globalTradeID":211296147,"tradeID":7189984,"date":"2017-08-18 08:05:28","type
":"buy","rate":"0.05461758","amount":"0.16656775","total":"0.00909752"},{"globalTradeID":211296046,"tradeID":7189983,"date":"2017-08-18 08:05:14",
"type":"buy","rate":"0.05461758","amount":"0.00000004","total":"0.00000000"},{"globalTradeID":211295939,"tradeID":7189982,"date":"2017-08-18 08:05
:01","type":"buy","rate":"0.05469915","amount":"0.00000007","total":"0.00000000"},{"globalTradeID":211295935,"tradeID":7189981,"date":"2017-08-18
08:05:01","type":"buy","rate":"0.05469917","amount":"3.80429339","total":"0.20809169"},{"globalTradeID":211295934,"tradeID":7189980,"date":"2017-0
8-18 08:05:01","type":"buy","rate":"0.05469916","amount":"6.15705782","total":"0.33678589"},{"globalTradeID":211295933,"tradeID":7189979,"date":"2
017-08-18 08:05:01","type":"buy","rate":"0.05454338","amount":"4.53573534","total":"0.24739433"},{"globalTradeID":211295932,"tradeID":7189978,"dat
e":"2017-08-18 08:05:01","type":"buy","rate":"0.05454337","amount":"1.08038946","total":"0.05892808"},{"globalTradeID":211295863,"tradeID":7189977
,"date":"2017-08-18 08:04:52","type":"sell","rate":"0.05454338","amount":"0.32157089","total":"0.01753956"},{"globalTradeID":211295639,"tradeID":7
189976,"date":"2017-08-18 08:04:29","type":"buy","rate":"0.05469926","amount":"1.91596109","total":"0.10480165"},{"globalTradeID":211295638,"trade
ID":7189975,"date":"2017-08-18 08:04:29","type":"buy","rate":"0.05454339","amount":"6.14953385","total":"0.33541642"},{"globalTradeID":211295637,"
tradeID":7189974,"date":"2017-08-18 08:04:29","type":"buy","rate":"0.05454339","amount":"2.43417023","total":"0.13276789"},{"globalTradeID":211295
636,"tradeID":7189973,"date":"2017-08-18 08:04:29","type":"buy","rate":"0.05454339","amount":"4.26184398","total":"0.23245541"},{"globalTradeID":2
11295496,"tradeID":7189972,"date":"2017-08-18 08:04:14","type":"sell","rate":"0.05454339","amount":"1.72918063","total":"0.09431537"},{"globalTrad
eID":211295366,"tradeID":7189971,"date":"2017-08-18 08:03:59","type":"buy","rate":"0.05469935","amount":"0.00000016","total":"0.00000000"},{"globa
lTradeID":211295348,"tradeID":7189970,"date":"2017-08-18 08:03:55","type":"buy","rate":"0.05469938","amount":"0.00001151","total":"0.00000062"},{"
globalTradeID":211295323,"tradeID":7189969,"date":"2017-08-18 08:03:50","type":"sell","rate":"0.05449138","amount":"0.00114164","total":"0.0000622
0"},{"globalTradeID":211295245,"tradeID":7189968,"date":"2017-08-18 08:03:36","type":"buy","rate":"0.054
------------------------------------------------------------------------------------------------
 ɢՍƝ฿õŁ v4.0.4  Scanning poloniex for trading opportunities 2017/08/18 15:43:08
------------------------------------------------------------------------------------------------
Nothing changed in BTC_CLAM: Bid/Ask is 0.00156701/0.00157027. Entry points are: 0.0015547141/0.0016431435


Can't tell you what causes this because my console does not log all of it.

10
Technical Support & Development / Re: Bugs/Issues tracker v3.3.5
« on: August 07, 2017, 10:08:41 AM »
Bot is still trying to avarage XEM even now when the value  (0.00007970 atm) is above bought price.
This is the output:

No new opportunities found...
------------------------------------------------------------------------------------------------
 ɢƱͶɃõŁ v3.3.4  Scanning poloniex for trading opportunities 2017/08/06 23:38:56
------------------------------------------------------------------------------------------------
2017/08/06 23:39:02: Kicking poloniex, receiving new tickers...
 ɢƱƝβǾŁ v3.3.4  Tips&Tricks: BTC_XEM can be averaged!!!
2017/08/07 11:01:12: There are some trading opportunities for BTC_XEM at poloniex. Scanning Trade History
2017/08/07 11:01:12: Last Bid price BTC_XEM: 0.00007244 | Last Ask: 0.0000725
2017/08/07 11:01:12: Balance BTC: 0.01708846
2017/08/07 11:01:12: Balance XEM: 475.08203502
2017/08/07 11:01:12: On Orders XEM: 0.00000000
Processing strategy BB for BTC_XEM on poloniex
TRAILING STOP!!!
The value of this coin dropped below bought price (0.0000780925). Proceeding with Trailing Stop!
Loading config...
Loading exchange poloniex
2017/08/07 11:01:32: Kicking poloniex, receiving new tickers...
------------------------------------------------------------------------------------------------
 ɢƱΠƁ۝Ł v3.3.4  Scanning poloniex for trading opportunities 2017/08/07 11:01:38
------------------------------------------------------------------------------------------------
2017/08/07 11:01:42: Kicking poloniex, receiving new tickers...
2017/08/07 11:03:02: Kicking poloniex, receiving new tickers...

11
Technical Support & Development / Re: Bugs/Issues tracker v3.3.5
« on: August 06, 2017, 10:32:52 PM »
Version 3.3.5 ignores trading limit and makes multiple buys before selling.
My limit is set to 0.01 BTC. Avaraging is enabled.
Please notice the last buy.


12
Technical Support & Development / Re: Bugs/Issues tracker v3.3.5
« on: August 03, 2017, 11:26:18 AM »
There are occasional errors while getting balances:

------------------------------------------------------------------------------------------------
 ɢƱŋɮØŁ v3.3.4  Scanning poloniex for trading opportunities 2017/08/03 12:20:35
------------------------------------------------------------------------------------------------
2017/08/03 12:20:37: Kicking poloniex, receiving new tickers...
No new opportunities found...
------------------------------------------------------------------------------------------------
 ɢՍŋɮǾŁ v3.3.4  Scanning poloniex for trading opportunities 2017/08/03 12:20:41
------------------------------------------------------------------------------------------------
2017/08/03 12:20:55: Kicking poloniex, receiving new tickers...
2017/08/03 12:21:05: Kicking poloniex, receiving new tickers...
2017/08/03 12:21:15: Kicking poloniex, receiving new tickers...
Error on strategy BB for BTC_ETC on poloniex while getting balances -| Error: Cannot read property 'error' of undefined
------------------------------------------------------------------------------------------------
 ɢƱҊß๏ͳ v3.3.4  Scanning poloniex for trading opportunities 2017/08/03 12:21:24
------------------------------------------------------------------------------------------------
2017/08/03 12:21:25: Kicking poloniex, receiving new tickers...
No new opportunities found...
------------------------------------------------------------------------------------------------
 ɢƱŋ฿۝Ŧ v3.3.4  Scanning poloniex for trading opportunities 2017/08/03 12:21:25
------------------------------------------------------------------------------------------------
No new opportunities found...
------------------------------------------------------------------------------------------------
 ɢƱΠɮØŦ v3.3.4  Scanning poloniex for trading opportunities 2017/08/03 12:21:32
------------------------------------------------------------------------------------------------
2017/08/03 12:21:35: Kicking poloniex, receiving new tickers...
Error on strategy BB for BTC_STEEM on poloniex while getting balances -| Error: Cannot read property 'error' of undefined

14
Technical Support & Development / Re: Stop trading after sell
« on: June 15, 2017, 11:35:28 PM »
Well just set buy strategy to PINGPONG and PINGPONG_BUY: 0.00000001
I guess.

Thanks. But i want to end sell with BB strategy, and after stop. No more buy's.

Maybe I don't understand you correctly but if you set the buy level to one satoshi, it is highly unlikely that the bot will make another by.
I think, you can still use BB to sell.
Use sth. like this in your config file:
        BUY_STRATEGY: "PINGPONG", // accepted values BB or STEPGAIN or GAIN or PINGPONG
   SELL_STRATEGY: "BB", // 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.00000001, //price to buy (or lower) in the ping pong strategy

15
But I guess this falls in line with https://gunthy.org/index.php?topic=430.0 which would be a nice feature.

16
You can not move every coin to lending.

17
Technical Support & Development / Re: Stop trading after sell
« on: June 15, 2017, 04:11:15 PM »
Well just set buy strategy to PINGPONG and PINGPONG_BUY: 0.00000001
I guess.

18
I definitely get less 422 errors using multiple keys.
Now using 6 keys for 18 pairs. 280s delay. 220s error delay.

19
Well I did fix a 422-loop with a lending bot once by using a new api key.
So I will try this.

20
Is this to fix 422 Errors? How many are we supposed to make for lets say 15 pairs?

Pages: [1] 2