Introduction
clearproof combines Circom/Groth16 proof components, encrypted personal-information payloads, a Python API, TypeScript tooling and EVM contracts. The intended users are teams at virtual asset service providers (VASPs), such as exchanges and custodians, evaluating transfer evidence alongside existing compliance systems.
Current scope
A circuit can check a specific mathematical statement about its inputs. Trustworthy transfer evidence also needs authenticated inputs, holder and transaction binding, approved policies, fresh sources and correct verifier behavior. The pilot implements these around the pilot-transfer-v3 proof and tests them locally with synthetic data. Live interoperability and independent assurance remain open.
Encrypted personal information can accompany a proof for an authorized recipient. Encryption does not eliminate required information exchange, and existing Travel Rule services may already provide encrypted messaging. TRP, TRISA and TAIP-10 bridge components are prototypes; complete bilateral interoperability is not claimed.
Components
| Location | Purpose |
|---|---|
circuits/ | Pilot circuit (transfer projection, credential, sanctions for both wallets, private valuation and tier) and the legacy demo circuit |
packages/proof | TypeScript proving, cryptographic verification and discovery |
packages/cli | Local proof tooling and synthetic demonstration |
packages/contracts | Pilot verifier and receipt-mirror registry, plus legacy verification, VASP registration and sanctions-root contracts |
src/ | Python API, protocol, storage, credential, encryption and chain components |
Availability
As checked 2026-10-07, the main repository is public. npm packages are at 0.7.2 and include the pilot. The local pilot is merged into main through PR #27; npm publication does not establish production readiness.
Plan an evaluation to record reproducibility, useful evidence and failures. Start with project status, quickstart requirements and security limitations.