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

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

   Call hash0x3a2b8bc8b0206c6dd69dc902137d8767fa15b31d00da23294d43c2eeea81d88b

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x9faf95004a14cc6bec40db48c4b2b2bdc2e678a58b70fcc45c260616569b84ee

   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 0xa001…0c68Settlement tx 0x5e40…d0f3

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 33.126. At the 8h horizon the hyperliquid-mid was 32.736, which is -118 bps signed to the direction of the call.