Open Source · MIT

Built on Zama FHE

Crivacy runs on @crivacy-fhe, an open-source SDK for issuing and verifying confidential KYC credentials with FHE on Sepolia.

LicenseMIT
NetworkSepolia
StatusLive on testnet
01 · Stack

Our infrastructure

Four components, no proprietary middleware. Anything built on the SDK looks the same on the wire.

Fully Homomorphic Encryption on an EVM. Sensitive KYC fields are stored and computed on as ciphertext, never revealed on-chain.

Open-source TypeScript SDK we authored: @crivacy-fhe/credential (issue, read, grant, decrypt) + @crivacy/js-sdk (OAuth 2.0 + OIDC + verifyDisclosure) + adapter-didit.

KYC vendor adapters

Didit today, with a provider interface any vendor can implement. Sumsub, Persona and others plug in as sibling adapters.

CrivacyKYC contract

Solidity + FHE on Sepolia. Encrypted euint/ebool fields keyed to the user's wallet, with per-firm access grants over the boolean eligibility verdict.

02 · Why

Why we open-sourced our SDK

The confidential credential pattern we built for Crivacy is reusable by any operator who wants to issue verifiable, encrypted credentials on-chain. Keeping it internal would mean every new issuer reinvents the same encryption layer, the same contract, and the same audit pipeline.

Our SDK lifts the internal codebase into a vendor-neutral set of packages. Any firm can verify a Crivacy-issued credential trustlessly by reading the CrivacyKYC contract directly, with no off-chain trust on Crivacy.

03 · Verify

On-chain verification

Every credential Crivacy issues is a confidential record on the CrivacyKYC contract, minted by our operator. A firm calls verifyDisclosure(), which reads the contract on Sepolia and returns the plaintext lifecycle plus encrypted handles. A firm granted per-firm access decrypts only the boolean eligibility verdict via the Zama relayer. Authenticity is established on-chain, not against Crivacy's word.

CrivacyKYC contract
0x91f410FfCF51abd0389890968b243bb9A32Eb94B
Network
Sepolia
04 · Standards

Confidential by design

The six sensitive fields (level, human score, identity, liveness, address, sanctioned) are encrypted with FHE and keyed to the user's wallet. The user decrypts their own data; a firm decrypts only a yes or no; Crivacy is the gatekeeper that issues and grants. All three roles stay synchronized through FHE.

crivacy-fhe / docs
crivacy-fhe-credential-sdk.md
05 · Contribute

Contribute

The SDK is community-friendly. Adapters for additional KYC vendors (Onfido, Veriff, Au10tix, Jumio, …) are the most-requested contribution.

© 2026 Crivacy. The @crivacy-fhe SDK is licensed under MIT.