HQ publishes every forecast on the /proof page along with a cryptographic hash and digital signature, before the outcome is known. This lets anyone independently confirm that a forecast wasn't quietly edited or backdated after the fact. Verifying it yourself takes a few minutes and doesn't require any special software.
What a signed forecast hash actually proves
A hash is a one-way fingerprint generated from a piece of text. Feed the same text in, and you always get the same hash out — but change even a single character, and the hash changes completely. By publishing the hash alongside the forecast at the time it's made, HQ creates a permanent, checkable record of exactly what was said and when.
The signature adds a second layer: it proves the hash was generated using HQ's private signing key, which means the forecast genuinely came from HQ and wasn't inserted or swapped by someone else.
Step 1: Locate the forecast and its published hash
On the /proof page, each forecast entry includes the original forecast text, a timestamp, the hash value, and the signature. Copy the exact forecast text as displayed — including any punctuation, line breaks, or formatting HQ used when publishing it.
Step 2: Generate the hash yourself
Paste the copied text into a SHA-256 hash generator (there are many free, reputable ones online, or you can use a command-line tool if you're comfortable with one). This will output a long string of letters and numbers — that's your independently generated hash.
- Make sure you're copying the raw text, not a screenshot or paraphrase
- Avoid adding extra spaces or line breaks that weren't in the original
- Use the same hash algorithm HQ specifies on the /proof page (typically SHA-256)
Step 3: Compare the hashes
Line up the hash you generated against the one published on /proof. They should match character for character. If they do, you've confirmed the forecast text is exactly what HQ published originally, with nothing altered.
If they don't match, don't assume foul play right away — the most common cause is a copy-paste discrepancy, like a missing space or an extra line break. Re-copy the text carefully and try again before raising a concern.
Step 4: Check the signature (optional but thorough)
For a deeper check, you can verify the digital signature using HQ's published public key, confirming that the hash was signed by HQ specifically and not inserted by a third party. This step is optional for most readers — matching the hash alone already tells you the content hasn't been changed — but it's available for anyone who wants cryptographic certainty about origin as well as integrity.
Why this matters for evaluating an AI forecaster
Plenty of services claim strong track records, but claims are easy to make and hard to check after the fact. A signed, timestamped, independently verifiable hash is one of the few ways to actually hold a forecasting system accountable, rather than taking its word for it. HQ pairs this transparency with real quantum hardware sourced from IBM systems, so both the provenance of the randomness behind forecasts and the integrity of the forecast record itself can be checked by anyone.
If you're exploring other tools in the HQ ecosystem — the Oracle, Genesis, Deep Think, or the Pantheon marketplace of collectible AI minds — the same philosophy applies: verifiable claims over blind trust. And if you're looking for fast, reliable infrastructure for your own projects, it's worth seeing how teams try Loadit to speed up their workflows.
A quick checklist
- Copy the exact forecast text from /proof
- Generate a SHA-256 hash of that text
- Compare it to the published hash, character by character
- Optionally verify the signature using HQ's public key
- Remember: hash verification proves integrity, not prediction accuracy