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

[nkaz001]

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 data, the transaction timestamp precedes the event timestamp. If we use the event timestamp, it results in lower latency and leads to inaccurate backtesting results.

Does historical data also use event timestamp?

[nkaz001]

for instance,
1710340597530784 {"stream":"btcusdt@depth@0ms","data":{"e":"depthUpdate","E":1710340597717,"T":1710340597716,"s":"BTCUSDT","U":4171697482390,"u":4171697488761,"pu":4171697482344,"b":[["1000.00","172.609"] ...

[thaaddeus]

historical data also uses event timestamp currently

[nkaz001]

could you add transaction time in the historical data? or could you consider replacing event time with transaction time?

[thaaddeus]

I will consider it, please vote on https://roadmap.tardis.dev/feature-requests