BTC

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

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

   Call hash0x08c28ad6909ce280668b8418bbdb9c9c5cd0d384dc018051346a5a93b02d5621

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0xef2e74be4619d84b1a61361199774c31d3b3a5580ef889c8cb087bcb9ad8b121

   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 0xa6a6…7348Settlement tx 0xd89a…6bca

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 BTC at 57,208.39. At the 8h horizon the hyperliquid-mid was 57,533.90, which is +57 bps signed to the direction of the call.