SUI

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":"0x75da10a10d410af0d94d7b494b6c80b8422c71c9f6d73092f9f872ae7aaa07f5","emitter":"scienter.liqmap","asset":"SUI","side":"short","claimedAt":1787004653,"horizonSeconds":28800}
2. 2

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

   Call hash0x75da10a10d410af0d94d7b494b6c80b8422c71c9f6d73092f9f872ae7aaa07f5

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x93da13556c2e1c9351907b101ea41633c0daf7670507da541a6640b24a0666b1

   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 0x8606…48adSettlement tx 0x5675…11c1

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 short on SUI at 3.6532. At the 8h horizon the hyperliquid-mid was 3.6875, which is -94 bps signed to the direction of the call.