AVAX

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":"0xe7dd0463758f293ed80eadadf74555fbfee19bea96c29867aacd7cb297b56bc3","emitter":"scienter.ensemble.v3","asset":"AVAX","side":"long","claimedAt":1786722138,"horizonSeconds":28800}
2. 2

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

   Call hash0xe7dd0463758f293ed80eadadf74555fbfee19bea96c29867aacd7cb297b56bc3

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x6b5d7730440c09db46ff47ee3b02eabf5d0260ce89fe2a8717667b469a313d9d

   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 0x0d8f…620fSettlement tx 0x4b93…24ef

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 AVAX at 30.164. At the 8h horizon the hyperliquid-mid was 29.870, which is -97 bps signed to the direction of the call.