> For the complete documentation index, see [llms.txt](https://docs.truvera.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.truvera.io/open-source-community/blockchain-sdk/trust-registry.md).
# Trust registry
Verifiable credentials have an advantage over physical documents, because they cannot be forged. However, there is still a fraud risk if a credential is issued by someone that has no authority to do so.
How can a verifier be sure that the credential came from an authorized issuer? And vice-versa, how can a credential holder know which verifiers are trustworthy and that it is okay to share their credentials with them? Trust registry is a solution to answer this problem.
## What is a trust registry?
\
A trust registry is an on-chain list of relationships between issuers and verifiers. It simplifies the process of identifying which issuers and verifiers are trustworthy within a particular ecosystem. These registries serve as secure repositories for identity information, leveraging blockchain technology to ensure its integrity and reliability.
Trust registries are governed by trust frameworks, a set of operating rules that participants of the ecosystem must follow.
## Why use a trust registry
By having a trust registry, credential verifiers do not need to manage a list of valid issuers and holders know which verifiers they can trust to share their credentials with. They only need to trust one Ecosystem administrator. [Ecosystem Tools](/truvera-workspace/ecosystem-tools.md) exemplifies the power of trust registries in creating a network of trusted digital identity issuers and verifiers.
Trust registry contains the following information:
* Name of the Trust Registry and the Governance Framework
* Ecosystem Administrator and Issuers DIDs, Organization Names, Logos and descriptions
* A record associated with the SchemaID, which consists of a mapping from the Issuer DID to the verification prices and set of the Verifier DIDs
---
# 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.truvera.io/open-source-community/blockchain-sdk/trust-registry.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.
