DIDComm in Hyperledger Aries Clause Samples
The "DIDComm in Hyperledger Aries" clause defines the use of the DIDComm messaging protocol within the Hyperledger Aries framework for secure, interoperable communication between decentralized identities. In practice, this clause specifies that parties will use DIDComm to exchange encrypted messages, such as credential offers or proofs, leveraging Aries agents to facilitate these interactions. By standardizing on DIDComm, the clause ensures consistent, secure, and privacy-preserving communication, addressing interoperability and security challenges in decentralized identity ecosystems.
DIDComm in Hyperledger Aries. Hyperledger Aries [24] builds on top of Hyperledger Indy, and uses Indy ledger as just one of the possible underlying Decentralized Ledgers (in fact, as of today, interfacing non-Indy ledgers is ongoing in the Aries community). The Aries community [25] itself declares that “▇▇▇▇▇ grew out of the work in Hyperledger Indy to create technologies for managing decentralized identity. Indy provides a specific blockchain purpose-built for identity. The tools created in Indy for building agents are being migrated to Aries and extended to be blockchain-agnostic. Functionality related to the Indy ledger will remain in Indy.” In fact, Aries is a large initiative which includes several working groups and produced more implementations of the same functional component, including: ● aries-cloudagent-python (Aca-py) [27]: the Python implementation is based on DIDComm-V1 and uses Indy as a Ledger through Indy SDK. The agent is suitable for all non-mobile agent applications and has production deployments. Many SSI implementations are already in place based on this component, including [28] and [29]. ● aries-staticagent-python: a configurable server-side agent that does not use persistent storage. To use it, keys are pre-configured and loaded into the agent at initialization time. ● aries-framework-dotnet: it can be used for building mobile (via Xamarin) and server-side agents and has production deployments. The framework uses Indy through the indy-sdk ● aries-framework-go: An innovative and technically interesting pure go language (golang) framework that does not currently embed the Indy SDK and works on supporting a golang-based verifiable credentials implementation. The development is in progress and some features are based on still “experimental projects” like go-mobile. The most recent version of the framework [26] provides 3 different implementations on the same common communication libraries: o aries-agent-rest: a Command Line Interface (CLI) implementation of a server-side framework. Following the framework-controller paradigm, it exposes an HTTP interface for its companion controller. Differently from other frameworks, it does not rely on Indy SDK. A golang-based verifiable credentials implementation is in progress. o aries-agent-mobile: uses the experimental go-mobile tool [30] to produce SW libraries used for Android and Ios. o aries-js-worker: a javascript interface to Aries Framework Go, for use in node.js or directly in the browser.