ccxt: ByBit Order output cost and amount are the wrong way around
MUST READ THIS BEFORE SUBMITTING ISSUES (read the links, then delete this message before submitting):
https://github.com/ccxt/ccxt/blob/master/FAQ https://github.com/ccxt/ccxt/blob/master/CONTRIBUTING.md#how-to-submit-an-issue
Make sure your local version of CCXT is up to date. Check by comparing the output of ccxt.version to https://github.com/ccxt/ccxt/blob/master/package.json#L3
- OS:
- Programming Language version: Node ^13
- CCXT version: ^1.26.45

About this issue
- Original URL
- State: closed
- Created 4 years ago
- Comments: 18 (8 by maintainers)
Commits related to this issue
- bybit parseTrade minor edit fix #6866 — committed to ccxt/ccxt by kroitor 4 years ago
- bybit parseOrder inverse futures amount / cost fix #6866 — committed to bitpanda-labs/ccxt by kroitor 4 years ago
- bybit parseTrade amount/cost fix #6866 — committed to bitpanda-labs/ccxt by kroitor 4 years ago
- bybit parseTrade minor edit fix #6866 — committed to bitpanda-labs/ccxt by kroitor 4 years ago
- bybit linear/inverse reverted #6866 — committed to ccxt/ccxt by kroitor 4 years ago
Totally understand you can ignore that
appreciate it thanks, on other small thing could you have the average populated by the last_exec_price as its null and I have example of market orders and I have to go into the info object to get it. happy to provide an example
@kroitor I think this commit should reverted too, Its going to make it too difficult for users to calculate held contract amounts which is whats more important. appreciate you spending time on this however I feel it will be better to wait for you guys to unify it properly.
Sure, this is from our DB, assumed you had this stuff mocked already