Below is the AFGO implementation status of all AIP 2.0 Aries RFCs, divided roughly by topic.
Base Requirements
Base Aries Concepts
[x] 0003-protocols
[x] 0004-agents
[x] 0005-didcomm
[x] 0011-decorators
[x] 0046-mediators-and-relays
[x] 0050-wallets
[x] 0094-cross-domain-messaging
General Functionality
[x] 0008-message-id-and-threading
[ ] 0017-attachments: links and sha256 not supported
[x] 0020-message-types
[x] 0047-json-LD-compatibility
[x] 0519-goal-codes: supported in protocols that have a goal code, and exposed to controller APIs for business logic to accept/reject/negotiate/etc.
[x] 0015-acks
[ ] 0019-encryption-envelope
[x] Authcrypt
[ ] Anoncrypt
[x] 0025-didcomm-transports: supports HTTP(S) and Websocket
[x] 0035-report-problem: minimal compliant implementation. Used in introduce, issue credential v2, and present proof v2 protocols. Emits problem report messages with description.code, and abandons on receipt.
[x] 0044-didcomm-file-and-mime-types: AFGO doesn't save messages as files, but does use media type profiles for configuring and negotiating envelope version.
[x] 0360-use-did-key
[x] 0627-static-peer-dids
Base Protocols
[x] 0023-did-exchange
[ ] 0048-trust-ping
[ ] 0183-revocation-notification
[x] 0434-outofband: as-yet still tightly coupled to didexchange, decoupling is a current WIP
[x] 0453-issue-credential-v2
[x] 0454-present-proof-v2
[ ] 0557-discover-features-v2
Sub-targets
Mediator coordination
[x] 0211-route-coordination: no support for Key List Messages and Key List Query.
[x] 0092-transport-return-route: supports only transport route option all.
Below is the AFGO implementation status of all AIP 2.0 Aries RFCs, divided roughly by topic.
Base Requirements
Base Aries Concepts
General Functionality
links
andsha256
not supporteddescription.code
, and abandons on receipt.Base Protocols
Sub-targets
Mediator coordination
all
.Indy-based Credentials
JSON-LD-based Credentials
BBS+-based Credentials
DIDComm v2 Prep
Chat