Verify records
Every live forecast is stored with a SHA-256 hash of its own data and of the previous record. No past forecast can be changed without breaking the whole chain after it. Backtest rows are not part of the chain: they were computed after the fact and are always labeled.
No live records yet.
Current chain hash (posted to Telegram every morning):
0000000000000000000000000000000000000000000000000000000000000000
How to verify it yourself
- Download a pair's CSV history — it includes the record fields, hash and prev_hash.
- Build a JSON object from pair, horizon, issue_date, target_date, snapshot_utc, price, low, high, range_pct, atr14, model, prev_hash; numbers rounded to 8 decimals, keys sorted, no spaces.
- Its SHA-256 must equal hash, and prev_hash must equal the previous record's hash.
- Compare the chain hash for a date with that morning's Telegram post: it was published before the day closed.
Latest records
| # | Issued | Pair | Horizon | Hash | Previous |
|---|