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":"0xc48dd9110543d371c220d9fb0b591c96eaba003a2655c07d0528450f2c0f2a81","emitter":"scienter.funding-skew","asset":"ETH","side":"long","claimedAt":1787080446,"horizonSeconds":28800}
2. 2

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

   Call hash0xc48dd9110543d371c220d9fb0b591c96eaba003a2655c07d0528450f2c0f2a81

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0xbd1043f8a1595c824d9382ee0def6615fc5d6a17c1ebf688fb46fc9d5ef13b6e

   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 0xa261…f76bSettlement tx 0xdf0c…78cc

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 long on ETH at 3,192.36. At the 8h horizon the hyperliquid-mid was 3,225.72, which is +104 bps signed to the direction of the call.