PrivateDAO is loading wallet-ready controls, Devnet context, and proof-linked routes so the app lands with real content instead of an empty frame.
Decision surface for whether the long-term privacy boundary remains receipt-based or moves to a stricter verifier-program boundary.
Decision packet only; it does not claim the stronger verifier-program path is already complete or production-frozen.
Audience: Judges, security reviewers, operators, funders
Open raw fileThis document is the decision surface for the final `zk_enforced` production boundary.
Production trust boundary remains:
Pros:
Cons:
Production trust boundary moves to:
Pros:
Cons:
Do not declare Option B complete yet.
Short-term production hardening should continue with Option A plus:
Only after that should the project freeze whether:
Promote the stronger path only when all of the following are closed: