Security
Trusted setup
Groth16 proofs are small (three curve points) and cheap to verify on-chain, about 34k gas per pairing on Sei. The price is a trusted setup: a ceremony that produces the proving and verifying keys. If every participant's secret randomness were known, anyone holding it could make proofs of false statements, for example spending notes that don't exist.
The testnet setup
- Phase 1: a local 2^15 Powers of Tau, one contribution plus a fixed public beacon.
- Phase 2: one contribution plus a fixed public beacon, with entropy from
/dev/urandomthat was never stored or printed. - Reproducible with
packages/circuits/setup/run-setup.sh; transcript and hashes are inpackages/circuits/setup/TRANSCRIPT.md. snarkjs powersoftau verifyandzkey verifyboth pass.
The single operator of this setup could forge proofs. That's acceptable for test funds and nothing else.
Before mainnet
- Phase 1 from the Perpetual Powers of Tau, hash-checked.
- A public Phase 2 with at least ten independent contributors, each verified.
- A final beacon from a drand round committed in advance.
- A published transcript and a verifier generated from the final key.
The verifier is immutable, so a new ceremony means a new pool. Funds don't migrate automatically.
Artifacts served by this site
The app downloads the circuit's wasm (3.2 MB) and proving key (14.8 MB) on first use, checks each against a SHA-256 hash compiled into the app, and caches them on the device. The hashes are listed on Contracts.
Source: apps/web/content/docs/trusted-setup.md