How Veristiq Works
A technical deep dive into our tamper-evident audit trail, draw atomicity, and verification engine.
The Problem: Private Databases = Zero Trust
Most competitions run on standard databases (MySQL, Postgres). An admin with access can easily modify entries, change timestamps, or re-run draws until they get a desired result.
Screen recordings prove nothing. They only show what happened on screen, not what happened in the database.
The Veristiq Process
From entry to audit in 3 verifiable steps.
Immutable Event Logging
Operators send entries and competition events (creation, update, pause) to our API. Each event is hashed and linked to the previous event's hash, creating an unbroken chain.
- Cryptographic linking (SHA-256)
- Real-time timestamps
- Tamper-evident structure
"event_id": "evt_8921...",
"type": "TICKET_ENTRY",
"data": { ... },
"previous_hash": "a7f3...",
"hash": "b8c9..."
Atomic Draw Execution
When a draw is triggered, the pool of eligible entries is locked. A random seed is generated server-side (provably fair) and combined with the entry pool hash to select a winner deterministically.
- Pool freezing
- Reproducible selection algorithm
- Instant result locking
Draw Locked
Timestamp: 2025-05-12T14:30:00Z
Public Verification
A public audit page is generated immediately. This page displays the winner, the draw time, and the cryptographic proofs. Anyone can independently verify the chain integrity.
- Publicly accessible URL
- Chain integrity status
- Exportable audit data
API-First Integration
Veristiq is built for developers. Integrate our REST API into your existing raffle platform (WordPress, Laravel, Node.js) in a few hours.
Read the API DocsDCMS Code Compliance
We map every feature directly to the upcoming DCMS voluntary code for competitions. Don't just say you're compliant—prove it.
View Compliance Mapping