T. Todua
T. Todua
@carlosmiei if you want, assign this to someone (this would be equal to 'new exchange' implementation, as v4 is expected to be quite different from v2). I'd like to continue...
@Curro666 can you tell if the issue is still present?
@Curro666 this PR updates bitmex : https://github.com/ccxt/ccxt/pull/15311 so, you will need to wait for its merge and re-test then.
> > @Curro666este PR actualiza bitmex: [# 15311](https://github.com/ccxt/ccxt/pull/15311) , por lo que deberá esperar a que se fusione y vuelva a probarlo. > > sorry but not bitmex the exchange...
Similar question was asked before [here](https://github.com/ccxt/ccxt/issues/8677). If that doesn't answer the issue, let us know.
@frosty00 @kroitor please, if you have some clues, post a reply here.
#lead this PR is ready for review. the affected exchange files have the needed changes, nothing is breaking-change. Private local tests (for `fetchCurrencies` & `fetchMarkets`) also run successfully for all...
@danieltorscho as you see, you can use these unified account-types: https://github.com/ccxt/ccxt/blob/37b2f250a161f808453d292052982baa2f8904c3/js/bybit.js#L578-L586 and it will work. also, as we think this is not issue in ccxt, I will close this issue...
@danieltorscho thanks for your follow ups! I will revise the current state of our bybit integration and its API docs, to find out what has been changed, and then push...
@filipegalo try it without `['options']` as Sam suggested and let us know: ``` exchange['apiKey'] = user['apiKey'] exchange['apiKey'] = user['secret'] ```