> For the complete documentation index, see [llms.txt](https://guardian.hedera.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guardian.hedera.com/docs/3.7.0/guardian/platform/trustchain.md).

# TrustChain

The Trust Chain is used to establish verifiable and transparent chains of custody for digital environmental assets, ensuring the integrity and reliability of transactions within the Guardian ecosystem.

### Description

The Trust Chain operates by leveraging a decentralized verification process, enabling users to trace the origin and lifecycle of digital assets. At its core, the Trust Chain utilizes cryptographic proofs and blockchain technology to create an unalterable record of transactions, from the creation of a digital asset through to its current state. This process involves generating Verifiable Presentations (VPs) that encapsulate the history of digital assets, and providing a comprehensive view of their journey. This ensures that each asset's provenance is accessible, transparent, and indisputable.

### Benefits

1. **Enhanced Transparency and Trust**: By providing a clear trail of an asset's history, the Trust Chain fosters a level of transparency that builds trust. Stakeholders can verify the authenticity and ownership of assets without relying on centralized authorities.
2. **Improved Security**: The cryptographic foundation of the Trust Chain ensures the security of digital assets. It mitigates the risk of fraud and unauthorized manipulation, safeguarding the interests of all parties involved.


---

# 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://guardian.hedera.com/docs/3.7.0/guardian/platform/trustchain.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.
