Aries Framework Go is following many open source standards and specifications from,
Aries Framework Go is following many standards from Decentralized Identity Foundation eco system for credential interactions.
Notable ones are,
- DIDComm Messaging v2.0: Version 2.0 od DIDComm Messaging to provide a secure, private communication methodology built atop the decentralized design of DIDs.
- Presentation Exchange v2.0.0: An advanced form of credential request standard which codifies a data format Verifiers can use to articulate proof requirements, and a data format Holders can use to describe proofs submitted in accordance with them. Mainly used in Present Proof Protocol and Aries Verifiable Credential Wallet implementation.
- Confidential Storage v0.1: For secured storage implementation, also know as Encrypted Data Vault.
- WACI Presentation Exchange: Wallet and credential interaction standards using DIDComm.
Notable ones are,
- Universal Wallet 2020: Implemented as Aries Verifiable Credential Wallet implementation.
- WACI Presentation Exchange: Wallet and credential interaction standards using DIDComm in Present Proof Protocol, Issue Credential Protocol and Aries Verifiable Credential Wallet.
- Verifiable Presentation Request Specification v0.1: Standards for requesting credentials to share from wallet. Used in Aries Verifiable Credential Wallet implementation.
- Verifiable Credentials Data Model v1.1: For all the verifiable credential data model operations.
- JSON-LD v1.1: For JSON-based Serialization for Linked Data.
- Linked Data Proofs v1.0: For generating JSON-LD based linked data proofs.
- Decentralized Identifiers (DIDs) v1.0: For signing and verifying verifiable credentials and presentations.
- WebKMS v0.7: For implementing cryptographic key management systems for the wallet.
- Decentralized Identifier Resolution (DID Resolution) v0.2: Followed for resolving various decentralized identifiers.
List of the notable aries-rfcs implemented by Aries Framework Go,
- 0348: Transition Message Type to HTTPs
- 0003: Protocols
- 0004: Agents
- 0005: DID Communication
- 0008: Message ID and Threading
- 0011: Decorators
- 0015: ACKs
- 0017: Attachments
- 0019: Encryption Envelope
- 0020: Message Types
- 0023: DID Exchange Protocol 1.0
- 0025: DIDComm Transports
- 0035: Report Problem Protocol 1.0
- 0036: Issue Credential Protocol 1.0
- 0037: Present Proof Protocol 1.0
- 0044: DIDComm File and MIME Types
- 0046: Mediators and Relays
- 0047: JSON-LD Compatibility
- 0092: Transports Return Route
- 0094: Cross-Domain Messaging
- 0095: Basic Message Protocol 1.0
- 0160: Connection Protocol
- 0211: Mediator Coordination Protocol
- 0302: Aries Interop Profile
- 0360: did:key Usage
- 0434: Out-of-Band Protocol 1.1
- 0453: Issue Credential Protocol 2.0
- 0454: Present Proof Protocol 2.0
- 0510: Presentation-Exchange Attachment format for requesting and presenting proofs
- 0519: Goal Codes
- 0587: Encryption Envelope v2
- 0593: JSON-LD Credential Attachment format for requesting and issuing credentials
- 0627: Static Peer DIDs
- 0646: W3C Credential Exchange using BBS+ Signatures
- 0032: Message Timing
- 0021: DIDComm Message Anatomy
- 0028: Introduce Protocol 1.0
- 0056: Service Decorator
- 0067: DIDComm DID document conventions
- 0074: DIDComm Best Practices
- 0124: DID Resolution Protocol 0.9
- 0270: Interop Test Suite
- 0309: DIDAuthZ
- 0317: Please ACK Decorator
- 0335: HTTP Over DIDComm
- 0346: DIDComm Between Two Mobile Agents Using Cloud Agent Mediator
- 0351: Purpose Decorator
- 0511: Credential-Manifest Attachment format for requesting and presenting credentials