Anonymous Credentials: a verifiable-credential format that uses zero-knowledge proofs, so a holder can prove claims from credentials without revealing the credentials or a correlatable identifier. An issuer publishes a schema and a credential definition (with a public key), signs a credential for a holder, and can publish a revocation registry; the holder later produces a proof that discloses only chosen attributes or predicates (for example 'over 18') and proves the credential is not revoked, linking multiple credentials through a hidden master secret. The specification formalises an implementation in use since 2017, first in Hyperledger Indy and now the Hyperledger AnonCreds project, now hosted at the LF Decentralized Trust. The v1.0 draft aims to be ledger-agnostic .
LicençaPermissive: code under Apache-2.0; the specification text under the Community Specification License 1.0. https://github.com/anoncreds/anoncreds-spec; https://github.com/anoncreds/anoncreds-rs (Rust reference implementation)
Status de Dev 🟢 Ativo
ProprietárioLF Decentralized Trust (Hyperledger AnonCreds project; the GitHub organisation 'anoncreds' describes itself as an LF Decentralized Trust project); the specification's editors include Stephen Curran, Sam Curren and others from IDunion and the Technische Universität Berlin
Órgão de GovernançaLF Decentralized Trust, AnonCreds Project (charter and maintainer process in the anoncreds/governance repository)
PaísInternational (an LF Decentralized Trust project; editors named across several organisations; the cited sources give no single country)
Ano de Início 2017
StackRust reference library (issuer, prover/holder, verifier services) with bindings; CL-signature-based zero-knowledge proofs; schema, credential definition, revocation registry and status-list objects published to a verifiable data registry of the implementer's choice
Financiamento Not stated by the project.
Última Investigação 29 de out. de 2026
Visão de topologia
Esta ferramenta no centro e o que se relaciona diretamente com ela. Cada linha nomeia o tipo de relação.
Animo (Ferramenta): Implementações em conformidade, Protocolo falado por
did:cheqd (Ferramenta): Implementações em conformidade, Protocolo falado por
did:indy (Ferramenta): Implementações em conformidade, Protocolo falado por
DIDComm (Ferramenta): Implementações em conformidade
OrigensPrivacy-preserving credentials for self-sovereign identity, originating in the Hyperledger Indy project and generalised so the credentials no longer depend on one ledger; based on the 'Anonymous credentials with type-3 revocation' work by Khovratovich, Lodder and Parra
Banco de Dados N/A
Linguagem de Consulta N/A
Formatos de DadosAnonCreds objects (schema, credential definition, revocation registry definition and status list, credential offer, request, credential, presentation) as JSON; the specification defines each object
Suporte MóvelLibrary-level: the Rust library has bindings used by wallet applications; no application of its own
Suporte WebLibrary-level only
Aplicativos NativosLibrary-level: the Rust library is embedded in wallets and agents
TermosFree and open: code under Apache-2.0 and the specification under the Community Specification License 1.0
Fundos Not stated by the project.
Baseado EmThe Hyperledger Indy credential implementation and Camenisch-Lysyanskaya signatures, with type-3 revocation (Khovratovich, Lodder, Parra); the v1.0 draft removes the dependency on one ledger
PermissõesIssuers decide who receives credentials; holders decide what to disclose; verifiers decide which proofs to accept
Autenticação e IdentidadeA holder proves possession of credentials with zero-knowledge proofs bound to a hidden link secret; no global identifier is revealed to the verifier
Modelo de ArmazenamentoSchemas, credential definitions and revocation objects are published to a verifiable data registry (originally an Indy ledger, now any supported registry); credentials are held by the holder
InteroperabilidadeUsed with Aries-style agents and a number of registries; the specification calls itself ledger-agnostic in v1.0; interoperability with W3C Verifiable Credentials data models is addressed by separate profiles outside the cited sources
Portabilidade de DadosCredentials are held by the holder and can be presented to any verifier that supports the format; they are bound to the issuer's published definition
Governança e Tomada de DecisãoProject charter and maintainer processes in the anoncreds/governance repository; the specification is the output of the AnonCreds Working Group's consensus
Maturidade / Padronização do Protocolov1.0 Draft specification under a community specification licence, with a reference implementation and years of deployment; not a W3C or IETF standard
Padrões de IdentidadePredates and differs from W3C Verifiable Credentials (it uses its own zero-knowledge format); related to W3C DID practice through Aries and registries
Métodos DID SuportadosRegistry-dependent; originally did:sov and Indy-based methods, with registry-agnostic identifiers in v1.0 (details are in the specification)
Gestão de ChavesThe issuer holds the credential-definition private key; the holder keeps a link secret; keys are managed by the implementing wallet or agent
Tipos de CredenciaisZero-knowledge verifiable credentials with revocation; attributes encoded as integers
Método de VerificaçãoThe verifier checks a zero-knowledge presentation against the published credential definition and revocation status list, including predicates and non-revocation proofs
Recursos de PrivacidadeZero-knowledge selective disclosure and predicates, unlinkable presentations, and link-secret binding so multiple credentials prove one holder without a shared identifier
Métodos de AutenticaçãoZero-knowledge proofs of credential possession; the issuer authenticates through its published definition
Mecanismo de RevogaçãoType-3 accumulator-based revocation registries with status lists; the holder proves non-revocation without revealing the credential
Tipos de Agentes SuportadosIssuers, holders (provers) and verifiers: individuals, organisations and devices
Tipos de Carteira/ClienteWallets and agents that embed the library; the project's own code is a library
Mecanismos de Recuperação Not stated by the project.
Conformidade / Regulamentações Not stated by the project.
Protocolos de Troca de CredenciaisCredential offer, request and presentation flows defined in the specification; messaging is carried by the surrounding agent protocols
Estrutura de ConfiançaTrust in issuers' published credential definitions on a verifiable data registry, with the verifier choosing which issuers to accept
Modelo de CustoFree to use; registry publication costs depend on the chosen registry
Resistência à CensuraModerate: verification needs only the published definition, but publishing and revocation depend on the chosen registry
Relacionamentos
Como esta ferramenta se conecta a outras ferramentas e organizações, a partir de relacionamentos revisados pelo responsável pelos dados do OpenHaven. Descrevem como os projetos se conectam, não a qualidade deles.