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

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

   Call hash0xbc0b6a01255fd10eb271dd561cccb6f49a309e72cca3551c0776996ff62ecb3d

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x2dc9fc49acfac7d62f304be809c61fbf0f31a98d18e8a750920008ec6023f541

   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 0x1cbb…fcb1Settlement tx 0x33c8…a87c

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