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

Pages: [1] 2
1
As explained to me by Gunthar himself on Telegram, BOUGHT_PRICE is ONLY used for when you acquire coins through other means (ex: mining). In these situations, bot does not have any basis for calculations so you must override.

On coins that already have order book history, BOUGHT_PRICE does not do any overriding. Instead, it adds to and becomes part of the average bought price of all previous exchange history.

This Feature Request is for a per-pair parameter that either A) ignores all previous order history or B) sets a rate that supersedes all other orders.

Example: I have 100 trade history on BTC_LTC on Polo. Right now, LTC balance is 0. I transfer in some coins that I bought on another exchange for USDT. The bot should ignore all previous trade history on Polo and use my override'd BOUGHT_PRICE for all calculations.

Example implementation, ignore history older than X days when averaging bought price. This could also be set to the string "ALL" to ignore all order history. Setting to "ALL" would require a BOUGHT_PRICE to be set.

Code: [Select]
"BTC_LTC": { ..., "override": { "IGNORE_HISTORY": X } }

2
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 18, 2017, 11:48:09 PM »
Would like to see more specific output for all STEPGAIN strats. Right now, gunbot prints out the calculated price to buy as whatever my lvl3 is

Code: [Select]
2017/08/18 22:40:37: EMA1: 0.16733624/EMA2: 0.16649036
2017/08/18 22:40:37: Price to buy: 0.13319228800000002
2017/08/18 22:40:38: Got Open Orders
2017/08/18 22:40:38: Last Bid/Price to sell: 0.185/0
2017/08/18 22:40:38: Last Ask/Price to buy: 0.1853676/0.13319228800000002

I'd like to see it print out all 3 levels and would also like to see more verbose messages. Example. If my BUYLEVEL=3, then I'd like to see "GOT LEVEL 1; LOOKING FOR LEVEL 2 (PriceToBuy: X.XXXX)".... "GOT LEVEL 2; LOOKING FOR LEVEL 3 (PriceToBuy: Y.YYYY)".... "GOT LEVEL 3; PLACING BUY"

GOT LEVEL 1; LOOKING FOR LEVEL 2 (PriceToBuy: X.XXXX)"....(didn't make it) "PRICE UP; BUYING AT LEVEL 1 (X.XXXX)"

3
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 17, 2017, 10:04:21 PM »
Code: [Select]
2017/08/17 20:59:23: Kicking poloniex, receiving new tickers...
Getting tickers for poloniex catch error: Cannot read property 'error' of undefined

4
Technical Support & Development / Re: Double Up Configuration
« on: August 17, 2017, 10:03:15 PM »
+1 on this. The DOUBLE_UP feature needs some safety configuration options. Like DOUBLE_UP_LIMIT, (how many times it will do it), and DOUBLE_UP_PCT: X (how much % price must have fallen from original bought before double buy will happen)

5
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 17, 2017, 10:01:16 PM »
If DOUBLE_UP is disabled, why is this even being displayed?!? Presents a false sense of what the bot is doing. Scared the crap outta me first time I saw it.

Please change the logic to not even display messages like these if the feature is disabled.

Code: [Select]
ɢƱŋ๏Ł v4.0.4  Tips&Tricks: USDT_REP can be bought!!!
2017/08/17 20:58:02: There are some trading opportunities for USDT_REP at poloniex. Scanning Trade History
2017/08/17 20:58:02: Last Bid price USDT_REP: 20.5 | Last Ask: 20.64148522
2017/08/17 20:58:02: Balance USDT: 15096.82436570
2017/08/17 20:58:02: Balance REP: 4.75000004
2017/08/17 20:58:02: On Orders REP: 0.00000000
Processing strategy BB_GAIN for USDT_REP on poloniex
2017/08/17 20:58:02: To sell we need 0.24343750205 USDT for fees - We have: 15096.82436570 USDT
┌─────────────────┬─────────────┬────────────────────┬───────────┬───────────────────────┬────────────┬──────────┬──────────┐
│ ɢՍŋβ๏ͳ v4.0.4   │ SMA         │ LowBB              │ HighBB    │ Last                  │ REP        │ Last Buy │ Pair     │
├─────────────────┼─────────────┼────────────────────┼───────────┼───────────────────────┼────────────┼──────────┼──────────┤
│ Sell cycle      │ 21.38342904 │ 20.640021          │ 22.126837 │ 20.5                  │ 4.75000004 │ 21       │ USDT_REP │
├─────────────────┼─────────────┼────────────────────┼───────────┼───────────────────────┼────────────┴──────────┴──────────┤
│ GUNBOT CALLBACK │ Sell price  │ 21.125999999999998 │ Result    │ DOUBLE_UP is disabled │                                  │
└─────────────────┴─────────────┴────────────────────┴───────────┴───────────────────────┴──────────────────────────────────┘

6
Technical Support & Development / Re: Bugs/Issues tracker v4.0.4
« on: August 17, 2017, 09:55:21 PM »
Please pass all numbers through parseFloat. Scientific notation is difficult to read for comparing numbers with the eyes.

Code: [Select]
2017/08/17 20:48:59: Price to sell: 5.590000000000001e-7
2017/08/17 20:48:59: EMA1: 0.00000031/EMA2: 0.00000031
2017/08/17 20:48:59: Price to buy: 2.48e-7
2017/08/17 20:49:01: Got Open Orders
2017/08/17 20:49:01: Last Bid/Price to sell: 3e-7/5.590000000000001e-7
2017/08/17 20:49:01: Last Ask/Price to buy: 3.1e-7/2.48e-7
2017/08/17 20:49:01: Trend for BTC_BCN:    UP!!!
Nothing changed in BTC_BCN: Bid/Ask is 3e-7/3.1e-7. Entry points are: 2.48e-7/5.590000000000001e-7

7
Technical Support & Development / Re: Bugs/Issues tracker v4.0.3 patched
« on: August 16, 2017, 05:19:19 PM »
This box REALLY needs to have a "Total: X.XXXXX" on the last line to show the user how much total base coin was spent.

Code: [Select]
Processing strategy BB_GAIN for BTC_NEOS on poloniex
┌───────────────┬─────────────┬───────────────┬───────────────┬────────────┬────────────┬────────────┬──────────┐
│ ɢՍŋβʘͳ v4.0.3  │ LowBB       │ HighBB        │ Buy at        │ Last       │ BTC        │ NEOS       │ Pair     │
├───────────────┼─────────────┼───────────────┼───────────────┼────────────┼────────────┼────────────┼──────────┤
│ Buy cycle     │ 0.00077140  │ 0.00112345    │ 0.00085941209 │ 0.00082055 │ 0.41524832 │ 0.00000000 │ BTC_NEOS │
├───────────────┼─────────────┼───────────────┼───────────────┼────────────┼────────────┼────────────┼──────────┤
│ Callbacks     │ Time to buy │ 0.00085941209 │ BTC_NEOS      │            │            │            │          │
├───────────────┼─────────────┼───────────────┼───────────────┼────────────┼────────────┴────────────┴──────────┤
│ BOUGHT!!!     │ Amount:     │ 60.93473900   │ Rate:         │ 0.00082055 │                                    │
└───────────────┴─────────────┴───────────────┴───────────────┴────────────┴────────────────────────────────────┘

Make it look like this:

Code: [Select]
Processing strategy BB_GAIN for BTC_NEOS on poloniex
┌───────────────┬─────────────┬───────────────┬───────────────┬────────────┬────────────┬────────────┬──────────┐
│ ɢՍŋβʘͳ v4.0.3  │ LowBB       │ HighBB        │ Buy at        │ Last       │ BTC        │ NEOS       │ Pair     │
├───────────────┼─────────────┼───────────────┼───────────────┼────────────┼────────────┼────────────┼──────────┤
│ Buy cycle     │ 0.00077140  │ 0.00112345    │ 0.00085941209 │ 0.00082055 │ 0.41524832 │ 0.00000000 │ BTC_NEOS │
├───────────────┼─────────────┼───────────────┼───────────────┼────────────┼────────────┼────────────┼──────────┤
│ Callbacks     │ Time to buy │ 0.00085941209 │ BTC_NEOS      │            │            │            │          │
├───────────────┼─────────────┼───────────────┼───────────────┼────────────┼────────────┼────────────┼──────────┤
│ BOUGHT!!!     │ Amount:     │ 60.93473900   │ Rate:         │ 0.00082055 │ Total:     │ 0.05000000 │          │
└───────────────┴─────────────┴───────────────┴───────────────┴────────────┴────────────┴────────────┴──────────┘

8
Technical Support & Development / Re: Bugs/Issues tracker v4.0.1_patched
« on: August 13, 2017, 02:17:09 AM »
Some bug caused all of my trade history to be displayed as output to the screen.

Code: [Select]
....(thousands of lines before)
,"amount":"4928.82660492","total":"0.02562989"},{"globalTradeID":208040617,"tradeID":5730270,"date":"2017-08-12 22:45:32","type":"buy","rate":"0.00000519","amount":"292.91513961","total":"0.00152022"},{"globalTradeID":208040528,"tradeID":5730269,"date":"2017-08-12 22:45:08","type":"buy","rate":"0.00000519","amount":"0.00164223","total":"0.00000000"},{"globalTradeID":208040523,"tradeID":5730268,"date":"2017-08-12 22:45:08","type":"sell","rate":"0.00000517","amount":"1439.41879216","total":"0.00744179"},{"globalTradeID":208040522,"tradeID":5730267,"date":"2017-08-12 22:45:08","type":"sell","rate":"0.00000517","amount":"101.35438596","total":"0.00052400"},{"globalTradeID":208040521,"tradeID":5730266,"date":"2017-08-12 22:45:08","type":"sell","rate":"0.00000517","amount":"6010.18764409","total":"0.03107267"},{"globalTradeID":208040520,"tradeID":5730265,"date":"2017-08-12 22:45:08","type":"sell","rate":"0.00000517","amount":"4227.40500000","total":"0.0218556
2017/08/13 01:14:00: Kicking poloniex, receiving new tickers...
------------------------------------------------------------------------------------------------
 ɢƱͶ฿ͳ v4.0.1  Scanning poloniex for trading opportunities 2017/08/13 01:14:01
------------------------------------------------------------------------------------------------

Unfortunately, I launched GB inside a tmux session and the amount of transaction history was larger than my scrollback buffer so I have no idea what was output before this.

Oh oh. It just happened again while typing this:

Code: [Select]
-----------------------------------------------------------------------------------------------
 ɢƱƝƁםŁ v4.0.1  Scanning poloniex for trading opportunities 2017/08/13 01:06:32
------------------------------------------------------------------------------------------------
No new opportunities found...
2017/08/13 01:07:28: Kicking poloniex, receiving new tickers...
------------------------------------------------------------------------------------------------
 ɢՍҊβםŁ v4.0.1  Scanning poloniex for trading opportunities 2017/08/13 01:07:28
------------------------------------------------------------------------------------------------
No new opportunities found...
2017/08/13 01:11:23: Kicking poloniex, receiving new tickers...
------------------------------------------------------------------------------------------------
 ɢՍΠβ۝ͳ v4.0.1  Scanning poloniex for trading opportunities 2017/08/13 01:11:23
------------------------------------------------------------------------------------------------
No new opportunities found...
2017/08/13 01:12:16: Kicking poloniex, receiving new tickers...
------------------------------------------------------------------------------------------------
 ɢƱͶβŦ v4.0.1  Scanning poloniex for trading opportunities 2017/08/13 01:12:16
------------------------------------------------------------------------------------------------
Error on strategy BB for BTC_STR on poloniex while getting prices -| Error: [{"globalTradeID":208111592,"tradeID":5732624,"date":"2017-08-13 01:12:17","type":"buy","rate":"0.00000474","amount":"2366.82700421","total":"0.01121875"},{"globalTradeID":208111584,"tradeID":5732623,"date":"2017-08-13 01:12:16","type":"sell","rate":"0.00000471","amount":"0.00431034","total":"0.00000002"},{"globalTradeID":208111442,"tradeID":5732622,"date":"2017-08-13 01:12:09","type":"buy","rate":"0.00000468","amount":"5926

9
Technical Support & Development / Re: Bugs/Issues tracker v4.0.1_patched
« on: August 12, 2017, 11:06:43 PM »
This first line is still confusing:
Code: [Select]
  ɢՍͶƁѺŦ v4.0.1  Tips&Tricks: USDT_XRP can be sold!!!
  2017/08/12 22:04:10: There are some trading opportunities for USDT_XRP at poloniex. Scanning Trade History
  2017/08/12 22:04:10: Last Bid price USDT_XRP: 0.17455546 | Last Ask: 0.17589524

Settings:

Code: [Select]
"USDT_XRP": { "strategy": "bbstepgain", "override": { "BTC_TRADING_LIMIT": 100, "BOUGHT_PRICE": 0.21 } },
No, this should not be sold now based on my BOUGHT_PRICE.

10
Technical Support & Development / Re: Bugs/Issues tracker v4.0.1_patched
« on: August 12, 2017, 10:59:44 PM »
Why not call it 4.0.2? It's a minor release, there should have been a minor version number bump.

11
Technical Support & Development / Re: Bugs/Issues tracker v4.0.1_patched
« on: August 12, 2017, 10:57:10 PM »
BUY: https://www.dropbox.com/s/0v3x2trsch623re/buy_sjcx.png?dl=0

Current state: https://www.dropbox.com/s/q0zo3yls0h6dtre/sjcx.png?dl=0

GB properly bought at low BB, as pictured in the BUY image above. I'm using bbstepgain with default settings for v4

It has not sold yet in almost 24 hours. Look at 'Current state' image. I would have expected GB to have sold somewhere in the 6:15 block. But it has not.

It should have sold as above then purchased again around 18:45 due to being near my low BB limit.

12
Technical Support & Development / Re: Bugs/Issues tracker v4.0.1
« on: August 12, 2017, 04:53:32 AM »
Please create different verbosity levels. I have no clue what the bot is doing. Print out things like "Passed Step-Gain Level 1!! (X%)" when it passes that level, etc for each level and for buys too. X% represents the % gain.

Print out things like 'LowBB is 0.xxx; Looking for target (20%) of 0.yyyy' (where 20% is what they have set for LOWBB)

Print out status of the trend watcher like in 3.3.2: Price is going up (+3), Price is steady(0), Price falls (-2)

13
Technical Support & Development / Re: Bot Won't Run Window 10 32Bit
« on: August 11, 2017, 11:40:01 PM »
Hate to sound like an ass but it's 2017, why are you running 32bit? Surely you have a computer at least 10 years old which can support Windows10 64bit?

14
Technical Support & Development / Re: Bugs/Issues tracker v4.0.1
« on: August 11, 2017, 11:37:41 PM »
Code: [Select]
Processing strategy BB for USDT_XRP on poloniex
------------------------------------------------------------------------------------------------
 ɢƱƁŁ v4.0.1  Scanning poloniex for trading opportunities 2017/08/11 22:35:46
------------------------------------------------------------------------------------------------
No new opportunities found...
2017/08/11 22:36:06: Kicking poloniex, receiving new tickers...
------------------------------------------------------------------------------------------------
 ɢƱƝɮǾŁ v4.0.1  Scanning poloniex for trading opportunities 2017/08/11 22:36:06
------------------------------------------------------------------------------------------------
No new opportunities found...
------------------------------------------------------------------------------------------------
 ɢՍҊƁѺŦ v4.0.1  Scanning poloniex for trading opportunities 2017/08/11 22:36:12
------------------------------------------------------------------------------------------------
Error on strategy BB for BTC_GAME on poloniex while getting order book -| Error: Cannot read property 'error' of undefined
2017/08/11 22:37:12: Kicking poloniex, receiving new tickers...
Getting tickers for poloniex catch error: Cannot read property 'error' of undefined

15
Technical Support & Development / Re: Bugs/Issues tracker v4.0.1
« on: August 11, 2017, 10:59:56 PM »
Proper formatting of float's still having issues. I reported this a while back: https://github.com/GuntharDeNiro/BTCT/issues/9

Code: [Select]
2017/08/11 21:58:16: There are some trading opportunities for BTC_DOGE at poloniex. Scanning Trade History
2017/08/11 21:58:16: Last Bid price BTC_DOGE: 5e-7 | Last Ask: 5.1e-7
2017/08/11 21:58:16: Balance BTC: 0.53753830

Code: [Select]
Nothing changed in BTC_DGB: Bid/Ask is 0.00000446/0.00000449. Entry points are: 0.0000043659959/0.0000052815

Code: [Select]
Nothing changed in BTC_DOGE: Bid/Ask is 5.1e-7/5.2e-7. Entry points are: 5.1538332e-7/5.355e-7

16
Technical Support & Development / Re: Bugs/Issues tracker v4.0.1
« on: August 11, 2017, 10:56:10 PM »
Please bring back 3.3.2-style console output (ie: per-coin per-window). I do not like seeing every coin on every exchange all cluttering 1 scrolling box. Makes it difficult to "watch" what GB is thinking about a specific coin.

Additionally, "v4.0.1  Tips&Tricks: USDT_XRP can be sold!!!"

I don't like seeing this message because it presents a false sense of the bots actions. If sold now, it would sell at a huge loss. This message tells me GB is thinking of selling it now.

17
Technical Support & Development / Re: 3.3.2 pingpong issues / bugs
« on: August 09, 2017, 05:18:49 PM »
More info. Bot just placed a BUY order for some BCN. It has not completed yet. But the bot has switched to SELL mode and is attempting to sell BCN that I do not have.

Code: [Select]
WARNING: we already bought!!! Switching to sell mode...
2017/08/09 16:16:03 Error: Total must be at least 0.0001.
!!! Cycle 327 failed. Will repeat in 27.471832543750317s

There needs to be some additional logic that says "I've placed a BUY order. Wait until it fulfills before switching to SELL mode."

18
Technical Support & Development / 3.3.2 pingpong issues / bugs
« on: August 09, 2017, 04:03:24 PM »
Trying out PINGPONG for the first time. Getting the error below. Additionally, there needs to be a bit more logic here too cause I had a SELL order and then immediately had a BUY order. Seems the bot did not wait for that sell order to fulfill before starting the next cycle.

Code: [Select]
###[ --2017/08/09 14:49:14--poloniex--BTC_BCN  --  Gunbot v3.3 cycle #16196 --------------- ]
::::: collecting market data...
***************************************************
EMA1:0.00000041 - EMA2:0.00000042
***************************************************
++++
LP 4.3e-7  Bal.BTC 0.20202401  Bal.BCN 0(23197.67491735)
We have open orders
boughtPrice 0.00000043
price  steady (0)
PriceToBuy 0.0042 priceToSell 0.0043
LP 0.0043000 > prBuy 0.0042000  secMargin 1.6844000000000007e-7  grows no
no altcoins: 0
price to buy: 4.2e-7
last price is too high
Gunbot callback at 2017/08/09 14:49:15 cycle # 16196
Callback:
---------
price too high
need faster: no
need slower: no

next delay will be 16.75511924853329s


We didnt buy yet [ { orderNumber: '4556533912',
    type: 'sell',
    rate: '0.00000043',
    startingAmount: '23197.67491735',
    amount: '23197.67491735',
    total: '0.00997500',
    date: '2017-08-09 14:48:57',
    margin: 0 } ]
Unhandled rejection Error: We sent BUY order but the exchange didnt receive it.
    at Object.console./snapshot/Users/Enrico/Desktop/xBot_v2.9.3/poloniex.js.module.exports.Market.checkifwesold.poloniex.returnOpenOrders [as callback] (evalmachine.<anonymous>:0:0)
    at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:2243:31
    at /snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/async/dist/async.js:906:16
    at Request._callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/plnx/lib/index.js:138:7)
    at Request.self.callback (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:188:22)
    at emitTwo (events.js:106:13)
    at Request.emit (events.js:192:7)
    at Request.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1171:10)
    at emitOne (events.js:96:13)
    at Request.emit (events.js:189:7)
    at IncomingMessage.<anonymous> (/snapshot/Users/Enrico/Desktop/xBot_v2.9.3/node_modules/request/request.js:1091:12)
    at Object.onceWrapper (events.js:291:19)
    at emitNone (events.js:91:20)
    at IncomingMessage.emit (events.js:186:7)
    at endReadableNT (_stream_readable.js:974:12)
    at _combinedTickCallback (internal/process/next_tick.js:74:11)
    at process._tickCallback (internal/process/next_tick.js:98:9)

19
https://github.com/GuntharDeNiro/BTCT/issues/8

On linux, the bot doesn't always recognize that the config file has changed. Instead of restarting the bot, bot should respond to kill -HUP to reload the config manually. "kill -HUP" is the accepted standard in the linux world for telling a daemon/app to reload any configuration files.

20
https://github.com/GuntharDeNiro/BTCT/issues/9

Sometimes values are printed as 0.12344001122, sometimes as 5443.2210 (which really should be printed as 0.54432210), sometimes printed as 7.1e-7, sometimes printed as price to buy: 7.679280000000009e-7

It's extremely frustrating to "see" what's going on with the bot when numbers are not formatted consistently.

Please fix the code so that all numbers are formatted properly to the correct number of significant digits.

Pages: [1] 2