Communication protocols
A communication protocol is the set of rules that issuers, holders and verifiers follow to send credentials to each other. Each ecosystem in Hovi uses its own protocol. Hovi handles the protocol for you, so you only need to know which one your ecosystem uses.
Why protocols matter
Think of a protocol as an agreed way of posting a letter: everyone uses the same envelope and address format, so the letter arrives intact and the receiver can check who sent it. In the same way, a protocol makes sure a credential reaches the right wallet, and that the verifier can check it hasn't been changed.
In practice, every protocol supports the same three steps:
- The issuer sends a credential to the holder, who stores it in their wallet.
- A verifier asks the holder for a credential, and the holder shares it.
- The verifier checks that the credential is genuine and unchanged.
Protocols by ecosystem
| Protocol | What it is | Used by |
|---|---|---|
| OID4VCI | OpenID for Verifiable Credential Issuance: issues credentials using OpenID standards. The holder usually scans a QR code or opens a link. | EU Digital Identity, Microsoft Entra |
| OID4VP | OpenID for Verifiable Presentations: asks a holder to share a credential and returns it to the verifier. | EU Digital Identity, Microsoft Entra |
| DIDComm v1 | Secure, private messaging between two parties identified by DIDs. The holder and the organization first set up a connection, and credentials are then exchanged over it. | cheqd, Indicio |
| Out-of-Band | Starts a DIDComm connection outside the main channel, for example with a QR code. | cheqd, Indicio |
| Iden3 | Polygon's identity protocol, built around zero-knowledge proofs. The holder can prove a fact without revealing the underlying data. | Polygon |
To see everything each ecosystem supports, see Compatibility.