REDACTED ON RUJIRA Practice onlyA community setup for Redacted’s privacy proofs. Try a local practice contribution while we prepare to launch. No crypto expertise needed.
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.
Zero-knowledge proofs let Redacted check an action without revealing its secret inputs. The planned ceremony will bring independent contributions together to create the public parameters those proofs need, reducing reliance on a single operator.
This practice shows the process. It does not secure live funds or count toward the final setup.
In this practice, your device adds fresh secret randomness to a development setup, then checks the result locally. The future community ceremony will use the same principle to prepare Redacted’s proof parameters.
No. There is no wallet connection, signature, transaction or participation fee. Never enter a seed phrase, private key or recovery password here.
Independent contributions reduce reliance on the ceremony operators. Each final circuit needs at least one honest phase-two contributor who keeps their randomness secret and discards it, on top of a trustworthy phase-one setup.
You can explore the page and try the practice on a capable phone. A computer is recommended for the full ceremony: cryptographic work can use substantial memory, battery and data. In-app wallet browsers may stop when backgrounded.
Practice time depends on your device and connection. Keep the tab in the foreground until local verification finishes. We will publish timing guidance before opening the community ceremony.
No. It makes a real Groth16 contribution to a development setup, and checks the result locally. It is not uploaded or included in the community ceremony.
No. A ceremony helps establish proof parameters. It does not replace audits or prove that the circuits, interface, contracts or devices are secure.
The planned live ceremony will publish accepted contribution files, hashes and receipts. The practice sends no contribution or gesture data to a coordinator. The website host can still see normal connection metadata, such as your IP address.
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