You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Aries AIP and RFCs Supported in Aries Cloud Agent Python
This document provides a summary of the adherence of ACA-Py to the Aries Interop
Profiles,
and an overview of the ACA-Py feature set. This document is
manually updated and as such, may not be up to date with the most recent release of
ACA-Py or the repository main branch. Reminders (and PRs!) to update this page are
welcome! If you have any questions, please contact us on the #aries channel on
Hyperledger Rocketchat or through an issue in this repo.
Coming Soon: An aries-mediator-service repository that is a pre-configured, production ready Aries Mediator Service based on a released version of ACA-Py.
Supports only JSON-LD Credentials using the Ed25519Signature2018, BbsBlsSignature2020 and BbsBlsSignatureProof2020 signature suites.
Supports the DIF Presentation Exchange data format for presentation requests and presentation submissions.
DID Methods
Method
Supported
Notes
did:sov
✅
did:web
✅
Resolution only
did:key
✅
did:peer
⚠️
AIP 1.0-based did:peer DIDs are used, meaning the DIDs are not prefixed with did:peer and are not following the conventions of AIP 2.0's RFC 0627: Static Peer DIDs
Aries Askar provides equivalent/evolved secure storage and cryptography support to the "indy-wallet" part of the Indy SDK. Available in ACA-Py (activated using a startup parameters but not yet widely used. When using Askar, other Indy SDK capabilities are handled by Indy Shared RS (AnonCreds) and Indy VDR (Indy ledger interactions).
Multi Indy ledger support (with automatic detection)
✅
Support added in the 0.7.3 Release.
Persistence of mediated messages
🚧
Messages are currently stored in an in-memory and so are subject to loss in the case of a sudden termination of an ACA-Py process. The in-memory queue is properly handled in the case of a graceful shutdown of an ACA-Py process (e.g. processing of the queue completes and no new messages are accepted). Work is underway to add useful external queues handling, including support for multiple external queue implementations (e.g., redis and kafka).
Storage Import & Export
⚠️
Supported by directly interacting with the indy-sdk or Aries Askar (e.g., no Admin API endpoint available for wallet import & export). Aries Askar support includes the ability to import storage exported from the Indy SDK's "indy-wallet" component.
Supported RFCs
AIP 1.0
All RFCs listed in AIP 1.0 are fully supported in ACA-Py. The following table
provides notes about the implementation of specific RFCs.
ACA-Py currently supports HTTP and WebSockets for both inbound and outbound messaging. Transports are pluggable and an agent instance can use multiple inbound and outbound transports.
Not using DIDDoc conventions yet, still using DID format of 0160-connections (which is incorrect and outdated). Also using incorrect format for did:peer (or not using a did: prefix at all)
Creating and resolving did:key DIDs is supported, but not all protocols are updated yet to use did:key. This is a breaking change for AIP 1.0 -> AIP 2.0.
Rarely (never?) used, and in implementing the V2 version of the protocol, the V1 version was found to be incomplete and was updated as part of Release 0.7.3