fetch_ticker in upbit about ccxt

[carlosmiei]

Hello @jshuh999, what do you mean exactly by "low upward trends are being returned" ?

[jshuh999]

Hello, I’m, sorry. English is my second language.I think upbit API retrieves correct tickers, but ccxt retrieves incorrect tickers.It seems that incorrect data is being entered in ticker[‘percentage’] from fetch_tickers()  When I sort ticker[‘percentage’] with reverse=True, incorrect data retrieved.On May 15, 2024, at 7:55 PM, Carlos Gonçalves ***@***.***> wrote: Hello @jshuh999, what do you mean exactly by "low upward trends are being returned" ? —Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you were mentioned.Message ID: ***@***.***>

[carlosmiei]

@jshuh999 Got it, thanks for clarifying it, we will take a look

[Dan-krm]

Hi @jshuh999 I looked into fetchTicker, fetchTickers and parseTicker on upbit and they're using the signed_change_rate from the exchange response for the ccxt percentage value in our parsed response.

That seems to be the correct expected behavior so I'm not sure how to resolve your issue for you.

Could you provide an example of the incorrect response and the correct response that you're expecting?

This is the endpoint we're using for fetchTicker/fetchTickers:
https://docs.upbit.com/reference/ticker%ED%98%84%EC%9E%AC%EA%B0%80-%EC%A0%95%EB%B3%B4
https://global-docs.upbit.com/reference/tickers