Skip to Content
DocumentationProject Status

Project status

Last checked: 2026-10-07.

Pilot-stage, pre-production software. Published npm packages: 0.7.2. Source checkout version: 0.7.2. Main GitHub repository: public.

The implementation below is merged into main (PR #27, September 7, 2026) and has been extended since. It is published in the npm packages (0.5.0 and later). It is not in the historical Sepolia deployments. Local acceptance evidence does not make it production software.

Available components and limits

AreaCurrent development status
Public installationAll five @clearproof packages are at 0.7.2 on npm and publish from GitHub Actions with signed build provenance; circuits is source only
Proof componentsCredential-bound Groth16 pilot-transfer-v3 statement (tree depths 32/20/20: 2^32 credential leaves per issuance root, 2^20 issuer leaves, 2^20 minus two sanctions addresses), holder-secret and issuer membership checks, sanctions screening of both wallets, exact transfer projection and valuation arithmetic, tested with real development proofs in CI
API and storageEncrypted tenant-scoped records, signed enrollment, revocation, transactional authorization and restart/retry isolation tested with PostgreSQL
VerificationMatching eight-signal statement checked in Python and Solidity; API/SDK trust the configured server, PostgreSQL owns consumption and contracts mirror receipts under publisher-validated checkpoints
EncryptionRecipient HPKE, independently scoped key authority, signed information approval and transfer/context binding; key rotation and altered-envelope rejection covered locally
Policy workflowsExplained ALLOW, DENY, REVIEW and INDETERMINATE outcomes; stored policy comparison, separate approval/activation history and reviewed rollback
InvestigationsRead-only timelines and paginated queues join counterparty, custody, chain and evidence observations, preserving duplicates, ordering and unresolved conflicts
Historical evidenceEncrypted exports with independently configured source/decision/status/timing trust, real proof verification and offline policy replay; missing trust remains indeterminate
Observation onboardingNon-authorizing observations, selected-cohort coverage/disagreement/timing reports and a disposable database/test-chain acceptance command
Provider and bilateral workBounded Fireblocks signature/event adapter tested with synthetic signatures; local simulated bilateral dispositions. Live provider access, automated signing-key refresh and remote TRP conformance remain open
Deployment and assuranceHistorical Sepolia deployments of the legacy contracts only; the pilot verifier and registry are not deployed. No completed independent circuit/contract audit or production trusted setup

The clean-checkout workflow installs locked dependencies, builds source workspaces, generates explicitly unapproved development artifacts and exercises real PostgreSQL, CLI/API and local EVM paths. Retained encrypted exports can be reviewed after the services stop. These are controlled synthetic tests with configured authorities, not proof of live source truth or legal compliance. The install-and-build portion of this workflow was re-verified from a clean public clone of main on September 15, 2026 at commit 1c8d385 (locked workspace install, workspace build, built-CLI --help, Python environment sync, Python unit suite: 1,923 passed, 4 skipped).

Capacity and assurance

Circuit capacity: 2^32 credential leaves per issuance root, 2^20 issuer leaves and 2^20 minus two sanctions addresses. The software refresh scans at most 1,024 enrollments across its configured 1–16 issuers, within a 30-second tenant transaction. Encrypted inventories are paged; the measured synthetic root-build median at 1,024 leaves was 16.73 seconds. Production throughput has not been demonstrated. Circuits and contracts have not been independently audited. Proving keys are development-only.

Adoption and commercial next steps

The proposed commercial direction is managed integrations and recurring operational workflows around portable evidence. Pilot briefs, interview questions, a measurement worksheet and hypothetical pricing experiments are prepared. No customer adoption, willingness to pay, revenue or service-level commitment is established.

Customer-dependent issuer/wallet support, live provider integration, ongoing re-screening feeds, commercial validation and independently reviewed production operations remain separate follow-on gates. The repository is public . The local pilot is on main through PR #27. Its TypeScript SDK and CLI are in the npm packages at 0.7.2; the Python API and acceptance tooling run from a source checkout. @clearproof/circuits publishes circuit sources only.

See security, testnet contracts and quickstart.

Last updated on