Security
Curated in-app view
Source file linked
Back to documents
Document route

Blind Policy Enterprise Readiness

Enterprise readiness packet for Blind Policy Verification covering the live Groth16 proof package, SDK path, benchmark boundary, tamper verification, and the remaining gates for Solana on-chain verification, additional circuits, HSM/KMS, external audit, and Rust/Python SDKs.

Document context

Enterprise readiness packet only; it claims live Groth16 proof generation and verification, while explicitly marking Solana on-chain verification, PLONK/STARK/recursive proofs, HSM/KMS, external audit, and Rust/Python SDKs as required next gates rather than completed production claims.

Audience: Enterprise buyers, CTOs, auditors, security reviewers, protocol engineers, investors

Open raw file

Blind Policy Verification Enterprise Readiness

PrivateDAO Blind Policy Verification is a product line for proving that a private policy was satisfied without exposing the policy inputs, internal thresholds, formulas, or sensitive customer records.

What Is Live Now

CapabilityStatusEvidence
Groth16 proof generationLiveThe backend generates a witness, runs snarkjs groth16 prove, then verifies before issuing a receipt.
Groth16 verificationLive/api/v1/proof-workflows/blind-policy/verify verifies the proof package and fails on tampering.
Public proof packageLiveIncludes proof, public signals, verification key, verification key hash, policy commitment, and input commitment.
Tamper detectionLiveAny changed public proof package produces mismatch with original and recomputed hashes.
TypeScript SDKPilot-readypackages/blind-policy-sdk provides a typed client for status, sample, prove, and verify.
Browser API consoleLive/developers/blind-policy-api lets a buyer test the flow from the browser.
BenchmarksLocal evidencenpm run benchmark:blind-policy measures package creation, hash recomputation, receipt verification, and Groth16 verification over the checked-in fixture.

Truth Boundary

The current production claim is Groth16 Blind Policy Verification.

REFHE, Ika / Encrypt, and MagicBlock are currently commitment and provider-readiness lanes inside this product unless a separate provider receipt is attached. They must not be described as final funded Ika dWallet DKG, final 2PC-MPC signing, final REFHE execution, or final MagicBlock settlement inside Blind Policy Verification without separate evidence.

PLONK, STARK, recursive proofs, and Solana on-chain verification are not claimed as live in this product yet.

Enterprise Gaps To Close

Enterprise requirementCurrent statusRequired next step
Solana on-chain verificationNot liveBuild a Solana verifier program or verification-record program that stores proof commitments and verification result references.
Blind Compliance circuitNot liveAdd circuit template for compliance checks with private documents and public compliance claim.
Blind KYC circuitNot liveAdd circuit template for KYC provider result commitments without exposing identity attributes.
Treasury Limits circuitNot liveAdd circuit template proving spend limits were respected without exposing private treasury policy.
DAO Voting Rules circuitNot liveAdd circuit template proving voting eligibility/rule satisfaction without exposing voter intent.
Multi-policy proofsNot liveAdd aggregation layer that binds multiple policy commitments into one public proof package.
HSM/KMS key managementNot liveAdd AWS KMS/HSM-backed signing/encryption boundaries for enterprise deployments.
External security auditNot completeCommission circuit and backend audit; publish scope, report, and remediation log.
Rust SDKNot liveImplement typed Rust client for prove/verify and proof package parsing.
Python SDKNot liveImplement typed Python client for prove/verify and audit workflow integration.
Public npm releaseNot livePublish @privatedao/blind-policy only after registry, versioning, and support policy are ready.

Customer Integration Path

  1. Call GET /api/v1/proof-workflows/blind-policy/status to confirm live proof status.
  2. Call GET /api/v1/proof-workflows/blind-policy/sample for a safe payload.
  3. Call POST /api/v1/proof-workflows/blind-policy/prove with private inputs.
  4. Store the returned public proof package.
  5. Call POST /api/v1/proof-workflows/blind-policy/verify with the public package.
  6. If any public package field changes, verification returns mismatch with original and recomputed hashes.

Architecture

Client
  |
Private Data
  |
Blind Policy
  |
Groth16 Circuit
  |
Proof Package
  |
Public Verification

Benchmarks

Run:

npm run benchmark:blind-policy

The current benchmark measures package creation, hash recomputation, receipt verification, and Groth16 verification over the checked-in proof fixture. It does not measure full witness generation.