Recompute the seal yourself.

Paste a signal_id or full commit_hash_sha256 below. This page fetches signal_commits.jsonl, finds the matching commit, and recomputes the SHA-256 digest of its canonical_payload in your browser via crypto.subtle.digest — no OIN backend involved. If the digest matches the published hash, the observation's content is cryptographically locked to that commit; its timing is proven once the day's Bitcoin anchor confirms (see the anchor box below).

We sell verifiable receipts and lead-time — not predictions. For the sharp who builds their own models and needs raw, early, KYC-free data with proof of when it existed. Not for copy-traders.

How it works

1. Fetches signal_commits.jsonl from this server (one JSON commit per line).
2. Locates the line whose signal_id OR commit_hash_sha256 matches your query.
3. Canonicalizes canonical_payload using sorted keys, no whitespace, ASCII-escaped non-ASCII (byte-identical to Python's json.dumps(payload, sort_keys=True, separators=(',', ':'))).
4. Computes SHA-256 via the browser-native WebCrypto API.
5. Compares against the published commit_hash_sha256.

Why this matters

Any track-record claim is trivial to fake post-hoc; we make no validated edge claim — we seal every call before resolution so you can grade it yourself. A SHA-256 commit-reveal over an append-only log makes editing a sealed call detectable: the observation's content is locked in BEFORE the outcome is known, and you can recompute it here without trusting the OIN backend.

What this proves — and what it doesn't

• Proven: a call's content (market, direction, entry) matches its published hash, and existed at the recorded commit time.
• Tamper-evidence chain (forward-only, from 2026-06-03): each new commit seals the previous commit's hash via prev_commit_hash, so inserting or deleting any commit after the chain began breaks the walk — click Verify Chain above. Commits sealed before the chain began are independent anchors (their integrity rests on the per-commit SHA-256 + the Bitcoin anchor, not the chain).
• External anchor (LIVE — OpenTimestamps → Bitcoin): the entire append-only corpus is committed to Bitcoin daily via OpenTimestamps (free, no wallet) — see the Bitcoin-anchor box above. Confirmations land within ~1–24h; until a given day's anchor is Bitcoin-confirmed, treat that day's committed_at_utc as self-reported. (EAS-on-Base attestation remains a separate, not-yet-live track.)
• Disclosed selection: this public corpus is the deduplicated, directional, market-bearing subset of a larger raw signal firehose — the inclusion rule is deterministic (drop null, duplicate, and non-directional rows). A sample of the public corpus is therefore a curated cohort, not the full firehose; the raw log is available on request.
• Outcome grading is OIN-computed by matching market text to resolved outcomes; commits do not yet carry a Polymarket condition_id, so resolution is not yet independently reproducible on-chain. The seal proves the observation's timing, not the outcome label.

Append-only commit log generated by services/manifold_mirror.py. This verifier is a single static HTML file with no external dependencies.