DIDComm Capability Overview
Sending and receiving cryptographically authenticated messages between DID agents, requesting and verifying verifiable credentials, and authenticating workflow actors via decentralized identity.
What is DIDComm?
DIDComm (Decentralized Identifier Communication) is a protocol for secure, private, authenticated messaging between parties who each control a DID (Decentralized Identifier). Messages are encrypted end-to-end and authenticated with the sender's DID key — no centralized API keys or user accounts required.
Available DIDComm Nodes
| Node Type | Operation | Output |
|---|---|---|
DIDCommSendNode | Send an encrypted message to a DID | { messageId, deliveredAt, status } |
DIDCommReceiveTrigger | Trigger node — inbound DIDComm message starts the workflow | Decoded message body as $json |
VCRequestNode | Request a verifiable credential presentation from an actor | { presentation, holder, credentialType } |
VCVerifyNode | Verify a presented VC against schema and trust registry | { valid, claims, issuer, expiresAt } |
DIDAuthNode | Authenticate a workflow actor via DID challenge/response | { authenticated, did, resolvedAt } |
Relationship to Passport IAM
DIDComm identity operates alongside Passport IAM, not replacing it. A Passport user can link a DID to their account, enabling decentralized identity verification in workflows while still using the Passport actor context ($context.actorId). For external parties without a Passport account, DIDComm provides the identity layer.