tardis-node

tardis-node copied to clipboard

[question] close real-time stream intentionally

7

I've checked this https://github.com/tardis-dev/tardis-node/issues/30, but it seems not working properly. Consider following code snippet, it basically re-subscribes some symbols to `deribit` exchange every minute. At the end of minute interval,...

thangng48

https://github.com/tardis-dev/tardis-node/blob/122a49f9bbb6f6917929a9da25f50d8bc3ed842e/src/realtimefeeds/binance.ts#L42-L48 A bunch of places in the real time feeds use this pattern where `Promise.all` is used to process a whole batch at once. This is not ideal however, because...

RobinDeBaets

kucoin support

3

hi, any plans for kucoin?

kigorw

It should be supported - there's support planned for it in ccxt as well ccxt/ccxt#56

thaaddeus

yuvadm

Looks like Tardis is using old `futures.order_book` channel for `gate-io-futures`, e.g. [2023-09-01 feed](https://api.tardis.dev/v1/data-feeds/gate-io-futures?from=2023-09-1) According to [this article](https://www.gate.io/article/19776) it should be possible to switch into `futures.order_book_update`, similarly as is already used...

kskalski

Why is 'E' event timestamp used instead of 'T' transaction time in Binance Futures depth update? Shouldn't it use 'T' transaction time?

4

In the Binance Futures depth stream, the event timestamp is actually the send timestamp, and the transaction timestamp is the actual time at which matching happens. When examining the stream...

nkaz001