> 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-presentations.md). # Verifiable Presentations From the W3C's perspective, a "verifiable presentation" expresses data derived from one or more verifiable credentials, ensuring the verifiability of the data's authorship. Therefore, holders can extract specific information from their pool of verified credentials and compile it into context-specific presentations of personal data. These newly crafted composite proofs, or presentations, are then dispatched to verifiers, who assess their authenticity. Essentially, verifiable presentations encompass three fundamental elements: * Presentation metadata * One or more verifiable credentials * Presentation proof Based on the W3C's depiction of verifiable presentations, the illustration below illustrates the constituents and their interconnection. The presentation, denoted by the dark blue background, incorporates metadata (in purple) and references one or more verified credentials (with a light blue background). Similarly, the credential consists of metadata (in blue) alongside claims (in green). In this instance, the claim asserts that Bob, the credential's subject, holds a bank account with the specified number. The presentation and the credentials are accompanied by digital signatures as evidence of the data's validity. --- # 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-presentations.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.