Status
- Service
- checking…
- Environment
- …
Veritrus is in its test phase. Test proofs are real proofs, signed with a test key; the test log may be reset at launch.
Trust
Trust, but verify. Then verify again.
Veritrus is built so you never have to take our word for anything. Here's everything you need to check us, and what we're adding next.
The public log
- Entries
- …
- Latest state
- …
- Chain intact
- …
Each entry includes the fingerprint of the one before; your browser just re-checked the whole chain.
Signing keys
Every record is signed with Ed25519. Save these and verify against them; retired keys stay listed forever so old proofs keep checking out.
| Key ID | Public key | Status |
|---|---|---|
| Loading… | ||
What we promise, precisely
We prove
That an execution ran exactly as declared, on inputs locked in advance, with randomness nobody controlled, and that the record hasn't changed.
We don't claim
That an operator is honest in everything, that entries were fair to begin with, or that a game is legal where you are.
We never hold
Names, emails, phone numbers or payment details of the people in a draw. Proofs carry anonymous IDs only.
Next on the trust roadmap
Open standard and checker
Publish the exact format and the verifier, so anyone can build an independent checker. The draft is up: see Standards.
Witnessed log
Other parties sign the log's latest state, so a rewritten history would be caught.
Blockchain anchoring
Regularly anchor the log's state on public blockchains: a timestamp nobody, including Veritrus, can change.
Independent audits
Security and fairness audits by outside firms, with the reports published here.
Key ceremony
A documented, witnessed process for creating and rotating signing keys, with hardware-protected keys.
Registry
Verified organizations, each with a public track record built from the log.