> For the complete documentation index, see [llms.txt](https://dev.ishare.eu/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://dev.ishare.eu/version-3.0/introduction/specific-technical-standards/verifiable-credentials-vc.md).

# Verifiable Credentials (VC)

The iSHARE Trust Framework supports Verifiable Credentials adhering to W3C Verifiable Credentials Data Model 2.0 as a technical standard for representing verifiable identity, adherence, and authorisation information.

This functionality complements the existing OAuth 2.0 and OpenID Connect 1.0 standards within iSHARE, offering an additional, decentralised mechanism for establishing trust across data spaces. VCs enable flexible use across both machine-to-machine (M2M) and human-to-machine (H2M) contexts.

### Associated Protocols

The iSHARE specifications refers to following standards to enable issuance and verification of the VCs:

* For human-to-machine interaction:
  * [OpenID for Verifiable Credential Issuance](https://openid.net/specs/openid-4-verifiable-credential-issuance-1_0.html) (OID4VCI): defines how credentials are securely issued using OAuth 2.0-compatible flows.
  * [OpenID for Verifiable Presentations ](https://openid.net/specs/openid-4-verifiable-presentations-1_0.html)(OID4VP): defines how holders present credentials and how verifiers validate them in a standardised request/response exchange.
* For machine-to-machine interaction:
  * [Decentralized Claims Protocol](https://eclipse-dataspace-dcp.github.io/decentralized-claims-protocol/v1.0/) (DCP): defines how credentials are issued and presented in a data space machine-to-machine context.

These protocols ensure that credential flows integrate seamlessly with iSHARE authorisation flows while remaining interoperable with external wallets and identity ecosystems such as eIDAS 2.0.

### Backwards Compatibility and Hybrid Use

To maintain backward compatibility, iSHARE supports a hybrid trust model where either Verifiable Credentials or existing JWT-based tokens can be used.

This allows gradual adoption of VC-based trust interactions without disrupting existing authorisation and identity processes.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://dev.ishare.eu/version-3.0/introduction/specific-technical-standards/verifiable-credentials-vc.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.