DIDComm

Protocolo de Identidad

Specification for secure, asynchronous, end-to-end encrypted messaging between parties identified by Decentralized Identifiers (DIDs). Defines envelope formats, encryption, signing, threading, transport-independence, and protocol-on-protocol patterns — anything party-to-party that needs DID-rooted authentication and confidentiality can be expressed as a DIDComm protocol. Higher-order protocols (issue-credential, present-proof, etc.) inherit DIDComms security, privacy, decentralization, and transport independence. Works over any transport: HTTP, BlueTooth, SMTP, raw sockets, etc.

Comunidad
Enlaces
Visitar Comunidad

Detalles

Licencia Spec: Apache 2.0; multiple independent implementations (didcomm-rs, didcomm-jvm, didcomm-python, walt.id, SpruceID, Aries family)
Estado de Desarrollo 🟢 Activo
Detalle del Estado de Desarrollo Released — DIDComm v2 reached DIF Approved Spec status July 2022; v2.1 in production
Propietario Decentralized Identity Foundation (DIF) — non-profit standards body; spec maintained by the DIDComm Messaging Working Group
Órgano de Gobierno DIF (DIDComm Messaging Working Group)
País International (DIF: USA-incorporated, global membership)
Año de Inicio 2019
Stack Specification only (no canonical implementation stack); reference implementations in Rust (didcomm-rs by DIF), Python, TypeScript/JavaScript, Java, Go, Swift
Financiamiento DIF (member-funded standards body)
Última Investigación 1 jul 2026

Dominios de Caso de Uso

Identidad y Confianza

Protocolo de Identidad Atributos

Orígenes Hyperledger Aries community (DIDComm v1); DIF migration and v2 redesign 2020-2022
Base de Datos N/A — specification is a transport-layer messaging protocol; persistence is implementation concern (typically wallet-side encrypted message stores)
Lenguaje de Consulta N/A — DIDComm is asynchronous message passing; query patterns are implemented as application-layer protocols (e.g., discover-features, basic-message) running over DIDComm
Formatos de Datos JWE (JSON Web Encryption) + JWS (JSON Web Signature) wrappers; JSON message bodies
Soporte Móvil Yes (transport-agnostic; multiple mobile SDKs and wallet implementations)
Soporte Web Yes (HTTPS transport)
Aplicaciones Nativas Yes (Bluetooth, raw sockets, push-notification mediator patterns)
Términos Open standard, free to implement; DIF IPR protections require working group membership for normative contributions
Fondos Unknown — DIF working group funded by member dues and member-organization staff time; reference implementations developed by member organizations on their own funding (Indicio, Anonyome, Mattr, walt.id) without a published per-spec budget
Basado En W3C Decentralized Identifiers (DIDs); JOSE (JWE/JWS); IETF cryptographic primitives
Permisos Implementation-defined at the DIDComm layer — DIDComm itself does not specify authorization model; subprotocols (issue-credential, present-proof, etc.) define their own permission semantics, and trust is rooted in DIDs of communicating parties
Autenticación e Identidad DID-rooted — sender and recipient identified by DIDs whose keys are used for signing and encryption
Modelo de Almacenamiento Stateless protocol — no message persistence at the protocol layer; mediators may queue messages for offline recipients
Interoperabilidad Multiple independent implementations (Aries, walt.id, SpruceID, didcomm-rs); transport-independent
Portabilidad de Datos High — messages are self-contained signed/encrypted artifacts portable across transports; mediator handoff supported; relationships portable across device changes via key rotation (from_prior JWT)
Gobernanza y Toma de Decisiones DIF DIDComm Working Group governance — open meetings (Mondays 12pm PST), IPR-protected contributions under DIF membership, consensus-driven specification process; chartered January 2020 building on Hyperledger Aries community work; aligns with W3C, IETF, and Aries communities
Madurez del Protocolo / Estandarización DIF Approved Spec (v2 since July 2022); v2.1 current; production deployments in government, travel, and enterprise
Estándares de Identidad W3C DIDs; W3C VCs (commonly carried as DIDComm payloads); DIF DIDComm v2.1
Métodos DID Soportados Any DID method — DIDComm is method-agnostic (did:key, did:web, did:peer, did:ion, did:indy, etc.)
Gestión de Claves Per DID method; DIDComm uses keys from DID documents for signing/encryption
Tipos de Credenciales Transport for any credential format (W3C VC, AnonCreds, mDoc, etc.); not credential-format-specific
Método de Verificación JWS signatures verifiable against DID document keys
Funciones de Privacidad Anoncrypt (anonymous encryption hides sender identity); routing through mediators for metadata privacy; per-message ephemeral keys
Métodos de Autenticación Authcrypt (signed + encrypted) and Anoncrypt (anonymous encryption); DID rotation support for relationship lifecycle
Mecanismo de Revocación Per credential format (DIDComm carries revocation messages but does not define revocation semantics); DID rotation for key compromise
Tipos de Agentes Soportados Edge agents (people, IoT), cloud agents, mediators, routing agents — full agent topology supported
Tipos de Billetera/Cliente Mobile wallets, cloud agents, web wallets; reference implementations in Rust, JavaScript, Python, JVM, .NET
Mecanismos de Recuperación Relationship-level rotation via from_prior JWT mechanism (rotate sender DID and re-establish thread continuity); credential-level recovery handled by carried credential protocols rather than DIDComm itself
Cumplimiento / Regulaciones Used in eIDAS, GDPR, and similar regulatory contexts as the secure communication layer underneath verifiable credential exchange; deployed in EUDI Wallet implementations and Indy/Aries deployments in government identity programs
Protocolos de Intercambio de Credenciales Issue Credential v2, Present Proof v2, Out-of-Band, DID Exchange — all DIDComm sub-protocols
Marco de Confianza Transport-agnostic — works under any trust framework (eIDAS 2.0, TOIP, etc.); used in BC Government, US DHS SVIP, IATA travel, IDUnion
Modelo de Costos Free — open standard, royalty-free under DIF IPR policy; implementation cost limited to chosen libraries and infrastructure
Resistencia a la Censura High — works over any transport including SMTP, Bluetooth, sneakernet; no required server