VERIFICATION

Proofline verifies whether a claimed result was real.

Not whether a strategy is good. Whether the record of it is true: that the signal happened when it is said to have happened, that the trade could have filled at that size, that the fees were paid, that the losing days are still in there, and that nothing was quietly changed afterward.

Open Builder →See Proofline records

Verification of a running system is a private pilot today. Submitting does not guarantee acceptance, and nothing on this page is for sale.

What Proofline records

A screenshot shows a number. A record shows the chain that produced it.

Signals: When the rule fired, and on what data it fired.
Orders and fills: What was sent, what came back, and at what price.
Failed and partial orders: The ones that did not fill, and the ones that filled short.
Fees and slippage: What the venue charged, and the gap between the price seen and the price got.
Liquidity: Whether the size the strategy wanted was actually available at that moment.
Observation times: When each price was read, so a decision can be placed against the data that existed then.
Strategy versions: Every change to the rules, and when it took effect.
Settlement and resolution: How the position closed, against the venue's official result.
Corrections and restatements: What was changed after the fact, and why.
Missing data and failures: What could not be observed. This stays visible, never filled in.

What a record preserves

Proofline records the complete chain behind a strategy, not only the trades that worked. It preserves the signal, market state, order path, execution outcome, fees, liquidity, strategy version, settlement rules, corrections, and missing data. That gives Proofline enough evidence to reconstruct execution, trace how the strategy changed, and audit whether the final record matches what actually happened.

Execution-path reconstructionOWNER SURFACE: The complete sequence from signal to order, fill, position, and settlement.; The account that ran the test can open the reconstruction, the record preview and the verification state for that exact run. It is private to that account; a visitor sees a published record's counts and hashes, never its individual events.
Provenance and restatement historyOPERATIONAL: Whether a result came from live trading, paper testing, replay, or imported data, including every correction and limitation.; Corrections are recorded rather than quietly applied, and every published record carries its dataset and report hashes. The full provenance graph behind them is private.
Settlement divergence between venuesMEASURED, NOT A CAPABILITY: Where two venues resolved the same question differently, measured rather than assumed.; One recorded month: two venues settled opposite on 119 of 2,190 windows resolved by both. Recorded per venue and never merged. Cross-venue verification is not supported today.

Proofline does not just preserve the result. It preserves the path that produced it.

How verification works

01
Connect or submit a strategy
A running system, a paper run, a recorded dataset, or the files and code behind an older strategy.
02
Proofline records activity as it happens
Raw responses are stored before anything is normalized, so the original is always recoverable.
03
Deterministic systems calculate the record
Fills, fees, liquidity, settlement and profit and loss are computed by versioned code, not judged. Two independent runs of the same sealed input produce byte-identical output.
04
Missing data and limitations stay visible
Where evidence is absent, the record says so. A gap is never interpolated to make a result look complete.
05
Proofline publishes a sealed, inspectable record
With its dataset hash, fill-model version, limitations and full version history, so someone else can check the work.

Steps two through four are automated. Steps one and five are operated by hand during the pilot. Proofline will not describe this as self-serve until it is.

Where a record can come from

Every record carries its provenance on its face. These are not interchangeable, and Proofline never presents one as another.

Live: Recorded from a running system as it traded.
Paper: Recorded from a running system placing simulated orders against live market data.
Replay: Recomputed from a sealed dataset, reproducible byte for byte.
Imported: Supplied by the operator. Labelled as such, and never presented as verified.

Read the full methodology →

Ready to build something Proofline can test?

Use Builder to define the strategy, resolve missing rules, create a testing plan, and produce the activity Proofline needs to build an honest record.

Builder is where the work happens. This page describes the standard a record is judged against; Builder is how you produce something that can be judged against it.

Open Builder →See the Strategy Handbook

A Proofline record establishes what the evidence supports. It is not investment advice, not a guarantee of future results, and not a certification that a strategy will make money. Read the limitations.