Risk · 2 min read

What fees and slippage assumptions mean

Published backtest assumptions on every certificate.

Certificates and marketplace surfaces publish separate historical market data and execution profiles, plus what the verification engine applied.

Historical market data (verification): composite Binance archive + Kraken refresh for 1d BTC-USD depth.
Execution profile: Kraken Spot · zero-friction research baseline.
Profile IDs: binance_kraken_composite_ohlcv_v1 (data) and kraken_spot_zero_friction_v1 (execution).
Trading fees: not applied in the current verification baseline unless marked applied on the certificate.
Slippage: not applied in the current verification baseline unless marked applied on the certificate.
Fill model: bar-close simulated fills; not live market microstructure.
Position sizing: fractional equity per trade unless params override.

Live trading economics differ. Treat certificates as diagnostic verification records.

Was this article helpful?

What beginners ask next

Short answers to the question you probably have right now — tap to expand.

I am brand new — where do I start?

Follow Find → Verify → Run: Marketplace, certificate, Studio backtest, optional Runner.

How do I read a certificate?

Start with symbol, timeframe, primary run metrics, assumptions, and trade log — not headline return alone.

I paid but Studio is locked

Check you are signed in with the purchase email, refresh My Strategies, then open Help → billing access.

Certificates · 2 min

The verification dossier: primary run, assumptions, trade log, and reproducibility hashes.

Studio · 3 min

Different windows, params, or cache — how to compare honestly.