Skip to main content
Contact the AIR team to enable them for your partner account before you start: Partner with us.
Iden3 credentials use a BJJ_SIG_2021 signature and the W3C Verifiable Credentials Data Model v1.1 in JSON-LD form. Holders prove claims with Groth16 zero-knowledge proofs. To issue them, see Issue Iden3 credentials. For when to choose Iden3 over SD-JWT, see Credential formats.

Verification modes

Verification programs for Iden3 credentials can require a zero-knowledge proof and choose where it is checked: For Iden3 programs, verifiablePresentation.verifiableCredential holds W3C Verifiable Credential objects whose credentialSubject contains the disclosed claims. proof is present only when the program requires a zero-knowledge proof. It carries the Groth16 proofValue and publicSignals, plus transactionHash for on-chain programs. Programs with several ZK queries return one entry per query. See VerifiablePresentationProof in the SDK reference.
When an Iden3 program does not require a zero-knowledge proof, the presentation has no proof block. It is unsigned and carries no cryptographic guarantee; the verification session status is the only trust anchor.
Iden3 credentials are always stored on-chain, in DStorage, as an envelope encrypted to the holder. DStorage operators and AIR see only ciphertext, never the claims. Verification is a separate step: it runs on-chain through the Universal Verifier only when the program sets on-chain ZKP verification, and off-chain otherwise.