# Establishing Token Authenticity

1. Get the serial number from the Token and check if the Token ID is compatible with Guardian
2. Find the Transaction ID of the minted token.
3. Take the MEMO value (which is the Hedera message timestamp) and add it to the URL after the `/messages/` to get a message from a Hedera Mirror Node, which represents the creation and logging of VP.
4. Check whether the topic ID is valid for Guardian
5. Examine the message contents and take the URL attribute values, which is an IPFS link with CID.
6. VP can be displayed when the above IPFS link is copied and pasted to the browser.
7. VP contents are displayed and verified by checking following contents:
   * Confirm it maps to the appropriate tokenID (this is logically a challenge that the VP represents a response to)
   * Verify signatures, retrieve DIDs as necessary
   * Confirm the MRV data that meets the criteria of the policy.

For a working example, please check [FAQs](/guardian-dev/guardian/faqs.md) Question no. 17.

#### To get a visual representation on the above process, please check [Detailed Architecture Diagram](/guardian-dev/guardian/architecture/schema-architecture.md).


---

# Agent Instructions: 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:

```
GET https://guardian.hedera.com/guardian-dev/guardian/tokens/token-authenticity/how-to-establish-token-authenticity.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.