What acceptance means
Given a fixed circuit, verification key, proof, and set of public inputs, acceptance means that a witness exists for the encoded relation under Groth16 security assumptions. For a withdrawal, that relation is intended to fix bundle membership, selected-child authority, nullifier, destination, amount, fee, chain, verifying contract, proof context, and encrypted payload hash.Trust chain
Each edge needs its own evidence. Artifact identity comes from independent pins and reviewed bindings around the proof.Trusted setup
Groth16 uses relation-specific setup material. Compromised toxic-waste handling or a setup for another circuit can invalidate soundness assumptions even when local verification passes. Nullark checks browser proving files against an independently bundled SHA-256 pin, the setup record, verifier identity, public-input order, and byte limits. The independent pin anchors manifest trust.Evidence beyond proof acceptance
The surrounding system still needs evidence for:- Circuit source and product intent
- Source-to-constraint compilation
- Trusted setup ceremony
- Authorized proving-artifact release
- Deployed verifier identity and pool routing
- Browser, dependency, wallet, RPC, relayer, and operator integrity
- Transaction privacy properties
- Pool availability and relayer funding