HYPE

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":"0xaf4593fe50fbbcc181720912a0b5f145a9a751739d845bdbadacc06246e09cdf","emitter":"scienter.ensemble.v3","asset":"HYPE","side":"short","claimedAt":1788049112,"horizonSeconds":28800}
2. 2

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

   Call hash0xaf4593fe50fbbcc181720912a0b5f145a9a751739d845bdbadacc06246e09cdf

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0xe4de5cc4714e04af6f73bc31d160d5ab37c25059041798f8a6c680fe1d35fdb2

   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 0xf8c6…9ef3

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.