binance / binance/binance-public-data
Clarification Regarding Replay and Backtesting Using Binance Historical Market Data
- Dominant language
- Python
- Stars
- 2.5k
- Forks
- 613
- PR merge metrics
- No merged PRs in 30d
Description
Hello Binance Team,
My name is Kunj, and I am currently developing a trading platform that is still under development.
We are planning to implement historical chart replay and manual backtesting using Binance historical market data (OHLC/Kline data).
Our planned implementation is:
- Use Binance historical market data.
- Store the required historical data to support replay and backtesting.
- Display replay and backtesting only within our authenticated platform.
- Users will not be able to download or access the raw Binance market data.
- We will not provide or redistribute Binance market data as a separate data service or API.
Our planned business model is as follows:
**- Option 1: If Binance's policies permit it, we plan to offer replay and backtesting as part of a paid subscription.
- Option 2: If Binance's policies do not permit charging for replay and backtesting, we plan to make those features available free of charge, while charging only for separate platform features and other tools. Access to Binance market data itself would not be sold separately.**
Before proceeding with development, we would appreciate your guidance on the following:
1. Is Option 1 permitted under Binance's policies?
2. If not, would Option 2 be permitted?
3. Are there any restrictions we should be aware of when implementing replay and backtesting using Binance historical market data?
4. Are there any official guidelines or documentation that apply to this use case?
We want to ensure that our implementation complies with Binance's policies before we proceed.
Thank you for your time and assistance.
Kind regards,
Kunj
Contributor guide
No contributing guide indexed for this repository
Research direction
No file, test, or entry point is identified; the issue requests Binance policy guidance for replay and backtesting with historical OHLC/Kline data. Start by reviewing the repository’s available public-data documentation and the stated use case, then document an authoritative answer covering the paid and free options and any applicable restrictions.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Active
- Clarity
- Needs clarification
- Newbie friendliness
- 15/100