LINK

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":"0xeb32f2d09acafd65841bac089633c670c34b8cbb9d42fc8bea1dd0e2da41c79a","emitter":"scienter.ensemble.v3","asset":"LINK","side":"long","claimedAt":1786796957,"horizonSeconds":28800}
2. 2

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

   Call hash0xeb32f2d09acafd65841bac089633c670c34b8cbb9d42fc8bea1dd0e2da41c79a

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0xa5b791354138c2dfc9ab4e51ba65e8b317f6464afe6331d88d48c6a952ade82e

   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 0x2f9c…7c18Settlement tx 0x4529…60f2

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 LINK at 18.393. At the 8h horizon the hyperliquid-mid was 19.081, which is +374 bps signed to the direction of the call.