Precommitted results
Publish a hashed commitment and Merkle root before disclosing any instant-win results. Preserve the original draw configuration in a signed record.
Cryptographic verification for competition operators
Cryptographically verified competition draws
Cryptographic proof your customers can verify themselves
Every committed draw gets a public proof record and verifiable ticket evidence. Replace "trust us" with "verify it yourself."
Built for UK competition operators • Public cryptographic proofs • Instant-win verification
LIVE DATABASE FEED
Recently published verification records
Actual draw commitments and revealed results, with Australian operators shown first when available.
Connecting to verification ledger…No activity loaded
SYDNEY--:--Australia
MELBOURNE--:--Australia
PERTH--:--Australia
LONDON--:--United Kingdom
Retrieving published draw records…
SHA-256Reproducible proof hashes
Ed25519Signed audit receipts
InstantIndividual ticket verification
WHY VERIFICATION MATTERS
Proof your customers can independently check.
Fairness needs evidence that survives beyond a screenshot. VerifiedDraws records the commitment, the outcome and a way to check both.
Public verification
Entrants can look up a draw's commitment, then independently verify their ticket's Merkle proof against the committed root.
Audit trail
Issue a digital receipt when a draw is committed. After closing, the published seed allows the complete allocation to be reproduced.
INSTANT-WIN VERIFICATION
Every ticket can carry its own proof.
For an instant-win draw, a winner allocation is committed before results are displayed. Each buyer can receive a private proof for their ticket without exposing the whole prize map early.
How instant proofs work →TICKET VERIFICATION
Ticket#00148
OutcomeCommitted allocation
AlgorithmMerkle + SHA-256
Validation✓ Proof matches committed root
Illustrative values — not an actual customer draw.THE EVIDENCE, EXPLAINED
See exactly what each proof guarantees.
We prefer a checkable method and clear limitations over claims that cannot be tested.
Read verification methodology →Can a result be altered after commitment?
The stored Merkle root binds the published ticket allocation. A disclosed ticket proof will fail if its outcome is changed without matching the original root. A public third-party timestamp is still planned.
How can I verify my individual ticket?
Once your operator has provided a genuine proof package, our checker recomputes the SHA-256 Merkle path. The resulting root must match the public draw record. Purchase-linked private proof delivery is not yet enabled in this staging release.
Does this already use a blockchain or external beacon?
Not yet. The staging build uses cryptographic commitments and signed records. We explicitly distinguish those from independent public randomness, external timestamps and blockchain transaction proofs.
Can I test it without registering?
Yes. The interactive demonstration generates a simulated draw, reveals a ticket outcome and verifies its mathematical proof in the browser without taking payment.
Open the demo →SEE IT IN ACTION
Explore Live Demo →
Don't just take our word for it.
Try a fresh simulated draw, inspect its individual ticket proof and verify the cryptographic root in your browser.