# Standards and Protocols

## Secure Channel

<table><thead><tr><th width="202"></th><th>Description</th></tr></thead><tbody><tr><td><strong>DIDComm V1</strong></td><td>DIDComm V1 over HTTP/s is used by the cloud agent to transmit and receive E2EE messages (basic messages, credential exchanges, proof exchanges, etc).</td></tr></tbody></table>

## Credential & Presentation Formats

<table><thead><tr><th width="202"></th><th>Description</th></tr></thead><tbody><tr><td><strong>Anoncreds V1</strong></td><td>The cloud agent supports issuance and presentation of credentials following the <a href="https://hyperledger.github.io/anoncreds-spec/">Hyperledger AnonCreds Specification v1.0</a>. Anoncreds credentials have many privacy-preserving capabilities such as blinded holder bindings, zero-knowledge proofs and selective disclosure.</td></tr><tr><td><strong>W3C VCs/VPs V1</strong></td><td>The cloud agent supports issuance and presentation of W3C credentials following the <a href="https://www.w3.org/TR/vc-data-model/">W3C Verifiable Credentials Data Model v1.1</a> spec, using LD-Proofs (JSON Linked Data Proofs).</td></tr></tbody></table>

## Credential & Proof Exchange

<table><thead><tr><th width="142"></th><th width="339">Description</th><th>Formats</th></tr></thead><tbody><tr><td><strong>AIP1</strong></td><td>Hyperledger Aries protocols from the AIP1 suite can be used to issue credentials and present proofs. This includes the protocols <a href="https://github.com/hyperledger/aries-rfcs/blob/main/features/0036-issue-credential/README.md">issue-credential-v1</a> and <a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0037-present-proof">present-proof-v1</a> respectively.</td><td><ul class="contains-task-list"><li><input type="checkbox" checked>Indy (Anoncreds)</li></ul></td></tr><tr><td><strong>AIP2</strong></td><td>Hyperledger Aries protocols from the AIP2 suite can also be used to issue credentials and present proofs. This includes the protocols <a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0453-issue-credential-v2">issue-credential-v2</a> and <a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0454-present-proof-v2">present-proof-v2</a> respectively.</td><td><ul class="contains-task-list"><li><input type="checkbox" checked><a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0592-indy-attachments">Indy (Anoncreds)</a></li><li><input type="checkbox" checked><a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0593-json-ld-cred-attach">Aries Linked Data Proof (W3C)</a> and <a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0510-dif-pres-exch-attach">DIF Presentation Exchange (W3C)</a></li></ul></td></tr></tbody></table>

## Supported DID Methods

The cloud agent is able to resolve any DID, by use of a universal resolver.

## Other Protocols

Some other notable protocols supported by the cloud agent include (but are not limited to):

<table><thead><tr><th width="180"></th><th>Description</th></tr></thead><tbody><tr><td><strong>AIP1 Connection Protocol</strong></td><td>The cloud agent establishes DIDComm connections using the AIP1 connection protocol (<a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0160-connection-protocol">RFC 0160</a>).</td></tr><tr><td><strong>Aries Basic Messages</strong></td><td>The cloud agent uses the AIP2 basic message protocol for exchanging arbitrary messages along a DIDComm connection (<a href="https://github.com/hyperledger/aries-rfcs/tree/c3b0e2120ad24810598375663b6922b980f85d00/features/0095-basic-message">RFC 0095</a>).</td></tr><tr><td><strong>Aries BBS+ Derived W3C VCs</strong></td><td>The cloud agent supports the issuance of W3C credentials using BBS+ signatures (<a href="https://github.com/hyperledger/aries-rfcs/tree/main/features/0646-bbs-credentials">RFC 0646</a>). This signature allows the holder to selectively disclose a subset of their W3C credential attributes when performing a proof exchange.</td></tr></tbody></table>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.sudoplatform.com/guides/decentralized-identity/cloud-agent/cloud-agent-admin-api/standards-and-protocols.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.