Standards and Protocols

Technical summary of the standards and protocols supported by the Edge Agent SDK

Secure Channel

	Description
DIDComm V1	DIDComm V1 over HTTP/s is used by the Edge Agent to transmit and receive E2EE messages (credential exchanges, proof presentations, chat messages, etc).

Credential & Presentation Formats

	Description
Anoncreds V1	Hyperledger Anoncreds V1 credentials and presentation can be used by the Edge Agent. Allowing the full zero-knowledge proof capabilities of Anoncreds to be taken advantage of by applications.
W3C VCs/VPs	W3C Verifiable Credentials and Verifiable Presentations using Linked Data Proofs are supported by the Edge Agent.
SD-JWT VC	IETF SD-JWT VCs are supported by the Edge Agent.

Credential & Proof Exchange

	Description	VC/VP Formats	Other
AIP1	Hyperledger Aries protocols from the AIP1 suite can be used to receive credentials and present proofs. This includes the protocols issue-credential-v1 and present-proof-v1 respectively.	Indy
AIP2	Hyperledger Aries protocols from the AIP2 suite can also be used to receive credentials and present proofs. This includes the protocols issue-credential-v2 and present-proof-v2 respectively.	Indy Anoncreds Aries LD Proof (W3C) DIF Presentation Exchange (W3C)
OID4VCI 🧪	OpenID4VCI Draft 13 (Implementor's Draft 1.0) protocol can be used to receive credentials from OpenID4VC issuers.	SD-JWT VC	DID binding Pre-authorization flow 🚧 JWK binding 🚧 authorization flow batch issuance
OID4VP 🧪	OpenID4VP Draft 21 protocol can be used to present credentials to OpenID4VP verifiers.	SD-JWT VC W3C Linked Data Proof	DID-based verifiers direct_post flow 🚧 fragment/ redirect flow

🧪 Experimental OpenID4VC 🧪

Given the draft statuses on OpenID4VC protocols, the Edge Agent implementation is considered experimental and highly subject to breaking changes going forward. Current interoperability testing targets for this implementation include Credo-ts & ACA-py.

Supported DID Methods

	Description	Resolve	Create
did:key	DID Keys can be used by the Edge Agent. They are particularly useful for creating a holder binding with some entity (e.g. W3C VC)
did:jwk	DID JWKs can be used by the Edge Agent. Like did:key, they are ideal for holder bindings, and have seen adoption in the OpenID4VC ecosystem.
did:peer	did:peer V4 is used by the Edge Agent in the process of establishing peer to peer connections.
did:cheqd	DID Cheqd is supported by the Edge Agent for DID and Anoncreds resolution. This method is a highly attractive public DID type, as it bridges modern DID features with an open decentralized ledger.
did:web	Resolution of DID Web is supported by the Edge Agent. This method is one of the simplest public DID methods, but has gained adoption for it's simplicity in many OpenID4VC implementations.
did:sov	Sovrin DIDs and Anoncreds can be resolved by the Edge Agent against the configured sovrin network (any indy network). Supporting the public DID type preferred by many Aries Issuers.
did:indy	🚧 Coming soon.. (replacing vague did:sov usage)

Other Protocols

Some other major protocols supported by Edge Agent include (but not limited to):

	Description
AIP2 Connection Protocols	Out of Band protocol (RFC 0434) & DIDExchange protocol (RFC 0023) is supported by the Edge Agent as a means for bootstrapping DIDComm connections.
AIP1 Connection Protocol	The AIP1 connection protocol (RFC 0160) is supported by the Edge Agent as a means for bootstrapping DIDComm connections.
Aries Basic Messages	The AIP2 protocol for exchanging text messages along a DIDComm connection (RFC 0095) is supported by the Edge Agent (see Messaging).
Aries BBS+ Derived W3C VCs	As an extension to supporting W3C credentials, the Edge Agent can receive and derive selectively disclosed variants of BBS+ signed credentials (as described in RFC 0646). This means the agent can selectively disclose a subset of their BBS+ W3C credential attributes when performing a presentation.
OpenID SIOPv2	🚧 Coming soon..

Data Encryption

All Agent wallet data (Connections, Credentials, Keys, Exchange states, Messages, etc) is encrypted at rest, using a combination of Aries Askar and SQLite encryption.