The machine-readable index of OpenTimestamps Bitcoin-anchor proofs: the manifestHash, the SHA-256 digest committed to Bitcoin, and every sealed record's…
Every sealed forecast is canonicalized as the string objectId|dateIssued|title|claim, hashed with SHA256, and folded into a single manifest of 78 records. That manifest is committed to the Bitcoin blockchain via OpenTimestamps. This page is the machine-readable index of those proofs — fetch the manifest, fetch the .ots proof, recompute each hash, and confirm the time anchor yourself, trusting no one.
manifestHash: d37716713581e2369b5fdcba1e1c5ccee400a747d8309d5e4ebdaec7615669c8. SHA-256(seal-manifest.json): 9eacf5cd1d71965b552e86a0df31ad57d6376321ecf5888f98ac1ea8964e49ed — the digest committed to Bitcoin. Anchor status: pending Bitcoin confirmation (calendar-committed, stamped 2026-06-29; checkable now with ots verify, a confirmed block typically appears within ~24h). We do not claim a block we do not yet have.
What the proof DOES establish: the manifest — and therefore each listed claim hash — existed at or before the anchoring Bitcoin block's timestamp, and has been tamper-evident since the seal (change one character and the SHA-256 digest breaks, the manifestHash changes, and the anchor no longer matches). The proof lives on infrastructure Vijay Jyotish LLC does not control and is checkable on any block explorer. What it does NOT establish: it does not assert that any forecast is correct — outcomes are graded separately against a pre-committed HIT / NEAR / PARTIAL / MISS rubric frozen in a separately anchored grading ledger, misses kept in the denominator. The anchor proves existence-by-a-time and tamper-evidence, not validity. That a specific call predates its own event is carried by each record's public X / YouTube upload timestamp, not by the manifest anchor.
Fetchable artifacts: the seal manifest at /seal-manifest.json (every record: id, title, issue date, source post, seal hash), the OpenTimestamps proof at /seal-manifest.json.ots, and a zero-dependency verifier at /verify-jyotint.mjs. Verify it yourself: node verify-jyotint.mjs --manifest seal-manifest.json --ots seal-manifest.json.ots, or the one-command /verify.sh. Hand it to your own AI at /verify-with-ai. Companion dataset: DOI 10.5281/zenodo.20630257.