> For the complete documentation index, see [llms.txt](https://docs.teranode.group/tng-identity-documentation/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.teranode.group/tng-identity-documentation/self-sovereign-identity-knowledge/some-of-the-critical-components-of-decentralise-id/verifiable-credentials.md). # Verifiable Credentials Organizations can issue their degrees, IDs, licenses, and more as verifiable digital credentials securely stored in a digital identity wallet. This wallet is a digital counterpart to a physical one, accessible via mobile applications on phones, computers, or even cloud-based servers. Verifiable Credentials, a digital and cryptographically secure iteration of both paper and digital credentials, reliably validate aspects of one's identity or qualifications. Individuals can then present these credentials to organizations requiring verification, envisioning a digital landscape where identity documents, academic achievements, licenses, and more are instantly verifiable. ### Standards and Protocols The Verifiable Credentials Data Model 1.0, established by the World Wide Web Consortium (W3C), serves as a standard for digital credentials. When credentials adhere to this model, they earn the title of Verifiable Credentials. This specification ensures credentials are expressed on the web in a cryptographically secure, privacy-respecting, and machine-verifiable manner. The W3C, an international community dedicated to setting web standards, including URL structures and decentralized identifiers, plays a pivotal role in defining these standards. Verifiable Credentials constitute one of the three pillars of Self-Sovereign Identity (SSI), alongside blockchain and decentralized identifiers. SSI empowers individuals with control over their digital identities, marking a significant shift in the approach to digital identity management. --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://docs.teranode.group/tng-identity-documentation/self-sovereign-identity-knowledge/some-of-the-critical-components-of-decentralise-id/verifiable-credentials.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.