Verify

The fixture record below is relayed. The judge path stores the same numbers from the fixture through submit_pnl, so anyone can recompute them.

Contract alpha-keys.testnet · explorer transaction

window7d

pnl_usd_e68000000

max_dd_bps10

sharpe_e4108098

n_trades2

equity_usd_e61008000000

code hash relayed-demo

input hash fixture

Flip one byte

The published digest is sha256 of the fixture line below. The check reads that line again. One flipped byte makes the digest disagree.

7d|8000000|10|108098|2|1008000000|relayed-demo|fixture

Check the record, then flip one byte.

Reproduce the published digest: printf '%s' '7d|8000000|10|108098|2|1008000000|relayed-demo|fixture' | sha256sum

Reproduce the metrics

make demo-seed

You see the same pnl, drawdown, and Sharpe printed as JSON, then the delayed events.

Reproduce a WASM hash

./scripts/build-worker.sh

You see wasm sha256 cb9c3130c6858cf4b460950281cff3468eabc0d79f1652fb05061c7fe41978dd. That is the third field of get_config. The relayed fixture hash is the label relayed-demo, not a WASM digest.