T. Todua
T. Todua
PR submitted, will be merged soon probably. about parsing the fees twice, please open a new issue , so we could assign it independently from this original issue.
Yes I guess, my edits were not enough and it needed further updates in base-parser functions, but as I couldnt finish it on time yesterday, @kroitor merged the PR not...
closing this one too. let me know if still any issue.
ahhh.... thanks. i've revived my old PR. I hope it might get merged at this stage.
@carlosmiei ready. i have completely rewriten some parts, as they were outdated and inaccurate. I've also unified futures/swap symbols, as their symbols were i.e. `XBTUSDT` (non unified) till date and...
@carlosmiei Bitmex ready to be reviewed. fixed all methods throughout entire class.
> This update might be relevant, https://blog.bitmex.com/site_announcement/upcoming-updates-to-our-websocket-and-rest-apis/ removal of nulls and some fields for endpoints on bitmex Good note Dan. On the other hand I think it will need a...
@carlosmiei how do you think - when this PR gets merged, it automatically switches to new precisions. however, users will have some distorted results and mistakes in their userland scripts,...
@samgermain I am not sure that conversion/code is the problem actually, as @carlosmiei raised questions about the proposed functionality (the precisions mostly) whether they were accurate or not. In my...
> @ttodua Was this fixed in another PR? yes, Carlos has made that in separate PR here - https://github.com/ccxt/ccxt/pull/18089 but it's not merged yet