Igor Kroitor

@samgermain thx, will get to it shortly!

@samgermain can we keep both implementations and make this behavior optional to let the user choose the method of interest ? For example: - https://github.com/ccxt/ccxt/blob/master/js/gemini.js#L463 - https://github.com/ccxt/ccxt/blob/master/js/gemini.js#L485 - https://github.com/ccxt/ccxt/blob/master/js/gemini.js#L522

@wunderb1t we will merge the `onSubscribed` callback very soon: https://github.com/kroitor/ccxt.pro/pull/341 that should help mitigate your issue.

> * KYC pending and not tested. Please, let me know when it's tested, thx!

Thanks, for your suggestion! We agree completely! As you may know, this library is under active development. Switching to fixed point math is on our roadmap. Related issue: https://github.com/ccxt/ccxt/issues/393. By...

> I take it that you have a preference for using fixed point math, but this seems like it could be challenging if any calculations are required and because different...

> I don't understand this, "fixed-point" and "big integer" are the same to me. I may be using the wrong term here, but what I mean under "fixed-point" is being...

@stonemonk , we have a concern on decimal.Decimal, because from Py2 docs it looks like it uses a global context in a dirty manner. If there's no other way to...

@stonemonk looks like we can use decimal.Decimal in both Pythons with default precision + quantize, it should cover all values, hopefully. Thx!

@Bomper yes, in fact, all languages are subject to that, so we are preparing a generalized solution to this issue. Will let you know upon progress.