ARB

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

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

   Call hash0xca59301ec997f01f13c8af481c327412dcf9408579208f0dcf2e03785ec9e1c4

   Sibling 00x9e3779b1aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 10x13c6ef362aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 20x1daa66d13aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Sibling 30x278dde6c4aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa

   Batch root0x0ec47b57bf9f6be66699a767ac005337f32bc9705896b3cf5c98c6e6d5e84c72

   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 0x9ddb…baeb

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.