Provably not backdated

Anchored track record

Every on-chain analytics site can quietly backfill a track record after the fact. This one can't. Each day's signal verdict is written to an append-only, hash-chained log (altering any past entry breaks every later hash) and anchored to the Bitcoin blockchain via OpenTimestamps— so each entry's timestamp is provable, not trusted. The .ots proof for every day is published alongside its record; run ots verify <date>.json.ots to confirm the Bitcoin block it was timestamped in. You can also re-verify the entire hash chain right here, in your browser.

Verifying chain…0 Bitcoin-anchored
How to verify independently
  1. Download /data/signal_log.jsonl.
  2. Each entry's hash = SHA-256(prev_hash + canonical JSON of the entry). Recompute to confirm the chain.
  3. For any day, fetch its .ots proof and run ots verify <date>.json.ots — OpenTimestamps confirms the Bitcoin block (and time) the hash was anchored in.

Loading…

Don't trust, verify

Verify it yourself, offline

One dependency-free Python file re-checks the signal hash chain and recomputes the dataset Merkle root against what we publish — you don't have to take our word for any of it.

# download the standalone verifier
curl -O https://onchainlab.net/verify_trust_suite.py
# check the live site (exits 0 if everything matches)
python verify_trust_suite.py
# and verify the Bitcoin anchors
pip install opentimestamps-client && ots verify <date>.json.ots