Proof the track record cannot be rewritten
Every day we publish signals. Every day, one hash of that full published set goes into a chain where each day hash includes the previous one. Change one historical signal and every later hash breaks. You do not have to trust us: you can check it yourself.
What this proves, in plain words
A track record is only worth something if it cannot be edited after the fact. This page makes that testable:
- Daily hash. Each day a script computes a SHA-256 fingerprint of every published dataset: the three reports, all alert streams and the append-only signal archive behind the performance page.
- Chained. Each day entry contains the previous day's hash. Rewriting any past day would change every hash after it.
- Anchored in the Bitcoin blockchain, free and independent. Each day entry is timestamped with OpenTimestamps, which commits the day's hash into the Bitcoin timechain. That timestamp is independent of us and of any host, so a day cannot be backdated later. The full chain and every day's fingerprint plus its Bitcoin proof are published here on this site (linked in the table below), so you can download and re-verify everything yourself, independently of any single host or account.
The selection rules behind the measured signals are frozen separately, see the performance page. The chain logic itself falls under the same integrity rule: it never changes automatically.
Verify it yourself
- Download the chain: curl -O https://datasignalslab.com/proof/chain.jsonl and each day's fingerprint from the table below (/proof/days/<date>.json).
- Recompute it. Each day's hash = sha256(prev + canonical_json(entry_without_hash)) (the exact spec is in every entry). Re-derive every hash from the raw entries; any edit to a past day breaks that day and every hash after it.
- Check the independent timestamp: ots verify days/<date>.json.ots -f days/<date>.json (the free OpenTimestamps client) confirms the day's fingerprint was committed to the Bitcoin blockchain - a clock no one controls.
Current chain status
The chain has 56 daily links, from 2026-07-08 to 2026-09-03. Latest day hash: 2f7f325ce46d5893c455b78783b96c85f30b43490df78c6ef2b432439c0080de, covering 17 published datasets.
| Date | Day hash | Datasets | Day file & Bitcoin anchor |
|---|---|---|---|
| 2026-09-03 | 2f7f325ce46d5893c455… | 17 | 2026-09-03.json · Bitcoin anchor |
| 2026-09-02 | c001315a41ce252187f4… | 17 | 2026-09-02.json · Bitcoin anchor |
| 2026-09-01 | 9843f44ad828a4a57152… | 17 | 2026-09-01.json · Bitcoin anchor |
| 2026-08-31 | a7dd870a4bf08179fc04… | 17 | 2026-08-31.json · Bitcoin anchor |
| 2026-08-30 | 6804ff951c11a855ad5d… | 17 | 2026-08-30.json · Bitcoin anchor |
| 2026-08-29 | 04b95e329365099bb5f2… | 17 | 2026-08-29.json · Bitcoin anchor |
| 2026-08-28 | 99605bec4daf54a0b2ef… | 17 | 2026-08-28.json · Bitcoin anchor |
Known gaps: 2026-08-26, 2026-08-27 were never sealed (the pipeline failed to run that day and there is nothing to backfill honestly). The next day links to the last sealed day, so every published hash still verifies; the gap itself stays visible forever, which is exactly what this chain is for.
Cite this
Free to use with attribution. Suggested credit:
DataSignals Lab. Proof: the daily hash chain behind the track record. https://datasignalslab.com/proof.html
DataSignals Lab publishes data and research. Informational only, not investment advice, not an offer or solicitation. Every figure links back to the official filing so you can verify it yourself.