These are clearly updates for a candle still building, but if there are no trades for a while, I won't get any further updates (even if the current candle has since closed). Has anyone challenged this scenario their own way? Would love hitbtc to just include "isClosed:true" just like binance does.
I'm trying to integrate the hitbtc APIs with a framework. I noticed the websocket sends updateCandles for conflicting events:
How do I differentiate the two? They look exactly the same:
These are clearly updates for a candle still building, but if there are no trades for a while, I won't get any further updates (even if the current candle has since closed). Has anyone challenged this scenario their own way? Would love hitbtc to just include "isClosed:true" just like binance does.