Oracle Receipt Verification

Verify any receipt.
The chain cannot
be backdated.

Enter a PROOF oracle receipt ID to verify it exists in a valid hash-linked chain and that the prediction preceded the outcome. This is the primitive that makes PROOF different from every prior prediction market: the claim is anchored before the outcome is known. Verify it yourself.

Verify a Receipt
PROOF Oracle Receipt Verifier
Anchor v0.1.0 · SHA-256 · Solana mainnet
✓ VALID — Prediction preceded outcome
This receipt exists in a valid hash-linked chain. The SHA-256 commitment was anchored to Solana before the outcome was known. The oracle's prediction cannot have been created after the fact.
✗ NOT FOUND
No receipt with this ID exists in the PROOF oracle chain. Either the ID is incorrect, or this receipt has not yet been issued. The oracle has not yet fired on this prediction.
Oracle status — pre-deployment
The oracle keypair has not yet been generated. The receipt chain currently contains pre-deployment commitments. Once the Ed25519 oracle keypair is generated and the first deal reaches mainnet, all receipts will be cryptographically signed and verifiable here in real time via the Solana RPC endpoint.

Current chain: 2 receipts · deal:shirokuma-algeria · both valid hash-linked · awaiting oracle keypair for cryptographic signing.
1c1649a2-307d-6521...shirokuma-algeriaseq 0
fc9db2c6-bb81-4a30...shirokuma-algeria · GENESISseq 1
How Receipt Verification Works
01
Oracle commits the prediction
Before any deal advances, the oracle hashes the prediction text with a timestamp and the oracle's Ed25519 public key. This hash is anchored to a specific Solana block. The methodology is locked at this point.
02
The prediction period runs
The oracle watches the pre-specified data sources during the window. No modification to the prediction or methodology is permitted. The commitment is on-chain and immutable.
03
Outcome occurs — oracle resolves
When both oracle sources confirm (or deny), the oracle issues a resolution receipt. The receipt extends the hash-linked chain. The chain validity proves the prediction preceded the outcome.
04
Anyone can verify — forever
The SHA-256 commitment, Solana block height, and chain linkage are all public. Any party can independently verify that the prediction was made before the outcome — without trusting PROOF or any institution.
Why This Matters

Bloomberg's analysts can claim they predicted something. PROOF's oracle proves it.

Bloomberg produces research notes with timestamps. But those timestamps are social facts — maintained by institutional authority, not by mathematics. A Bloomberg analyst's track record is what Bloomberg says it is.

PROOF oracle receipts are mathematical facts. SHA-256 anchored to a Solana block height. The prediction either preceded the outcome or it didn't. There is no ambiguity. No institutional authority required. The ledger is the authority. Every receipt on this page is verifiable by reading the Solana chain — independently, without asking PROOF permission.

This is the single property that changes everything. The oracle's credibility is not a social claim. It is a verifiable track record. 87.6% accuracy across 121 GENESIS runs — not what we say. What the chain shows.

The Anchor Standard

PROOF's oracle conforms to Anchor v0.1.0 — an open standard published at github.com/PROOF-xyz/ANCHOR. Any oracle system can adopt the Anchor standard. Any verifier can check Anchor conformance against this specification. The standard defines: prediction format, oracle keypair requirements, anchoring methodology, chain linkage rules, and resolution criteria.

The open standard is the moat. Once Anchor becomes the reference standard for oracle accountability, any oracle that does not adopt it must explain why it chose less accountability. The verifier on this page works for any Anchor-compliant receipt — not just PROOF's.

Continue reading System Dashboard
→