DOGE

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":"0x146d6ebe3a2782a939729bb2d506ae962a7e3978635fce6f68a45f3a91fce032","emitter":"scienter.whaletrack","asset":"DOGE","side":"short","claimedAt":1785672623,"horizonSeconds":28800}
2. 2

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

   Call hash0x146d6ebe3a2782a939729bb2d506ae962a7e3978635fce6f68a45f3a91fce032

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0xec521d81397750dad396ea21f310b5de64c3fc3edbe2b4ee8f406c5aed39768e

   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 0x569c…45efSettlement tx 0xb42f…edd2

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 DOGE at 0.13771. At the 8h horizon the hyperliquid-mid was 0.13671, which is +73 bps signed to the direction of the call.