BITZ nonce issue

[jed057]

• OS:
• Programming Language version: Python
• CCXT version: latest
• Exchange: BIT-Z
• Method: nonce()

In my application I need to periodically query balances and open orders in a relatively high frequency. Then I got an error with 'nonce must be a 6 dig string' or something after several minutes.. it is a 100% reproducible issue.

When I doing some logging I found the generated nonce was an incremental 6 digits (each time) so I guess it will exceed 999999 finally.

I have tried to use the random lib to generate a random 6 digit string and test again it looks the issue never happen again. (there could be other solutions..)

[mkutny]

When I doing some logging I found the generated nonce was an incremental 6 digits (each time) so I guess it will exceed 999999 finally.

It's milliseconds % 1000000 so every ~15 mins it produces 0, indeed.

Does it fail somehow if you send the same nonce twice in a row? I wonder if it could be ignored as they use timestamp as a part of signature anyway.

[jed057]

not really sure, what i can provide is the response with the 203 code and msg content : u"Nonce must be a 6 bit string"

[mkutny]

Ok, as a temporary fix (if you need it urgently) you can change the following line to seconds (or its equivalent in async version):

ccxt/python/ccxt/bitz.py

Line 342 in ecf82f3

milliseconds = self.milliseconds()

[wntsang4]

I got this error too. "Nonce must be a 6 bit string"

[kroitor]

6 bit is a range of 0-64, that is ridiculous for a nonce value )) I guess they really mean 6 decimal digits... maybe even 6 characters... which is still a pretty restrictive upper limit... It might demand changing the key once in a quarter...

Anyway, @wntsang4 , @jed057 I'll look into it and will figure a way to make it work smoothly. Hold on, plz, will get back to you on this issue.