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":"0xcd7d97bd0d1e0804992b2d5f274ba8af6340881476ccdbe8f019e61a4c1639b0","emitter":"scienter.whaletrack","asset":"AVAX","side":"long","claimedAt":1786453334,"horizonSeconds":28800}
2. 2

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

   Call hash0xcd7d97bd0d1e0804992b2d5f274ba8af6340881476ccdbe8f019e61a4c1639b0

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x91061f618b04e0463c064832304f7565da88bcff400daf083e9d74aea50abd69

   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 0xa05c…5eafSettlement tx 0x32ab…bd2f

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