Gekko: Kraken buy order precision

Created on 5 Sep 2017  路  6Comments  路  Source: askmike/gekko

Note: for support questions, please join our Discord server

  • I'm submitting a ...
    [ X] bug report
    [ ] feature request
    [ ] question about the decisions made in the repository

  • Action taken (what you did)
    Ask gekko to trade on kraken

  • Expected result (what you hoped would happen)
    that gekko can buy!

  • Actual result (unexpected outcome)
    Error of kraken api call due to precision problem

  • Other information (e.g. detailed explanation, stacktraces, related issues, suggestions how to fix, links for us to have context, eg. stackoverflow, etc)

This behaviour was explained by kraken a few days ago
https://blog.kraken.com/post/1261/announcement-reducing-price-precision-on-all-trading-pairs/

2017-09-05 00:00:47 (DEBUG): kraken returned an error, retrying..
2017-09-05 00:00:52 (DEBUG): BUY 0.359568 ETH @ 273.60199999 EUR
2017-09-05 00:00:53 (ERROR): unable to buy Error: Order:Invalid price:XETHZEUR price can only be specified up to 3 decimals.
at /home/XXX/bin/gekko/node_modules/kraken-api-es5/index.js:59:13
at next (native)
at step (/home/XXX/bin/gekko/node_modules/kraken-api-es5/index.js:1:253)
at /home/XXX/bin/gekko/node_modules/kraken-api-es5/index.js:1:423
at process._tickCallback (internal/process/next_tick.js:109:7)

bug exchange wontfix

All 6 comments

Ah yes, Kraken has changed a few days back. Will update!

I'm working on

@lbnt can you try out the latest develop branch of Gekko? You can download it here:
https://github.com/askmike/gekko/tree/develop

It includes a fix for this issue by @julesGoullee!

I'm currently trying multiple pairs too

I keep getting:

TypeError: Cannot read property 'log' of undefined
at pipelineRunner (C:\xxxx\xx\Downloads\gekko-develop\web\routes\startGekko
.js:86:14)
at Object.message (C:\xxxx\xx\Downloads\gekko-develop\core\workers\pipeline
\messageHandlers\realtimeHandler.js:10:9)
at ChildProcess. (C:\xxxx\xx\Downloads\gekko-develop\core\worker
s\pipeline\parent.js:29:12)
at emitTwo (events.js:126:13)
at ChildProcess.emit (events.js:214:7)
at emit (internal/child_process.js:772:12)
at _combinedTickCallback (internal/process/next_tick.js:141:11)
at process._tickCallback (internal/process/next_tick.js:180:9)
disconnect

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. If you feel this is very a important issue please reach out the maintainer of this project directly via e-mail: gekko at mvr dot me.

Was this page helpful?
0 / 5 - 0 ratings

Related issues

EslamAwwad picture EslamAwwad  路  6Comments

prathanbomb picture prathanbomb  路  3Comments

burtnderson picture burtnderson  路  5Comments

yacindou picture yacindou  路  3Comments

LeMoussel picture LeMoussel  路  6Comments