Time synchronization with Binance

I’m seeing a number if reports with ZenBot, Gekko and the CCXT projects of Binance users getting a Response Code 400 due to their internal system clocks skewing by more than 1 second. Apparently Binance required the timestamps on all signed requests to be within 1000ms of their internal time. The issue arises for Windows users where time syncrhronization is either turned off, or whose clocks have a large skew (as the time sync service in windows only updates once a day).

For this reason it may be a good idea to implement an NIST time sync based service directly into the binance module and use an internal clock for generating timestamps over the system clock.

For reference see the following issues

https://github.com/askmike/gekko/issues/1663 https://github.com/ccxt/ccxt/issues/936

I will admit that I am unsure of the feasibility of this task, but probably we shouldn’t ever update the computer’s system time as part of the process.