How It Works
One wave, start to finish — provable at every step.
A complete wave from commit to reveal to outcome to contribution, in plain language, with the proof at each step.
Participation usually arrives finished. You are shown an outcome and asked to believe the path that produced it. A wave on Veraq runs the other way around: the mechanism that decides it is published first, and every step is designed to be written to the open record as it happens, so the whole sequence can be read back afterward by anyone once the record's read API is live.
This page follows a single wave from end to end — commit, participate, reveal, outcome, contribution — and points to the proof at each step. Nothing here is meant to be taken on faith: each stage is designed to leave an entry you'll be able to open and check yourself. That reading path isn't live yet — this page describes the design, ahead of it.
One note on scope: this is the wave mechanism specifically, commit-reveal-v1. The free official-result predictions you can try right now (state a value or band against an independent authority's own published figure) run on a different, simpler mechanism entirely — no commitment or reveal, checked directly against a public source instead.
The pieces of a wave
- Wave
- One defined round of participation, opened and closed on the open record.
- Mechanism
- The published method that decides the wave — commit-reveal-v1 — committed before the wave begins and provable after.
- Participation
- A participant taking part on terms already visible, recorded as it is made.
- Outcome
- What the wave resolves to once the mechanism is revealed and run against the record.
- Contribution
- The defined share of the participation routed automatically to a verified cause, written from outcome to cause.
One wave, in order
- 01
Commit: the mechanism is published first
Before the wave opens, the commit-reveal mechanism is committed to the open record. A commitment is published and timestamped, so the method is fixed and readable in advance. You can study how the wave will be decided before deciding to take part.
- 02
Participate
Participants join the wave on terms that are already in the open. Each participation is written to the record as it is made — nothing material happens off the record, and the set of participations is fixed once the wave closes.
- 03
Reveal
After the wave closes, the committed mechanism is revealed and checked against the earlier commitment. Because the commitment was published first, the reveal cannot be changed to fit a preferred result. The method you read at commit is the method that runs.
- 04
Outcome
The revealed mechanism is run against the recorded participations to produce the outcome. The inputs were fixed at close and the method was fixed at commit, so the same inputs and method yield the same outcome — for us and for anyone re-running it.
- 05
The defined share flows to a cause
A defined, published share of the participation is allocated automatically to a verified cause, fixed for the wave and published in advance. The contribution is written to the open record from outcome to cause, so where it went can be followed exactly. No appeal, no asking — it is part of how the wave resolves.
Commit before the moment, reveal after it. The order is the whole point.
What you'll be able to check at each step (once the record's read API is live)
The mechanism
Read commit-reveal-v1 at commit, and confirm at reveal that what ran matches what was committed.
The participations
See that the set of participations was fixed when the wave closed, before the reveal.
The outcome
Re-run the revealed mechanism against the recorded participations and arrive at the same outcome.
The contribution
Follow the defined share from outcome to the named, verified cause it reached.
A wave at a glance
- 1
- mechanism, committed before the wave opens
- 5
- recorded steps from commit to contribution
- 100%
- of the sequence written to the open record (illustrative)
Verify it yourself (once the record's read API is live)
Every claim on this page is designed to resolve to an entry you'll be able to open. Pull a wave's commitment and confirm it predates participation. Pull the reveal and confirm it matches the commitment. Re-run the revealed mechanism against the recorded participations and check that the outcome agrees. Then follow the defined share to the cause it reached.
You won't have to trust the description. You'll be able to read the record and confirm the wave did what it says — this page describes that design, ahead of the read API going live.
You won’t have to trust it. You’ll be able to check it — step by step, once the record is live.