Community
Participation at the centre.
Participation at the centre — how people join waves, see where a defined share goes, and share in collective upside.
Veraq is built around participants, not users. A participant is someone taking part on terms they can see — the mechanism that decides each wave is published before it runs, the outcome is written to an open record, and a defined share of every contribution flows to a verified cause, fixed per wave and published in advance.
Nothing important is meant to happen out of sight. Where most platforms ask you to take the process on faith, Veraq is built the other way around: the working is shown, and anyone will be able to read it once the open record's read API is live. This page describes how people join a wave, see where a defined share goes, and share in collective upside — and how each of those steps is designed to stay checkable.
How a participant moves through a wave
- 01
Read the commit
Before a wave opens, its mechanism (commit-reveal-v1) is committed to the open record. You can read the math that will decide the wave first, rather than after the fact.
- 02
Take part
Join the wave. Your participation is recorded on the open record as it happens, alongside everyone else’s — legible terms, in plain sight.
- 03
Watch the reveal
When the wave closes, the committed mechanism is revealed and run. Because it was published first, the reveal is designed to be checked against the commit, step for step, once the record's read API is live.
- 04
Follow the outcome
The outcome is written to the record, and a defined share of it is allocated automatically to the wave's verified cause, fixed and published in advance — auditable from outcome to cause.
Verified causes
Fixed and published in advance
A defined share of every contribution is allocated to a verified cause, fixed for the wave and published before it opens — not a line item set behind closed doors, and not picked live by a participant.
Causes are verified
Each cause is vetted and named openly before it can receive a contribution. There is no anonymous bucket and no appeal — only named, verified destinations.
Recorded end to end
Every contribution is designed to be written to the open record, so once its read API is live you'll be able to follow exactly where a defined share went, from outcome to cause, without taking anyone’s word for it.
Shared by design
The upside here is structural. The defined share that flows to causes is published and consistent — part of how a wave works, not a gesture added on top of it. The centre belongs to no single participant and no single party, by construction.
That is the difference Veraq is built to keep: shared benefit is not solicited and not promised. It is recorded, and the record is designed to be open to anyone who wants to check it, once its read API is live.
Participation you won’t have to trust. Participation you’ll be able to check.
Community, in round numbers
- 1 record
- Every participation, outcome and contribution, in one open place
- 7 entities
- Wave, Mechanism, Participant, Participation, Outcome, Contribution, Cause
- 100% recorded
- Nothing material happens off the open record (a design guarantee — illustrative until the record is live)
Ways to take part
Joining the waitlist is the first step: it reserves your place for the earliest waves and keeps you close to how the system develops. Once you are in, you can join a wave and see the verified cause a defined share flows to; verifying it yourself against the open record follows once that record's read API is live.
Developers and the curious are welcome to read first and take part later — every claim on this page is designed to link back to a record entry that proves it, once the record is live.