Skip to content

7. Supported Credential Formats and -Exchange Protocols, Wallets and DID

7.1 DID Methods

did:web did:ebsi did:elsi did:key did:keri did:op
Tagus X
Loire X
Danube X [1] via extension [2] via extension [2] X [1] via extension [2] via extension [2]

Note

  1. The did method is directly supported by the Gaia-X Basic Functions component of the Danube Gaia-X Core Engine.
  2. The did method may be directly supported by a suitable extension of the Gaia-X Core Engine.

In the table, the following did methods are mentioned:

  • did:ebsi (European Blockchain Services Infrastructure; now the Europeum EDIC)
  • did:elsi (linked to eIDAS)
  • did:key (equivalent to allowing completely anonymous participants)
  • did:keri (GLEIF)
  • did:op (Ocean Protocol) or other DLT-based methods

7.2 Credential Formats

jws2020 vc-jwt
Tagus X
Loire X
Danube X

where: - jws2020: JSON Web Signature 2020 - vc-jwt: Verifiable Credential as JSON Web Token as specified in Securing Verifiable Credentials using JOSE and COSE

7.3 Credential Exchange Protocols

VC-API OpenID DIDCOMM Eclipse DCP CHAPI WACI
Tagus X
Loire X X
Danube X X

where:

  • OpenID: Open ID Connect
  • DIDComm: Decentralized Communication
  • Eclipse DCP: Eclipse Decentralized Claims Protocol
  • VC-API: Verifiable Credential API
  • CHAPI: Credential Handler API
  • WACI: Wallet and Credential Interactions

Note

Regarding Danube, these DID Methods, Credential Formats and Credential Exchange will only be in the initial implementation, more formats and protocols might be supported by external extensions.

Suggest a modification