Open mrherickz opened 4 years ago
You are right. It's probably a nonce issue. You should wait a few ms between calls or, even better, wait for a request to complete before sending the next one. There is a delay implemented in the lib, but maybe it's not enough given the delay/round-trip between client and server.
Nonce should always be a bigger integer then the one sent last time for a given key, so if an async request T arrives after request T+1, which is possible bc of different routes, for example, it fails.
While playing around with Biscoint's node client, I constantly get this response in the authenticated endpoints:
I suspect the issue is related to the nonce or the actual request signing.