Groth16 Ceremony
Phase 1 rehearsal

Participant 07 · Phase 1 rehearsal

Join the circle.
Leave no secret.

A shared ceremony in the long summer light. Verify the chain, add what only you can know, and pass it on intact. The entire contribution runs locally in this browser.

Step
Ceremony
Status
Time
01
WelcomeVerify the invitation & your place
In progress
~ 1 min
02
PrepareTest browser, memory, power & storage
Waiting
~ 1 min
03
ReceiveFetch & verify the shared chain
Waiting
~ 8 min
04
ContributeAdd entropy & compute in WASM
Waiting
~ 74 min
05
ReturnClear, attest & upload the candidate
Waiting
~ 10 min
Step 01 / Welcome local session

Public record · MPC-003

Every hand leaves
a verifiable trace.

Follow the rehearsal chain from its signed beginning to the latest accepted contribution. Records are append-only; every transition can be independently checked.

07Accepted
00Rejected
Phase 1Active round
32Reserved places

Contribution ledger

Accepted records

PositionParticipantAcceptedRecord

Participant guide · browser rehearsal

A quiet machine.
A careful hand.

You do not need to understand the cryptography to participate safely. Follow the checks, keep the browser open, and never bypass a warning.

Before you begin

Prepare your device

No production minimum profile has been approved. The ceremony checks the device you actually use.

⌁

Stable power

Plug in the computer and disable automatic sleep for the contribution window.

◎

Supported browser

Use the latest Chromium or Firefox. Complete the isolation and worker checks.

◇

Free storage

Grant durable browser storage and keep at least the amount requested by preflight free.

↟

Memory headroom

Close heavy applications. The contribution pauses before memory becomes unsafe.

The contribution

Five steps, in order

01

Verify your invitation

Match the signed definition, coordinator identity, ceremony identifier, and your roster position. Stop if anything differs.

~1 min
02

Check the machine

Preflight tests browser isolation, workers, total available memory, durable storage, power, and wake-lock support.

~1 min
03

Receive the chain

The browser downloads the preceding artifacts in resumable chunks and replays every accepted transition locally.

~8 min
04

Add your contribution

Fresh private randomness is mixed into the chain. Computation happens locally while worker health and memory are monitored.

~74 min
05

Clear and return

Verify the candidate, clear temporary secrets, attest to the clearing steps, and upload. Only the coordinator can publish it.

~10 min

Recovery

If something interrupts you

Network disappears

Leave the tab open. Download or upload resumes from the last verified byte when the connection returns.

Wait and resume
Tab or browser closes

Reopen the invitation in the same browser profile. Durable checkpoints are checked before resuming.

Reopen invitation
Worker stops

The failed shard is discarded and retried in a replacement worker. The candidate is verified from scratch afterward.

Automatic recovery
Computer restarts

Return with the same browser profile. If checkpoints cannot be authenticated, the contribution safely starts again.

Never publish partial work
i
An upload is not an acceptance.A partial or crashed contribution cannot become the chain head. Publication requires a complete file, matching digest, valid proof, and an explicit coordinator decision.

Common questions

Small answers to important things

Can I use the computer while it runs?

Light use is fine, but avoid games, video editing, virtual machines, and other memory-heavy work. Keep the ceremony tab visible whenever possible.

Does my private randomness leave the browser?

No. Only the transformed candidate and public verification data are returned. Temporary randomness stays in local worker memory and is cleared before upload.

Can I prove that the secret was erased?

No. The erasure statement records that you followed the clearing instructions; it is not cryptographic proof that every copy was destroyed.

What if a verification check fails?

Stop. Do not bypass the warning or upload the candidate. Save the diagnostic receipt and contact the coordinator through the signed invitation channel.

Is browser participation production-ready?

Not yet. This site shows the intended flow. Production participation requires approved software identity, browser policy, and hardware guidance based on completed benchmarks.

Coordinator desk · MPC-003

Hold the circle.
Keep the chain moving.

Review people who signed up with Google, give each account the smallest role it needs, schedule the handoff, and require an independent check before anything becomes public.

32Google sign-ups
18Roles assigned
07Active position
07 / 32Accepted

People & permissions

Participant roster

Role edits are drafts until you send a signed invitation.

Google accountAssigned roleWindowStatus
ANAri Nilssonari.n@example.test · email verified
Now · 2h 30mPosition 07
In progress
LMLea Mikkelsenlea.m@example.test · email verified
04 Sep · 09:00Position 08
Ready
OSOwen Sørensenowen.s@example.test · email verified
On callPositions 08–10
Confirmed
IKIngrid Koingrid.k@example.test · email verified
AlwaysIndependent review
Available
RMRavi Mehtaravi.m@example.test · email verified
Read onlyPublic records
Active
ESElin Strandelin.s@example.test · email verified
Not scheduledSigned up today
Needs review
Showing 6 people · 32 total sign-ups

Access model

From sign-up to assigned duty

Every permission change should be attributable, reviewable, and reversible before a slot begins.

01

Sign in

A person signs up with a Google account and accepts the ceremony privacy and conduct notices.

02

Review

The coordinator checks eligibility, availability, conflicts, and the requested participation type.

03

Assign

Choose contributor, backup, verifier, or observer. Privileges stay dormant until invitation.

04

Invite & record

Send a signed, expiring invitation and append the role decision to the private operations log.

Google sign-in proves account control, not human identity. If identity, geography, affiliation, or sanctions checks matter to this ceremony, define and perform those checks separately. Do not imply that Google completed them.
Prototype states