Skip to content

Transparency

The facts, with no marketing in the way.

The single source of truth once it is live: queryable data from the open record, with nothing between the visitor and the facts. Illustrative until then — see the FAQ.

This page describes the open record — the structure a wave is written to, and what reading it directly will show once the live query is wired (see the FAQ below). Nothing here is summarised for effect and nothing is held back to be revealed later; the figures marked illustrative are a preview of that shape, not yet a live query result.

Every wave runs on a published mechanism, commit-reveal-v1, committed before the wave begins and provable after it ends. The status panels, the recent waves, and the contributions to causes describe entries on that record. Where a value is shown, it is meant to link back to the entry it came from, so a reader can leave this page and confirm it at the source.

Open-record status

planned
Record availability (illustrative — not yet online)
~1,200
Waves recorded (illustrative)
100%
Waves with a published commitment before they ran (illustrative)
< 1s
Typical lag from event to recorded entry (illustrative)

Recent waves, as the record writes them

  1. 01

    Commitment is written

    Before participation opens, the Mechanism for the Wave is committed to the open record under commit-reveal-v1. The commitment fixes what will decide the wave without disclosing the value that drives it. No wave appears in the recent list before this entry exists.

  2. 02

    Participations are recorded

    Each Participant who takes part has a Participation written against the wave. The set is recorded as it forms, so the inputs to the outcome are known and countable.

  3. 03

    Reveal is published

    When the wave closes, the committed value is revealed and written to the record. Anyone can confirm the reveal matches the earlier commitment, then re-run the mechanism over the recorded participations.

  4. 04

    Outcome and contribution are linked

    The Outcome is written and linked to its wave, and the defined share is recorded as a Contribution to the Cause fixed and published before the wave ran, traceable from outcome to cause. The list orders waves the way the record was written, not for effect.

The seven entities

Wave
One round of participation. Everything below links back to a wave.
Mechanism
The published, provable process that decides a wave — currently commit-reveal-v1.
Participant
A person taking part, recorded as a contributor to the wave rather than a customer of it.
Participation
A single recorded act of taking part in a given wave.
Outcome
What the mechanism produced for a wave, written to the record after the reveal.
Contribution
The defined share of a participation, allocated automatically and recorded as it moves to a cause.
Cause
A verified destination for contributions, fixed per wave and published in advance, named openly on the record.

Contributions by cause

Allocated, not solicited

The defined share is a fixed, published portion of every contribution. It is allocated by the mechanism at the moment you take part — never because anyone was asked.

Traceable end to end

Each contribution links its outcome to its cause. You can start at a wave and follow the share through to the verified destination it reached, without leaving the record.

Causes named openly

Every cause receiving contributions is listed by name with its verification entry. Totals shown per cause are sums of recorded contributions, not estimates.

Verification tools and explorers (planned)

Wave explorer

Not live yet. Once wired, opening any wave will read its commitment, participations, reveal, outcome, and contribution as linked entries — the shape described above.

Commitment and reveal check

Not live yet. Once wired, this will confirm that a published reveal matches the commitment recorded before the wave ran, then let a reader re-derive the outcome themselves.

Open format and references

The record format and commit-reveal-v1 are described in the open on this site (see Documentation) — a third party can read and assess the design today, ahead of the explorer and check tools above going live and ahead of the underlying packages being published anywhere a third party could install them.

Methodology and definitions

Are the figures on this page live?

Not yet — every figure on this page is illustrative until the live query is wired. Once it is, they'll be read from the open record rather than maintained by hand: counts and totals will be exact sums of recorded entries, not estimates.

What does it mean that the mechanism is committed first?

Under commit-reveal-v1, the value that decides a wave is fixed and recorded before participation closes, then revealed afterward. Because the commitment is written first, the reveal cannot be adjusted to suit a result.

Can I reproduce an outcome myself?

Not yet, but that's the design: with the recorded participations, the published mechanism, and the revealed value, you'll be able to re-run commit-reveal-v1 and arrive at the same outcome the record shows. See Verification tools and explorers above for current status.

What is not on the record?

Personal data beyond what participation requires is kept private and is not written here. What is recorded is the wave, its mechanism, the participations, the outcome, and the contribution to a cause.

Read it, re-run it, follow the share to its cause — once the record is live. Nothing on this page asks to be believed in the meantime, either: it's marked illustrative until it is.