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

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

   Call hash0x644e9248ee170e4d67ad7b82d3231f1307ab51139419796695a1225c3e57d83c

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0xd73f36c62c1090d1590fe7a65407201a2a51e2caff32b295097d7c89a804dc0a

   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 0xe3ba…4956Settlement tx 0xf77c…5783

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 SUI at 3.3761. At the 8h horizon the hyperliquid-mid was 3.3357, which is -120 bps signed to the direction of the call.