Verification details

BetGlitch hashes every published pick. On its own that only proves the record has not been edited — we compute the hash, we serve the record, so nothing stops us replacing both. This page closes that gap by handing the timestamp to parties who are not us.

What this proves

  • Existence before a point in time. Each digest is submitted to independent OpenTimestamps calendars, which aggregate it into a Bitcoin transaction. Once confirmed, the proof shows the digest existed before that block — a fact BetGlitch cannot backdate, rewrite or withdraw.
  • Taken before kickoff. Anchoring runs immediately after publication, while the fixtures are still hours away. A timestamp taken after the matches were played would prove nothing about foresight.
  • Not our word for it. The digest is computed only from data the public claims API already serves, so you can rebuild it yourself and check it against the proof with the standard ots tool. No BetGlitch cooperation required.

What it does not prove: that a published pick was a good bet. Timestamping fixes when we said something, never whether we were right. That is what the results page is for.

Verify it yourself

  1. Fetch the claims: https://api.betglitch.com/api/proof/claims/?limit=200
  2. Build one line per claim as <claim_id>:<claim_hash>, sort the lines, prefix the manifest version line, and end with a newline. The anchor detail endpoint serves the exact manifest so you can diff against it.
  3. SHA-256 that text. It must equal the digest below.
  4. Download the proof and run ots verify --digest <digest> proof.ots
0 timestamps0 confirmed in Bitcoin0 commitments covered

No commitments have been anchored yet. This page fills in on the next publication cycle.

← Back to the results