How to use (3 steps)
- In Pre-commit, set the list and operation, then publish the commit hash.
- After a public beacon is published, paste the beacon, your published commit, and the reveal data.
- Check commit match, reproduce results, then download an audit report (JSON/CSV/PNG).
Note: This tool does not verify the beacon source; you are responsible for choosing a trustworthy public value.
Paste-to-verify fairness
Randomness beacon verifier tool
Create a commitment first, then reproduce a deterministic pick/shuffle using a public beacon value you paste — no external requests.
Tip: You can drag & drop a .txt/.csv file onto the items box.
Normalization
Secret salt (optional)
Share URL contains settings only (no items/secret/beacon/commit).
This memo is not hashed; it is included only in your downloaded report.
Manual reveal (advanced)
Tip: You can drag & drop a .txt/.csv file onto the items box.
Normalization
Copy URL shares settings only. Inputs (beacon/items/secret) are excluded.
Pre-commit result
Publish text template
Verification result
Frequently asked questions
What is a randomness beacon?
A randomness beacon is a public value published by a third party at a known time (for example, drand or NIST). You can paste it here and use it to reproduce a deterministic draw.
Does this tool fetch or verify the beacon source?
No. This page does not fetch external data. You paste the beacon value yourself. Verifying the beacon’s authenticity is up to you.
What does the commit hash prove?
It commits you to the list, operation, normalization settings, and optional secret salt before the beacon is known. Anyone can later recompute it to detect changes.
Is this suitable for cryptographic security?
This tool is for transparency and reproducibility, not for generating secret keys or security-critical randomness.