AnonCreds

Protocolo de Identidad

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 .

Fundación

Detalles

Licencia Permissive: 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)
Estado de Desarrollo 🟢 Activo
Propietario LF 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
Órgano de Gobierno LF Decentralized Trust, AnonCreds Project (charter and maintainer process in the anoncreds/governance repository)
País International (an LF Decentralized Trust project; editors named across several organisations; the cited sources give no single country)
Año de Inicio 2017
Stack Rust 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
Financiamiento Not stated by the project.
Última Investigación 29 oct 2026

Vista de topología

Esta herramienta en el centro y lo que se relaciona directamente con ella. Cada línea nombra el tipo de relación.

Vista de topología: AnonCredsEsta herramienta en el centro y lo que se relaciona directamente con ella. Cada línea nombra el tipo de relación.AnonCredsAnimo (Implementaciones conformes, Protocolo hablado por)Animodid:cheqd (Implementaciones conformes, Protocolo hablado por)did:cheqddid:indy (Implementaciones conformes, Protocolo hablado por)did:indyDIDComm (Implementaciones conformes)DIDCommDIDs (Cumple con)DIDsDock.io / Truvera (Implementaciones conformes, Protocolo hablado por)Dock.io /TruveraKeyring (Implementaciones conformes)KeyringNorthern Block / 4sure (Implementaciones conformes, Protocolo hablado por)NorthernBlock / 4sureVCs (Cumple con)VCs
  • Animo (Herramienta): Implementaciones conformes, Protocolo hablado por
  • did:cheqd (Herramienta): Implementaciones conformes, Protocolo hablado por
  • did:indy (Herramienta): Implementaciones conformes, Protocolo hablado por
  • DIDComm (Herramienta): Implementaciones conformes
  • DIDs (Herramienta): Cumple con
  • Dock.io / Truvera (Herramienta): Implementaciones conformes, Protocolo hablado por
  • Keyring (Herramienta): Implementaciones conformes
  • Northern Block / 4sure (Herramienta): Implementaciones conformes, Protocolo hablado por
  • VCs (Herramienta): Cumple con

Abrir en el Explorador de grafo

Dominios de Caso de Uso

Capacidades

Identidad soberana Atestaciones portátiles Divulgación contextual

Protocolo de Identidad Atributos

Orígenes Privacy-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
Base de Datos N/A
Lenguaje de Consulta N/A
Formatos de Datos AnonCreds objects (schema, credential definition, revocation registry definition and status list, credential offer, request, credential, presentation) as JSON; the specification defines each object
Soporte Móvil Library-level: the Rust library has bindings used by wallet applications; no application of its own
Soporte Web Library-level only
Aplicaciones Nativas Library-level: the Rust library is embedded in wallets and agents
Términos Free and open: code under Apache-2.0 and the specification under the Community Specification License 1.0
Fondos Not stated by the project.
Basado En The 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
Permisos Issuers decide who receives credentials; holders decide what to disclose; verifiers decide which proofs to accept
Autenticación e Identidad A 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 Almacenamiento Schemas, 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
Interoperabilidad Used 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
Portabilidad de Datos Credentials 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
Gobernanza y Toma de Decisiones Project charter and maintainer processes in the anoncreds/governance repository; the specification is the output of the AnonCreds Working Group's consensus
Madurez del Protocolo / Estandarización v1.0 Draft specification under a community specification licence, with a reference implementation and years of deployment; not a W3C or IETF standard
Estándares de Identidad Predates 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 Soportados Registry-dependent; originally did:sov and Indy-based methods, with registry-agnostic identifiers in v1.0 (details are in the specification)
Gestión de Claves The issuer holds the credential-definition private key; the holder keeps a link secret; keys are managed by the implementing wallet or agent
Tipos de Credenciales Zero-knowledge verifiable credentials with revocation; attributes encoded as integers
Método de Verificación The verifier checks a zero-knowledge presentation against the published credential definition and revocation status list, including predicates and non-revocation proofs
Funciones de Privacidad Zero-knowledge selective disclosure and predicates, unlinkable presentations, and link-secret binding so multiple credentials prove one holder without a shared identifier
Métodos de Autenticación Zero-knowledge proofs of credential possession; the issuer authenticates through its published definition
Mecanismo de Revocación Type-3 accumulator-based revocation registries with status lists; the holder proves non-revocation without revealing the credential
Tipos de Agentes Soportados Issuers, holders (provers) and verifiers: individuals, organisations and devices
Tipos de Billetera/Cliente Wallets and agents that embed the library; the project's own code is a library
Mecanismos de Recuperación Not stated by the project.
Cumplimiento / Regulaciones Not stated by the project.
Protocolos de Intercambio de Credenciales Credential offer, request and presentation flows defined in the specification; messaging is carried by the surrounding agent protocols
Marco de Confianza Trust in issuers' published credential definitions on a verifiable data registry, with the verifier choosing which issuers to accept
Modelo de Costos Free to use; registry publication costs depend on the chosen registry
Resistencia a la Censura Moderate: verification needs only the published definition, but publishing and revocation depend on the chosen registry

Relaciones

Cómo se conecta esta herramienta con otras herramientas y organizaciones, según relaciones revisadas por el responsable de datos de OpenHaven. Describen cómo se conectan los proyectos, no su calidad.

Cumple con