Closed georgiosd closed 8 years ago
Solved it after chatting to Kraken chat (only discovered after coming here)...
For anyone passing by this issue, two notes:
For posterity, and those looking for answers, I fixed my nonce issues by bumping the tolerance setting on my api key. Its not posted very well in the docs, but you can specify a threshold that will not trigger a nonce exception. I set mine to 15000000 (15s) since this library signs requests in nano seconds.
I just use multiple API keys.
On Sat, 2 Sep 2017, 00:18 brentechols notifications@github.com wrote:
For posterity, and those looking for answers, I fixed my nonce issues by bumping the tolerance setting on my api key. Its not posted very well in the docs, but you can specify a threshold that will not trigger a nonce exception. I set mine to 15000000 (15s) since this library signs requests in nano seconds.
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/nothingisdead/npm-kraken-api/issues/20#issuecomment-326685934, or mute the thread https://github.com/notifications/unsubscribe-auth/AF2d_kxdLjeysN9uKfyPps0g7VHrcot0ks5seHSvgaJpZM4KyTWo .
--
Vlad Nistor
+40721278740 vladnistor@gmail.com
Hi all,
I'm not developing on Node but hoping you guys can give a hand, having trouble with nonce like so many others before me lol.
I use a semaphore to make sure only one nonce is generated and the response is received before trying another one but still getting a nonce error.
From fiddler capture, the requests in order (added nonce header for debugging):
Response to AddOrder:
What else could be wrong??