Standards and Protocols
Technical summary of the standards and protocols supported by the Edge Agent SDK
Last updated
Technical summary of the standards and protocols supported by the Edge Agent SDK
Last updated
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).
Anoncreds V1
W3C VCs/VPs
SD-JWT VC
AIP1
AIP2
OID4VCI 🧪
OID4VP 🧪
🧪 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 & .
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 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 V4 is used by the Edge Agent in the process of establishing peer to peer connections.
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.
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.
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.
🚧 Coming soon..
🚧 Coming soon.. (replacing vague did:sov usage)
Some other major protocols supported by Edge Agent include (but not limited to):
AIP2 Connection Protocols
AIP1 Connection Protocol
Aries Basic Messages
Aries BBS+ Derived W3C VCs
OpenID SIOPv2
🚧 Coming soon..
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.
using Linked Data Proofs are supported by the Edge Agent.
are supported by the Edge Agent.
Hyperledger Aries protocols from the AIP1 suite can be used to receive credentials and present proofs. This includes the protocols and respectively.
Hyperledger Aries protocols from the AIP2 suite can also be used to receive credentials and present proofs. This includes the protocols and respectively.
(Implementor's Draft 1.0) protocol can be used to receive credentials from OpenID4VC issuers.
protocol can be used to present credentials to OpenID4VP verifiers.
Out of Band protocol () & DIDExchange protocol () is supported by the Edge Agent as a means for bootstrapping DIDComm connections.
The AIP1 connection protocol () is supported by the Edge Agent as a means for bootstrapping DIDComm connections.
The AIP2 protocol for exchanging text messages along a DIDComm connection () is supported by the Edge Agent (see ).
As an extension to supporting W3C credentials, the Edge Agent can receive and derive selectively disclosed variants of BBS+ signed credentials (as described in ). This means the agent can selectively disclose a subset of their BBS+ W3C credential attributes when performing a presentation.
All Agent wallet data (Connections, Credentials, Keys, Exchange states, Messages, etc) is encrypted at rest, using a combination of and SQLite encryption.