Skip to crypto research
Crypto Trading Strategy GuideVenue / Contract / Settlement

Crypto Backtest Data Workbench

Freeze venue history, token membership, product terms and causal data joins. A current crypto directory does not define the universe available in the past.

Your evidence states are not a provider score, audit opinion or performance finding.

0 documented10 unresolved0 not applicable

RECORD 01

Venue coverage

Which exchanges and product versions existed in the evaluation? Current access or liquidity cannot be projected backwards without dated records.

Evidence: Historical venue and product map

RECORD 02

Token membership

What assets were eligible before outcomes appeared? Retain delisted, renamed and failed assets rather than only current survivors.

Evidence: Admission and removal history

RECORD 03

Contract changes

Did multiplier, collateral or settlement terms change? Preserve dated specifications so one symbol does not hide several economic contracts.

Evidence: Product-version timeline

RECORD 04

Timestamp alignment

How do blockchain, vendor and market clocks join? A block timestamp alone does not establish when a labeled feature reached the researcher.

Evidence: Observation and vendor availability

RECORD 05

Wallet revisions

Were address categories assigned retrospectively? A current classification cannot silently become information available to a historical trading decision.

Evidence: Label version and revision dates

RECORD 06

Quote completeness

Which missing, stale and discontinuous quotes remain visible? Filling gaps with convenient prices can create entries that were never observable.

Evidence: Gap log and declared treatment

RECORD 07

Financing data

What dated funding or borrowing observations enter net outcomes? A flat modern assumption should remain hypothetical if historical charges were not supplied.

Evidence: Financing source and convention

RECORD 08

Leakage check

Which transformations and target horizons cross the fit boundary? Venue history is necessary context but does not guarantee a causal experiment.

Evidence: Transform cutoff and label horizon

RECORD 09

Execution model

What order and liquidation assumptions apply to the candidate? Reference returns cannot identify actual exchange fills or account survival.

Evidence: Fill policy and account constraints

RECORD 10

Reproduction scope

Can the preserved inputs regenerate the evaluated universe and outcome? A final chart is not a complete archive or independent replication.

Evidence: Dataset digests and runnable computation

Original source, user evidence record and bounded conclusion
Different evidence objects, not a numerical quality ranking.

Primary reference documents

References support source definitions and mechanisms, not a completed review, measured return or endorsement. The questions are this publication's editorial record design.

A Crypto Backtest Needs the Tokens That Disappeared

Make each reference identify its vintage

The original ten-field workbench records evidence state, reference and notes. A real reference should name venue, product family, historical membership interval, dataset identity and access rights. Preserve source event time separately from availability and account receipt. Current metadata can document present syntax but cannot settle past eligibility. A note that quotes a vendor feature is not a complete historical source. The form's documented count measures the entered record state only, not actual verification, profitable research or deployed production. No field turns a missing crypto archive into an independently validated model.

Bring the outage and settlement packets as exercises

The new JSON packets can illustrate unit and state mistakes without serving as genuine inputs to a financial study. Their prices, costs and relative incident steps are invented. Keep that classification beside every imported note. Actual fill, order and account evidence needs original authentic records with selected contract and quantity scope. A cancelled remainder does not certify a closed position, and a coin valuation is not an executed cash conversion. The workbench remains a source checklist rather than an order reconciler or backtesting engine. It stores no production credential and owns no live data refresh.

Completion remains a separate research obligation

A genuine instrument task goes through the canonical factory and independent master, including the correct asset-class integration. Entry identity is frozen before one selected exit and its financial checks. A component checklist or software pass cannot replace that completion. Missing evidence remains unresolved even if all notes are neatly filled. JSON import identity checks and formula-safe CSV support document handling, not economic certification. Public hosting is managed-cloud owned, with no personal-computer fallback. TODO(Darren): supply licensed eligible crypto data and authentic account scope before any stronger strategy, provider or deployment claim is made.

Filled settlement and outage references