ETH

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":"0x608548794fdc3fafc61db37a7b779c82d7b56a60f1aafbdf5be19dbe3ade0dda","emitter":"scienter.ensemble.v3","asset":"ETH","side":"short","claimedAt":1787709591,"horizonSeconds":28800}
2. 2

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

   Call hash0x608548794fdc3fafc61db37a7b779c82d7b56a60f1aafbdf5be19dbe3ade0dda

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x3a2b7ec5d21449e5719953c57d3bc9789f6c621ca5ccc592fe1a2d621673dbbc

   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 0x6298…93dcSettlement tx 0x6b0e…ee3e

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 ETH at 3,303.88. At the 8h horizon the hyperliquid-mid was 3,325.19, which is -64 bps signed to the direction of the call.