REDACTED ON RUJIRA Practice onlyRedacted runs on a set of numbers that nobody is allowed to secretly own. So we are not making them ourselves.
Hundreds of strangers each stir in a piece only they ever see, then destroy it. Your turn takes about five minutes, in this tab, and you can practise it right now.
No account, seed phrase or signature.
Keep this tab open while your device works.
Your result is checked locally. Nothing is submitted.
A desktop browser is recommended.
Redacted needs a set of starting numbers that nobody secretly controls.
Those numbers are built by many people, each adding a piece of randomness and then destroying it. As long as one person really destroyed theirs, nobody can fake a proof afterwards — not us, not a contributor, not anyone who breaks into a server later. That is why this is done in public, by strangers, instead of by the team.
This page is a practice run. Nothing here is sent anywhere, and nothing here protects real money yet.
Your computer takes the numbers built so far and mixes in a scrambled piece of its own.
Then it throws that piece away and checks that the result still adds up.
That is it. Nothing leaves this tab during the practice.
No. No wallet, no signature, no transaction, no fee.
Nobody should ever ask you for a seed phrase or a password here. If a page claiming to be us does, it is not us.
Every person who joins is one more person who would have to be dishonest for the result to be broken.
One honest participant is enough to keep it safe. You could be that one, and nobody needs to know which.
You can look around and try the practice on a good phone.
For the real one a computer is better: the work uses a lot of memory and battery, and phones often stop it when you switch apps.
A few minutes, depending on your device and connection.
Keep this tab in front until it says it is finished. We will publish proper timings before the real one opens.
No. It does the real work, but on a test setup, and the result is only checked on your own device.
Nothing is uploaded and nothing here becomes part of the real ceremony later.
It removes one specific risk: that whoever built the starting numbers kept a way to fake proofs.
It does not check the rest of the code, and it is not an audit. Anyone telling you otherwise is overselling it.
In the real ceremony: the files each participant produced, and a receipt showing they were accepted. That is what makes it checkable.
In this practice nothing is sent at all. The website still sees ordinary things like your IP address, same as any site.
Everything here can be done on your own machine, with your own tools, and checked by anyone afterwards. The browser is a convenience, never the authority.
You can do the whole thing away from this page: take the current file, contribute on a machine of your choosing, and hand the result back. The four states below are the ones that matter, and they are not the same thing.
Download the latest accepted file and the manifest next to it. Check the hash against the manifest before you touch anything — if they disagree, stop and tell us.
Run the pinned snarkjs version on any machine, online or not. Your randomness never has to leave that machine, and nothing about this step needs us.
Verify your own output against the file you started from. If it does not verify locally, it will not be accepted, and sending it wastes your slot.
Upload the contribution and save the signed receipt. Keep the artifact hash: it is how a submission gets reconciled if the connection drops mid-way.
A finished upload is not an accepted contribution. If you never see Accepted, keep your artifact hash and ask us to reconcile it — do not quietly contribute a second time.
Generate and verify a practice contribution in your own terminal. No mouse interaction needed.
npx --yes snarkjs@0.7.6 zkey contribute control_register.initial.zkey contribution.zkey --name="Participant"Follow the guide to download and check the practice files first. Never use a wallet secret as entropy. Live uploads are not open yet.
Download the full guideThe community transcript will appear after the real ceremony opens. Nothing from the practice is counted here.
These are development artifacts, not the frozen community ceremony inputs. The browser practice uses the small registration circuit; the full ceremony must cover all six.
| Circuit | Public inputs | Initial key | Integrity |
|---|---|---|---|
Reserve depositreserve_deposit | 4 | — | — |
Reserve spendreserve_spend | 7 | — | — |
Reserve mergereserve_merge | 5 | — | — |
Account registrationcontrol_register | 2 | — | — |
Private actionscontrol_action | 5 | — | — |
Spending account creationcreate_subwallet | 5 | — | — |
Practice manifest SHA-256
Loading…Compare a local file with a SHA-256 hash from an independently trusted manifest. A matching fingerprint is an integrity check, not a Groth16 verification.
Groth16 / BN254. Phase two requires at least one independent honest contributor per circuit who does not disclose their randomness. This also relies on a trustworthy, verified Phase 1; phase two cannot repair a compromised one.
Before opening: freeze and reproduce the final circuits; verify Phase 1 provenance; publish hashed initial keys; review the contribution engine and coordinator; prepare durable, mirrored records; and announce the final-beacon policy.
The site, browser and device are still part of the trust boundary. A receipt cannot prove that randomness was destroyed or that participants are independent. No secure memory-erasure guarantee is made for a JavaScript browser.
Read the snarkjs source