Developer guide
Build with ZKProofport.
Choose a proving environment, inspect its trust assumptions, and integrate the proof into your application.
Choose your integration path.
Mobile / on-device
The TypeScript app SDK creates proof requests, opens the mobile app through a QR code or deep link, and receives a proof and public outputs. Supported mobile flows generate proofs on the user’s device. Current SDK support includes Coinbase KYC, country policy, and Google Workspace / Microsoft 365 OIDC domain proofs.
Agents / hosted proving
Use the agent SDK or local MCP package for programmatic proof requests. The agent infrastructure includes an AWS Nitro Enclave implementation. Endpoint configuration and attestation determine whether a request uses that protected environment or a standard server.
Browser proof runner
The web SDK opens the portal for supported browser-based proving and verification flows. The portal is intended to be launched by an application with its request context.
Understand what each path protects.
Different proving environments have different trust assumptions. A valid zero-knowledge proof does not establish where the proof was generated.
On-device proving
Supported mobile flows compute proofs on the user’s device. The verifier receives the proof and its public outputs. Credential retrieval, relay metadata, and public inputs have their own disclosure boundaries; inspect the selected circuit and integration before choosing a policy.
TEE and standard-server endpoints
In the supported Nitro deployment, clients validate hardware attestation and encrypt inputs to the enclave key. Standard-server endpoints can receive readable proof inputs over HTTPS. Verify the endpoint’s mode and returned evidence; neither proof validity nor the presence of a TEE-capable SDK implies enclave execution.
Public outputs and policy design
Applications must verify both the proof and that its public outputs match the requested policy and scope. A result can reveal information by inference: for example, a country policy containing one country may reveal that country. These proofs do not guarantee complete unlinkability or eliminate privacy and compliance obligations.
Circuits and open specifications.
CIPs define proof semantics, public inputs, assumptions, and limitations. The circuit repository contains Noir implementations and Solidity verifiers. Consult each specification and SDK for its current support status.
The GIWA Sepolia privacy prototype uses a test attester. Production Dojang issuer and schema parameters remain unresolved. Balance conditions and combined eligibility policies shown on the homepage are future directions.
Inspect the implementation.
Review deployment records and circuit source for the network and verifier you plan to use. Open-source availability and deployed contracts are not evidence of an independent security audit.