binance / binance/binance-public-data

Perp-Kline data Intergrity issue

Open
#395 2 comments 0 reactions 0 assignees View on GitHub
Futures
Dominant language
Python
Stars
2.5k
Forks
612
PR merge metrics
No merged PRs in 30d

Description

Take BTC_USDT as a sample here, UTC 2025-01-29 kline-1m data between [1738113780000,1738114500000] and [1738118460000,1738118640000] volumes are zero. But fapi and website kline chart is not.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by comparing the BTC_USDT kline-1m records for the two UTC 2025-01-29 timestamp ranges with the fapi response and website kline chart referenced in the issue. Trace where the historical data is sourced and determine whether the archived zero volumes are incorrect; done means the discrepancy is explained and the affected data or process is identified for correction.

Written by the indexing model from the issue text.

Assessment

Domain
data
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.