OP

Verify this yourself

1. 1

   Take the canonical payload below and hash it. It must equal the call hash — this is what fixes the claim to these exact fields.

   Canonical payload{"callHash":"0xf63777db5124d5d2de7d9620e806250900fcee5acf51f62b5e2f6759d64e7b93","emitter":"scienter.ensemble.v3","asset":"OP","side":"short","claimedAt":1787655082,"horizonSeconds":28800}
2. 2

   Fold the call hash with each sibling in order. The result must equal the batch root the ledger published.

   Call hash0xf63777db5124d5d2de7d9620e806250900fcee5acf51f62b5e2f6759d64e7b93

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x203944fb372bd47c77984ee3cd59d13d27bb4c63f4e46ef41ff5e3669aaf9b9b

   This batch contains 64 calls; 4 siblings is the expected depth.

3. 3

   Read the root out of the Base transaction and compare timestamps. The block must predate the settlement — that is the entire claim.

   Commit tx 0x2c37…21c5Settlement tx 0xcb0b…86f7

What this proves: the call existed, unmodified, before the outcome did. What it does not prove: that the call was good. That is what the backtest and the aggregate on the ledger index are for — and they include the losses.

Outcome

Called short on OP at 1.8915. At the 8h horizon the hyperliquid-mid was 1.8979, which is -34 bps signed to the direction of the call.