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

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

   Call hash0x118cc7a1a72cb1a949acba60cbcb8b3d02f6d65e619cf04c8f2de002fc4465f1

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x582857dd482c9ba0ee0a06dd2cefa2e49285396e433f7f5bf8b9d63bec96e4f5

   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 0xb60d…8bd1Settlement tx 0xe48b…3ad7

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