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, every step is written to the open record as it happens, and the whole sequence can be read back afterward by anyone.
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 taken on faith. Each stage leaves an entry you can open and check yourself.
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 outcome 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 outcome is allocated automatically to a verified cause the community chooses. 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 can check at each step
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
Verify it yourself
Every claim on this page resolves to an entry you can 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 do not have to trust the description. You can read the record and confirm the wave did what it says.
You don’t have to trust it. You can check it — step by step.