Replies: 2 comments
|
Nonce errors on Kraken usually mean overlapping signed requests with a stale counter — either two processes sharing one key, or retries that reuse a nonce after a network blip. If #356 covers the SDK-side fix, the operational checklist is still worth doing: one process per API key, serialize private calls, and avoid spinning up a second client in a worker without its own key. Clock skew alone rarely causes Kraken nonce failures unless the local clock jumps backward. |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi everyone, I am changing my code from a selfmade client to connect API to this library, but everytime I try to get any data I get EAPI: nonce error
`from kraken.spot import SpotClient
client = SpotClient(key="API_KEY", secret="API_PRIVATE_KEY")
print(client.request("POST", "/0/private/Balance"))`
All reactions