You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Not an issue, but a question regarding the data quality from Bitfinex: I've noticed that sometimes the raw orderbook stream will send bids that cross the best ask at that point, and vice versa. I'm wondering if you had observed the same issues and how you go about remediating them. For now I'm just removing all crossed quotes from the book when the situation occurs, but it feels like I might not have an accurate representation of the real book.
I've checked that there was indeed no level removal (book.Count == 0) at the crossed price beforehand, so my raw data confirms the issue is happening. So I'm wondering if I might have missed some updates, ie. dropped messages. Would you suggest to always use the server sequence number? In some code comment you write that it should not be required due to TCP transport guarantees. I've also seen the checksum option but it seems heavy-handed and would increase traffic quite a bit.
Thanks for your insights, and really appreciate the high-quality library you're providing!
The text was updated successfully, but these errors were encountered:
Does that issue occur like instantionously or only after x minutes/hours?
I would say it shouldn't take place, OB invalidity happens, but it is very rare.
Anyway, I didn't test that raw OB (L3) API extensively yet, always just for a few minutes, and didn't visually spot any cross, but never checked one-by-one response log.
Also, beware of the misleading price precision in the data. OB data doesn't always follow their '5 significant digits' rule, because Bitfinex is doing cross book execution.
For example orders from BTC/USD are merged together with BTC/EUR.
Found discussion here: https://www.reddit.com/r/bitfinex/comments/fvrgml/websocket_price_precision/
Not an issue, but a question regarding the data quality from Bitfinex: I've noticed that sometimes the raw orderbook stream will send bids that cross the best ask at that point, and vice versa. I'm wondering if you had observed the same issues and how you go about remediating them. For now I'm just removing all crossed quotes from the book when the situation occurs, but it feels like I might not have an accurate representation of the real book.
I've checked that there was indeed no level removal (
book.Count == 0
) at the crossed price beforehand, so my raw data confirms the issue is happening. So I'm wondering if I might have missed some updates, ie. dropped messages. Would you suggest to always use the server sequence number? In some code comment you write that it should not be required due to TCP transport guarantees. I've also seen the checksum option but it seems heavy-handed and would increase traffic quite a bit.Thanks for your insights, and really appreciate the high-quality library you're providing!
The text was updated successfully, but these errors were encountered: