SOL

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

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

   Call hash0x0ee401416185b58728efb7585166a0ea51e7e45b6590758534a34f73ce6b2062

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x3739475b54f05badb6d670fd425f2ecaaccb7d64a3440fe3626f3b6bd5bce998

   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 0xea65…6e53Settlement tx 0xa49b…c9c1

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 SOL at 184.198. At the 8h horizon the hyperliquid-mid was 172.664, which is +626 bps signed to the direction of the call.