binance / binance/binance-public-data
Clarification requested: historical Spot symbol manifest and daily kline archive boundaries
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 613
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I am documenting a reproducible historical research dataset using Binance Public Data and would appreciate clarification on two archive properties.
1. Historical Spot symbol completeness
Does Binance publish, or retain through an official interface, a complete historical manifest of Binance Spot markets as of a specified date?
Specifically, I need the complete set of Spot markets quoted in USDT as of 2019-09-02 00:00:00 UTC, including symbols that may later have been delisted, renamed, migrated, or removed from current exchangeInfo.
The current exchangeInfo endpoint and the repository’s symbol-discovery helpers appear to return current running symbols. Is there an official dated manifest, historical exchangeInfo snapshot, archive index, or other Binance-controlled record suitable for reconstructing the complete historical symbol set?
2. Daily Spot kline archive containment
For a daily Spot kline archive such as:
data/spot/daily/klines/{SYMBOL}/1d/{SYMBOL}-1d-{YYYY-MM-DD}.zip
is it guaranteed that every included kline has an open timestamp in the half-open UTC interval:
[YYYY-MM-DD 00:00:00 UTC, next day 00:00:00 UTC)
For the 1d interval, is the archive expected to contain exactly one kline whose open timestamp is the named date at 00:00:00 UTC?
I understand that the companion CHECKSUM verifies file integrity. I am asking separately whether the UTC-day containment and one-row 1d semantics are formally guaranteed by the archive-generation process.
A link to authoritative documentation, archive-generation code, or a maintainer statement covering these points would be greatly appreciated.
Thank you.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the current exchangeInfo endpoint, the repository’s symbol-discovery helpers, and the documented data/spot/daily/klines/{SYMBOL}/1d archive path. Check whether the repository exposes archive-generation code or authoritative documentation for historical symbol snapshots, UTC-day containment, and one-row 1d semantics. Done means linking authoritative sources or recording a maintainer-confirmed answer for both questions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- data, documentation
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100