ETH

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

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

   Call hash0x565b2c17c97c3abc957a587e0c281500ec248470d8cb572b4b74176e379f6ca9

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0xef465ca68d00162bf145a82f3ffc91d5a6e8b647f2f7a714aa190b6c0a4307cf

   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 0xfba8…38a8Settlement tx 0xbb4d…5b4b

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 ETH at 3,137.16. At the 8h horizon the hyperliquid-mid was 3,144.90, which is +25 bps signed to the direction of the call.