Privacy-focused evidence
for crypto transfers.
Explore zero-knowledge checks and encrypted transfer information with clearproof. Built for teams evaluating how to verify specific facts while limiting the spread of customer data.
Development software for controlled evaluation. Circuits and contracts have not completed independent audits; current proving artifacts use a development-only trusted setup.
Repository and package status checked September 7, 2026
What you can evaluate today
The project includes Circom/Groth16 circuits, a TypeScript SDK, CLI tools, a Python API, encrypted payload components and EVM contracts. These components are a foundation for a pilot.
Source availability: the main GitHub repository, repfigit/clearproof, is public. The local adoption pilot is merged into main through PR #27 and remains unreleased on npm; published packages and historical deployments are separate.
Versions: published npm packages are at 0.3.0; the development checkout is 0.4.0. Features in development may not be available in the published packages.
Installation: the public proof SDK installs successfully. The published CLI currently has an unavailable dependency; use a source checkout for CLI evaluation.
Assurance: no completed independent circuit or contract audit, production trusted setup, or end-to-end regulatory compliance certification is claimed. Use synthetic data and testnet funds for evaluation.
The intended transfer workflow
A virtual asset service provider (VASP), such as an exchange or custodian, combines checks, protected information exchange and a scoped verification decision.
A zero-knowledge proof and encrypted payload do not by themselves establish legal compliance. Required information, trusted counterparties, screening, retention and applicable rules depend on the deployment. Public proof metadata can also reveal information; the design does not promise complete anonymity.
Development pilot and next steps
In development · UnreleasedThe unreleased pilot focuses on evidence and recurring operational work for a stablecoin processor or custodian. The capabilities below have local synthetic acceptance evidence; customer adoption and managed distribution remain to be validated.
Latest development progress
An open draft change adds wallet-signed credential enrollment, revocation records, encrypted storage scoped to each tenant, signed issuer roots and a contract for recording approved roots. Transfer checks bind participant, asset, valuation, policy and timing fields to a commitment.
The draft also adds development proof generation and cryptographic verification, signed valuation inputs, and policy evaluation that explains allow, review, deny or indeterminate outcomes. Policy comparison reports show how proposed rules change decisions using supplied or retained evidence. Policy review and activation are separate operations, with retained activation history and explicit rollback to a reviewed, effective version.
The draft local authorization service checks the active policy, credential revocation, approved roots, signed external facts and the cryptographic proof. An allow decision requires approved transfer information and encrypts it for a trusted recipient key. Evidence, a receipt and replay protection are recorded together; a failure rolls back the operation. A local simulated counterparty checks signed evidence and encrypted information and returns accept, reject, information-request or pending outcomes. Remote delivery and payment execution remain outside this local acceptance scope.
Encrypted evidence exports preserve the original proof, policy and source-record versions for an approved reviewer. Offline inspection checks integrity and cryptographic validity; independently configured trust also enables statement reconstruction and conditional policy replay after proof expiry. Review also checks independently configured decision and source authorities, historical revocation and RFC 3161 timing evidence. Results distinguish supported, contradicted and indeterminate evidence; missing trust never becomes approval.
Transfer investigation tools combine compliance, proof, counterparty, custody, chain and evidence observations into timelines and paginated queues. Reports identify conflicts and unresolved steps with suggested owners and next actions. Access is authenticated and scoped to each tenant; reports do not authorize transfers.
A Fireblocks webhook adapter verifies a supported signature and event profile and retains encrypted source evidence through an authenticated relay. Validation uses synthetic signed events and a local database. Live provider interoperability and automatic signing-key refresh remain unvalidated or unimplemented.
Observation mode records explained outcomes without authorizing transfers. Selected-cohort reports keep missing cases, disagreement and measured evaluation time explicit. A source-checkout runner owns a disposable database and test chain, exercises real development proofs and retains encrypted historical exports for offline review. These local results do not establish live provider interoperability, customer value or production assurance. Independent security review remains open. This work is not included in the published 0.3.0 packages or the Sepolia deployments listed below.
Published packages
Version 0.3.0 is available on npm for each package below, checked September 7, 2026. Review each package’s contents and requirements before integrating.
Start with the SDK
npm install @clearproof/proof@0.3.0Proof generation also requires compatible circuit WASM and proving-key files; verification requires the matching verification key. The package installation alone is not a complete proving setup.
Read setup requirementsRecorded testnet deployments
Sepolia onlyAddresses from the July 20, 2026 deployment record. Contract bytecode was checked on Sepolia on September 5, 2026. These are historical test deployments; code presence does not establish that they match the current development checkout. Deployment and explorer listings do not establish an independent security audit.