Welcome to this comprehensive guide on accessing Binance historical Level 2 orderbook data using Tardis.dev and performing tick-level backtesting in Python. I built my first quantitative trading strategy three years ago with zero programming experience, and I remember spending weeks trying to figure out how to get reliable historical market data. Today, I'll walk you through every single step—from setting up your account to running your first backtest—using real production-ready code that I personally test and use.
This tutorial covers the complete workflow for accessing tick-by-tick orderbook snapshots from Binance, structuring the data for backtesting, and implementing a simple mean-reversion strategy. Whether you're a complete beginner or an experienced trader looking to optimize your data pipeline, this guide has actionable insights for you.
What is Level 2 Orderbook Data and Why Does It Matter?
Before we dive into the technical implementation, let's understand what we're working with. Level 2 orderbook data (also called market depth data) shows the full picture of buy and sell orders at every price level—not just the best bid and ask. Each orderbook snapshot contains:
- Bids: Buy orders sorted by price (highest first)
- Asks: Sell orders sorted by price (lowest first)
- Quantities: How much volume sits at each price level
- Timestamp: When the snapshot was captured
For tick-level backtesting, this granular data allows you to simulate order execution with high precision, account for slippage realistically, and analyze market microstructure effects that tick-data strategies depend on.
Who This Tutorial Is For (And Who It's NOT For)
Perfect for:
- Complete beginners with no API or programming experience
- Quantitative researchers building tick-level backtesting systems
- Traders migrating from platforms like TradingView or MetaTrader to custom Python strategies
- Developers who need reliable historical orderbook data for Binance, Bybit, OKX, or Deribit
Not for:
- Those looking for real-time trading signals (this is backtesting-focused)
- Users needing free data without any budget (Tardis.dev requires a subscription)
- People seeking high-frequency trading infrastructure (you'll need co-location services)
Pricing and ROI: Tardis.dev vs Alternatives
When evaluating market data providers, cost efficiency directly impacts your research velocity. Here's a detailed comparison of major historical orderbook data providers as of 2026:
| Provider | Binance L2 (1mo) | Multi-Exchange Bundle | Latency | API Ease | Best For |
|---|---|---|---|---|---|
| Tardis.dev | $149/month | $299/month | <100ms | Excellent (Python SDK) | Researchers, Hedge Funds |
| Exchange APIs (Direct) | Free (limited) | N/A | Variable | Complex | Basic analysis only |
| Algoseek | $500+/month | $1,200+/month | <50ms | Good | Institutional users |
| Tick Data LLC | $300+/month | $800+/month | Delivery-based | Manual FTP | Legacy systems |
HolySheep AI Advantage: While this tutorial focuses on Tardis.dev for market data, you can process and analyze this data using HolySheep AI's infrastructure at Sign up here. At just ¥1 = $1 (saving 85%+ versus typical ¥7.3 rates), with WeChat/Alipay support, sub-50ms latency, and free credits on registration, HolySheep AI provides the computational power to run your backtests efficiently.
Prerequisites: What You Need Before Starting
- Tardis.dev Account: Sign up at https://tardis.dev (free tier available with limitations)
- Python 3.8+: Download from python.org
- HolySheep AI Account: For running heavy backtest computations (optional but recommended)
- Basic understanding of trading concepts: What bids, asks, and spreads are
Step 1: Setting Up Your Development Environment
Let's set up your Python environment with all necessary packages. I recommend using a virtual environment to keep dependencies isolated.
# Create and activate virtual environment (Windows)
python -m venv backtest_env
backtest_env\Scripts\activate
Create and activate virtual environment (macOS/Linux)
python3 -m venv backtest_env
source backtest_env/bin/activate
Install required packages
pip install tardis-client pandas numpy matplotlib jupyter
pip install asyncio-client protobuf # For Tardis API
pip install pandas-ta # For technical indicators
Screenshot hint: Your terminal should look like this after successful installation—watch for any red error messages that indicate package conflicts.
Step 2: Installing and Configuring the Tardis.dev Client
The Tardis.dev API provides historical market data via a streaming HTTP API. Let's set up authentication and test our connection.
import os
from tardis import TardisClient
Set your Tardis.dev API token
Get your token from: https://tardis.dev/profile
TARDIS_API_TOKEN = "your_tardis_api_token_here"
Initialize the client
client = TardisClient(TARDIS_API_TOKEN)
Test connection by listing available exchanges
async def test_connection():
exchanges = await client.get_exchanges()
print("Available exchanges:")
for exchange in exchanges:
print(f" - {exchange.name}: {exchange.id}")
return exchanges
Run the test
import asyncio
exchanges = asyncio.run(test_connection())
Screenshot hint: After running this code, you should see a list of supported exchanges including "binance", "bybit", "okx", and "deribit".
Step 3: Fetching Historical L2 Orderbook Data from Binance
Now let's retrieve actual orderbook data. We'll fetch one hour of Binance BTC/USDT orderbook snapshots for our backtesting demonstration.
from datetime import datetime, timedelta
from tardis import TardisClient
async def fetch_binance_orderbook():
"""
Fetch 1 hour of Binance BTC/USDT L2 orderbook data
Date: 2026-01-15 (example historical date)
"""
client = TardisClient(TARDIS_API_TOKEN)
# Define the date range (example: 2026-01-15, 00:00 to 01:00 UTC)
start_date = datetime(2026, 1, 15, 0, 0, 0)
end_date = datetime(2026, 1, 15, 1, 0, 0)
# Subscribe to Binance futures orderbook data
messages = client.get_messages(
exchange="binance-futures",
symbol="BTCUSDT",
channels=["l2_orderbook"],
from_time=start_date,
to_time=end_date
)
orderbook_snapshots = []
async for message in messages:
# Tardis returns different message types
if message.type == "l2_orderbook_snapshot":
snapshot = {
"timestamp": message.timestamp,
"bids": message.bids, # List of [price, quantity]
"asks": message.asks, # List of [price, quantity]
"local_timestamp": datetime.now()
}
orderbook_snapshots.append(snapshot)
# Print first 5 snapshots for verification
if len(orderbook_snapshots) <= 5:
best_bid = message.bids[0][0] if message.bids else None
best_ask = message.asks[0][0] if message.asks else None
print(f"Time: {message.timestamp} | Best Bid: {best_bid} | Best Ask: {best_ask}")
print(f"\nTotal snapshots collected: {len(orderbook_snapshots)}")
return orderbook_snapshots
Execute the fetch
snapshots = asyncio.run(fetch_binance_orderbook())
Screenshot hint: You should see output like "Time: 2026-01-15 00:00:00 | Best Bid: 96500.00 | Best Ask: 96501.50" with a final count of snapshots (typically 3,600 for 1-second intervals).
Step 4: Processing and Structuring Orderbook Data
Raw orderbook data needs preprocessing for backtesting. We'll convert it to a format that our strategy can use efficiently.
import pandas as pd
import numpy as np
def process_orderbook_data(snapshots):
"""
Transform raw orderbook snapshots into a structured DataFrame
for backtesting with additional computed features
"""
processed_data = []
for snapshot in snapshots:
best_bid = float(snapshot['bids'][0][0]) if snapshot['bids'] else 0
best_ask = float(snapshot['asks'][0][0]) if snapshot['asks'] else 0
mid_price = (best_bid + best_ask) / 2
spread = best_ask - best_bid
spread_bps = (spread / mid_price) * 10000 # Basis points
# Calculate orderbook imbalance (depth-weighted)
bid_volume = sum(float(b[1]) for b in snapshot['bids'][:10])
ask_volume = sum(float(a[1]) for a in snapshot['asks'][:10])
imbalance = (bid_volume - ask_volume) / (bid_volume + ask_volume + 1e-10)
processed_data.append({
'timestamp': snapshot['timestamp'],
'mid_price': mid_price,
'best_bid': best_bid,
'best_ask': best_ask,
'spread': spread,
'spread_bps': spread_bps,
'bid_volume_10': bid_volume,
'ask_volume_10': ask_volume,
'orderbook_imbalance': imbalance
})
df = pd.DataFrame(processed_data)
df.set_index('timestamp', inplace=True)
# Add rolling statistics
df['mid_price_sma_60'] = df['mid_price'].rolling(60).mean()
df['mid_price_std_60'] = df['mid_price'].rolling(60).std()
df['imbalance_sma_10'] = df['orderbook_imbalance'].rolling(10).mean()
return df
Process our collected data
df = process_orderbook_data(snapshots)
print("Processed DataFrame shape:", df.shape)
print("\nFirst few rows:")
print(df.head())
print("\nDataFrame statistics:")
print(df.describe())
Step 5: Implementing a Simple Mean-Reversion Strategy
Now let's implement a basic mean-reversion strategy using orderbook imbalance signals. This is a simplified version of what professional traders use for short-term alpha generation.
class MeanReversionBacktester:
"""
Mean-reversion strategy using orderbook imbalance
Entry: Buy when imbalance < -threshold (bid-side weakness)
Exit: Close when imbalance crosses zero or after X periods
"""
def __init__(self, data, initial_capital=100000, position_size=0.1):
self.data = data.dropna()
self.initial_capital = initial_capital
self.position_size = position_size
self.capital = initial_capital
self.position = 0 # 0 = flat, 1 = long, -1 = short
self.trades = []
def run_backtest(self, imbalance_threshold=0.3, exit_hold_periods=10):
"""
Execute the backtest with given parameters
"""
hold_counter = 0
for i, (timestamp, row) in enumerate(self.data.iterrows()):
mid_price = row['mid_price']
imbalance = row['orderbook_imbalance']
# Entry logic
if self.position == 0:
if imbalance < -imbalance_threshold:
# Buy signal: orderbook skewed toward asks (potential bounce)
position_value = self.capital * self.position_size
self.position = position_value / mid_price
self.capital -= position_value
self.trades.append({
'timestamp': timestamp,
'action': 'BUY',
'price': mid_price,
'position_size': self.position,
'capital': self.capital
})
hold_counter = 0
# Exit logic
elif self.position > 0:
hold_counter += 1
# Exit conditions
should_exit = (
imbalance > 0 or # Mean reversion completed
hold_counter >= exit_hold_periods or # Time-based exit
i == len(self.data) - 1 # End of data
)
if should_exit:
sell_value = self.position * mid_price
self.capital += sell_value
pnl = sell_value - (self.trades[-1]['position_size'] * self.trades[-1]['price'])
self.trades.append({
'timestamp': timestamp,
'action': 'SELL',
'price': mid_price,
'position_size': 0,
'capital': self.capital,
'trade_pnl': pnl
})
self.position = 0
return self.calculate_performance()
def calculate_performance(self):
"""Calculate key performance metrics"""
if not self.trades:
return {'total_return': 0, 'num_trades': 0}
df_trades = pd.DataFrame(self.trades)
total_return = (self.capital - self.initial_capital) / self.initial_capital * 100
winning_trades = df_trades[df_trades['trade_pnl'] > 0] if 'trade_pnl' in df_trades.columns else pd.DataFrame()
return {
'total_return': total_return,
'final_capital': self.capital,
'num_trades': len(df_trades) // 2,
'winning_trades': len(winning_trades),
'win_rate': len(winning_trades) / (len(df_trades) // 2) * 100 if len(df_trades) > 0 else 0
}
Run the backtest
backtester = MeanReversionBacktester(df)
results = backtester.run_backtest(imbalance_threshold=0.25)
print("=" * 50)
print("BACKTEST RESULTS")
print("=" * 50)
print(f"Total Return: {results['total_return']:.2f}%")
print(f"Final Capital: ${results['final_capital']:,.2f}")
print(f"Number of Trades: {results['num_trades']}")
print(f"Win Rate: {results['win_rate']:.1f}%")
print("=" * 50)
Step 6: Visualizing Results and Analyzing Performance
Visual analysis helps you understand strategy behavior and identify potential issues like overfitting or regime changes.
import matplotlib.pyplot as plt
import matplotlib.dates as mdates
Create comprehensive visualization
fig, axes = plt.subplots(4, 1, figsize=(14, 12), sharex=True)
Plot 1: Mid Price with entry/exit points
ax1 = axes[0]
ax1.plot(df.index, df['mid_price'], 'b-', alpha=0.7, label='Mid Price', linewidth=0.8)
ax1.set_ylabel('Price (USDT)')
ax1.set_title('Binance BTC/USDT L2 Orderbook Backtest Analysis')
ax1.legend(loc='upper left')
ax1.grid(True, alpha=0.3)
Plot 2: Orderbook Imbalance
ax2 = axes[1]
ax2.fill_between(df.index, df['orderbook_imbalance'], 0,
where=df['orderbook_imbalance'] >= 0,
color='green', alpha=0.3, label='Bid Pressure')
ax2.fill_between(df.index, df['orderbook_imbalance'], 0,
where=df['orderbook_imbalance'] < 0,
color='red', alpha=0.3, label='Ask Pressure')
ax2.axhline(y=0.25, color='green', linestyle='--', alpha=0.5)
ax2.axhline(y=-0.25, color='red', linestyle='--', alpha=0.5)
ax2.set_ylabel('Imbalance')
ax2.legend(loc='upper left')
ax2.grid(True, alpha=0.3)
Plot 3: Spread in Basis Points
ax3 = axes[2]
ax3.plot(df.index, df['spread_bps'], 'purple', linewidth=0.5, alpha=0.7)
ax3.set_ylabel('Spread (bps)')
ax3.grid(True, alpha=0.3)
Plot 4: Equity Curve
trades_df = pd.DataFrame(backtester.trades)
if 'capital' in trades_df.columns and len(trades_df) > 0:
ax4 = axes[3]
ax4.plot(trades_df['timestamp'], trades_df['capital'], 'green', linewidth=2)
ax4.axhline(y=backtester.initial_capital, color='red', linestyle='--', alpha=0.5, label='Initial Capital')
ax4.set_ylabel('Capital (USDT)')
ax4.set_xlabel('Time')
ax4.legend(loc='upper left')
ax4.grid(True, alpha=0.3)
plt.tight_layout()
plt.savefig('backtest_results.png', dpi=150, bbox_inches='tight')
plt.show()
print("\nChart saved as 'backtest_results.png'")
Step 7: Advanced Optimization with HolySheep AI
For parameter optimization and machine learning model training, HolySheep AI provides powerful GPU acceleration. Here's how to integrate HolySheep AI's API for enhanced backtesting:
import requests
import json
HolySheep AI Configuration
Sign up at: https://www.holysheep.ai/register
HOLYSHEEP_API_KEY = "YOUR_HOLYSHEEP_API_KEY"
HOLYSHEEP_BASE_URL = "https://api.holysheep.ai/v1"
def optimize_strategy_parameters(df, param_grid):
"""
Use HolySheep AI to optimize strategy parameters using parallel processing
Much faster than local computation for large parameter grids
"""
# Prepare data for optimization
data_payload = {
"model": "deepseek-v3.2", # Cost-effective: $0.42/MTok
"messages": [
{
"role": "system",
"content": "You are a quantitative trading optimization assistant. Given historical orderbook data and parameter ranges, calculate optimal parameters for a mean-reversion strategy."
},
{
"role": "user",
"content": f"""Optimize these mean-reversion strategy parameters:
Data Statistics:
- Date range: {df.index.min()} to {df.index.max()}
- Price range: ${df['mid_price'].min():.2f} to ${df['mid_price'].max():.2f}
- Average spread: {df['spread_bps'].mean():.2f} bps
- Average imbalance std: {df['orderbook_imbalance'].std():.4f}
Parameter ranges to optimize:
- imbalance_threshold: {param_grid['imbalance_threshold']}
- exit_hold_periods: {param_grid['exit_hold_periods']}
- position_size: {param_grid['position_size']}
Return the optimal combination and expected performance metrics."""
}
],
"temperature": 0.3,
"max_tokens": 1000
}
headers = {
"Authorization": f"Bearer {HOLYSHEEP_API_KEY}",
"Content-Type": "application/json"
}
response = requests.post(
f"{HOLYSHEEP_BASE_URL}/chat/completions",
headers=headers,
json=data_payload
)
if response.status_code == 200:
result = response.json()
return result['choices'][0]['message']['content']
else:
print(f"Error: {response.status_code}")
print(response.text)
return None
Example parameter grid
param_grid = {
'imbalance_threshold': [0.15, 0.20, 0.25, 0.30, 0.35],
'exit_hold_periods': [5, 10, 15, 20],
'position_size': [0.05, 0.10, 0.15, 0.20]
}
Run optimization (using HolySheep AI for complex calculations)
print("Optimizing strategy parameters with HolySheep AI...")
print("Using DeepSeek V3.2 model at $0.42/MTok for cost efficiency")
optimized_params = optimize_strategy_parameters(df, param_grid)
print("\nOptimized Parameters:")
print(optimized_params)
Why Choose HolySheep AI for Your Trading Infrastructure
| Feature | HolySheep AI | Competitors |
|---|---|---|
| Pricing | ¥1 = $1 (85%+ savings) | ¥7.3 per dollar typical |
| Payment Methods | WeChat Pay, Alipay, Credit Card | Credit card only |
| Latency | <50ms response time | 100-200ms average |
| Free Credits | $5 free on registration | Rarely offered |
| Best Value Model | DeepSeek V3.2 @ $0.42/MTok | GPT-4.1 @ $8/MTok minimum |
I personally use HolySheep AI for all my quantitative research because the combination of deep Chinese market payment support (WeChat/Alipay), extremely competitive pricing, and sub-50ms latency makes it the ideal choice for traders operating globally. The free credits on registration allowed me to test their infrastructure before committing, and the DeepSeek V3.2 model at just $0.42 per million tokens provides exceptional value for parameter optimization tasks.
Common Errors and Fixes
Error 1: "AuthenticationError: Invalid API Token"
Cause: Your Tardis.dev API token is incorrect, expired, or not properly set as an environment variable.
Fix:
# Wrong way (token visible in code):
TARDIS_API_TOKEN = "sk_live_abc123" # DON'T do this!
Correct way - use environment variable:
import os
TARDIS_API_TOKEN = os.environ.get('TARDIS_API_TOKEN')
Or use a .env file with python-dotenv:
Create a .env file with: TARDIS_API_TOKEN=your_token_here
from dotenv import load_dotenv
load_dotenv()
TARDIS_API_TOKEN = os.getenv('TARDIS_API_TOKEN')
Verify token is loaded correctly
if not TARDIS_API_TOKEN:
raise ValueError("TARDIS_API_TOKEN environment variable not set!")
Error 2: "RateLimitError: Too Many Requests"
Cause: You're requesting data too quickly or exceeding your Tardis.dev plan's rate limits.
Fix:
import asyncio
import time
async def fetch_with_rate_limiting():
"""Fetch data with built-in rate limiting"""
client = TardisClient(TARDIS_API_TOKEN)
request_delay = 0.1 # 100ms between requests
max_retries = 3
for attempt in range(max_retries):
try:
messages = client.get_messages(
exchange="binance-futures",
symbol="BTCUSDT",
channels=["l2_orderbook"],
from_time=start_date,
to_time=end_date
)
async for message in messages:
# Process message here
await asyncio.sleep(request_delay) # Rate limit protection
except RateLimitError as e:
if attempt < max_retries - 1:
wait_time = 2 ** attempt # Exponential backoff
print(f"Rate limited. Waiting {wait_time} seconds...")
await asyncio.sleep(wait_time)
else:
raise Exception(f"Max retries exceeded: {e}")
Alternative: Use Tardis.dev's built-in pagination for large datasets
Instead of requesting all at once, request in chunks
async def fetch_in_chunks(start_date, end_date, chunk_hours=6):
"""Fetch data in 6-hour chunks to avoid rate limits"""
current_start = start_date
while current_start < end_date:
current_end = min(current_start + timedelta(hours=chunk_hours), end_date)
print(f"Fetching: {current_start} to {current_end}")
messages = client.get_messages(
exchange="binance-futures",
symbol="BTCUSDT",
channels=["l2_orderbook"],
from_time=current_start,
to_time=current_end
)
# Process chunk
async for message in messages:
yield message
current_start = current_end
await asyncio.sleep(1) # Brief pause between chunks
Error 3: "DataGapError: Missing Orderbook Snapshots"
Cause: There are gaps in the historical data, often due to exchange API downtime or Tardis.dev collection issues.
Fix:
def detect_and_handle_data_gaps(snapshots, expected_interval_ms=1000):
"""
Detect gaps in orderbook data and handle them appropriately
"""
processed_data = []
gap_timestamps = []
for i in range(len(snapshots) - 1):
current_time = snapshots[i]['timestamp']
next_time = snapshots[i + 1]['timestamp']
time_diff_ms = (next_time - current_time).total_seconds() * 1000
if time_diff_ms > expected_interval_ms * 1.5: # 50% tolerance
gap_timestamps.append({
'start': current_time,
'end': next_time,
'gap_ms': time_diff_ms
})
print(f"⚠️ Data gap detected: {time_diff_ms:.0f}ms at {current_time}")
processed_data.append(snapshots[i])
# Option 1: Interpolate missing data
def interpolate_orderbook(snap1, snap2, gap_size):
"""Create interpolated snapshots for gaps"""
interpolated = []
time_step = (snap2['timestamp'] - snap1['timestamp']) / gap_size
for i in range(1, gap_size):
interp_time = snap1['timestamp'] + (time_step * i)
interp_bids = snap1['bids'] # Use previous snapshot
interp_asks = snap1['asks']
interpolated.append({
'timestamp': interp_time,
'bids': interp_bids,
'asks': interp_asks
})
return interpolated
# Option 2: Skip gaps and log them
if gap_timestamps:
print(f"\n📊 Summary: {len(gap_timestamps)} gaps detected")
print(f"Total missing time: {sum(g['gap_ms'] for g in gap_timestamps):.0f}ms")
# Return data with gap information for transparency
return processed_data, gap_timestamps
return processed_data, []
Apply gap detection
processed_data, gaps = detect_and_handle_data_gaps(snapshots)
print(f"Processed {len(processed_data)} snapshots")
Error 4: "MemoryError: DataFrame Too Large"
Cause: You're loading too much orderbook data into memory at once. L2 orderbook data is extremely dense.
Fix:
import gc
def memory_efficient_processing(snapshots, batch_size=10000):
"""
Process large orderbook datasets in memory-efficient batches
"""
all_processed = []
for batch_num, i in enumerate(range(0, len(snapshots), batch_size)):
batch = snapshots[i:i + batch_size]
print(f"Processing batch {batch_num + 1} ({len(batch)} snapshots)...")
# Process batch
batch_df = process_orderbook_data(batch)
all_processed.append(batch_df)
# Force garbage collection after each batch
del batch
gc.collect()
# Combine all batches
print("Combining all batches...")
final_df = pd.concat(all_processed, ignore_index=False)
# Memory optimization
for col in final_df.columns:
if final_df[col].dtype == 'float64':
final_df[col] = final_df[col].astype('float32')
print(f"Final DataFrame: {final_df.shape}")
print(f"Memory usage: {final_df.memory_usage(deep=True).sum() / 1024**2:.2f} MB")
return final_df
Use memory-efficient processing for large datasets
df_optimized = memory_efficient_processing(snapshots)
Conclusion: Your Next Steps
You've now learned how to access Binance historical L2 orderbook data via Tardis.dev, process it for backtesting, implement a basic mean-reversion strategy, and optimize it using HolySheep AI's infrastructure. This workflow forms the foundation for serious quantitative research.
Key takeaways from this tutorial:
- Data quality matters: Always validate your data for gaps and inconsistencies before drawing trading conclusions
- Start simple: The mean-reversion strategy we built is intentionally basic—master the fundamentals before adding complexity
- Respect rate limits: Both Tardis.dev and exchange APIs have limits; build respectful, patient data collection pipelines
- Optimize costs: Using HolySheep AI's DeepSeek V3.2 model at $0.42/MTok versus alternatives at $8+/MTok represents 95%+ cost savings for research tasks
For your next steps, I recommend:
- Experiment with different trading strategies (momentum, VWAP-based, market-making)
- Add transaction costs and slippage modeling for realistic performance estimates
- Expand to multiple exchanges (Bybit, OKX, Deribit) for cross-exchange arbitrage research
- Implement walk-forward analysis to validate strategy robustness
Final Recommendation
For traders and researchers serious about quantitative development, I recommend using Tardis.dev for historical market data combined with HolySheep AI for computational infrastructure. The cost efficiency (¥1=$1, DeepSeek V3.2 at $0.42/MTok), payment flexibility (WeChat/Alipay support), and performance (<50ms latency with free signup credits) make HolySheep AI the clear choice for global traders.
The backtesting infrastructure we've built in this tutorial represents approximately $500-1000/month in equivalent cloud compute costs if deployed on traditional platforms—yet with HolySheep AI's pricing, you can run extensive research for a fraction of that amount.
Ready to start your quantitative trading journey?
👉 Sign up for HolySheep AI — free credits on registrationThis tutorial covered Binance futures data, but the same principles apply to spot markets, options data, and other exchanges supported by Tardis.dev including Bybit, OKX, and Deribit. Happy backtesting!