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.

Topics - krixt

Pages: [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 } }

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


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.


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.

Consider this excerpt from the running bot.

Code: [Select]
###[ --2017/07/15 02:00:07--poloniex--BTC_AMP  --  Gunbot v3.3 cycle #22149 --------------- ]
::::: collecting market data...
Low BB:0.00007436 - High BB:0.00007619
EMA1:0.00007555 - EMA2:0.00007555
BB price to buy 0.00007509200394562912 -- GAIN price to buy 0.00007301632966666657
LP 0.00007438  Bal.BTC 0.51366307  Bal.AMP 0(0)
No open orders
boughtPrice 0.00007436
price  falls (-3)
PriceToBuy 0.7302 priceToSell 0.7585
LP 0.7438000 > prBuy 0.7301633  secMargin 0.000029744000000000002  grows no
no altcoins: 0
price to buy: 0.00007301632966666657
last price is too high

The settings are:

Code: [Select]
LOW_BB: 40,
HIGH_BB: 40,
BUYLVL3: 10,
GAIN: 2,

There are two problems here.
  • There are two lines that say 'priceToBuy' and they both have different values. Why are there 2 of this line?
  • Notice that prBuy and 'price to buy' match that of GAIN price to buy. The question here is WHY? GAIN is not my buy strategy; BB is. So why is the bot doing this?

General Discussion / Placing manual orders with the bot
« on: July 08, 2017, 10:48:42 PM »
Does it royally screw up the bot if I place a manual order for a pair the bot is currently "managing"?

General Discussion / Upgrading to 3.3.2 - Instructions Needed
« on: July 06, 2017, 04:20:41 PM »
Gunthar's instructions are unclear: "just replace executables"

I understand that part, extract the zip and copy/replace the binaries.

Do I then stop all my bots and re-start them? Is that safe? How do I know the best time to restart my bots? What's the proper, step-by-step, upgrade procedure if you have running bots already?

Pages: [1]