Hunter KillerCreate free account
Menu
loading…
Scored in public · including the misses

The public record of the levels we publish.

Published levels are logged before their outcomes are scored.

Published levels are logged before their outcomes are scored. The record includes misses and simple baselines, including when a baseline does as well or better. Only evidence cleared for public release is shown.

Every scored published level

Complete chronological hit and miss rows for the current provisional window. Released headline figures stay separate.

Loading the complete scored row record…

Newest listed miss

Misses included: reached and missed levels both stay in the record. Dated record status

Recorded liquidations around a touched served wall

Loading the recorded dollars

Data age unavailable. A dated snapshot of recorded dollars is not available.

Public data is at least 2 hours behind. Missing evidence is never counted as zero.

Method

The first complete 15 minute bar after a wall was served that spans its price opens a one hour window. Recorded dollars use the frozen wall band and position side across the registered venues, with repeats excluded. Each event belongs to at most one episode. Both dollar totals include only complete, attested episodes. Gaps remain unresolved. These observations do not establish causation.

A liquidation map estimates where leveraged positions could be forced closed. Published-level outcomes and the historical band-containment backtest answer different questions. The backtest measures whether price stayed inside a band, rather than whether a published level was reached.

Every miss, listed

Loading the scored record. See the dated record status.

More

More records as they score.

Sealed daily: why we anchor this record cryptographically

a new seal is appended every day

Every day, the complete record ledger and outcome journals behind this page are canonicalized and hashed with SHA-256, and each day's seal includes the previous day's seal: a hash chain, the standard construction behind append-only audit logs.

Why it matters: a track record the vendor can edit after the fact is marketing, not evidence. With the chain, any retroactive edit to the history (one character, by anyone, including us) breaks every seal written after it, and anyone holding a copy of the chain can prove it. We cannot quietly rewrite a bad week.

Check it yourself: the full chain is public as machine-readable JSON at /proof/anchors, and the payload itself embeds the exact step-by-step verification recipe (canonicalization, digest, and chain rule), so re-checking every seal needs nothing but a copy of the chain and a SHA-256 implementation. The chain lets anyone check whether the retained history has changed.

How we verify