> For the complete documentation index, see [llms.txt](https://crosschain-alliance.gitbook.io/hashi/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://crosschain-alliance.gitbook.io/hashi/getting-started/quick-start/reading-foreign-state/setting-the-scene.md).

# Setting the scene

What we have:

\------

What we need:

* The verification on **Gnosis Chain** chain of USDC total supply on **Optimism**.

How Hashi enables the Event verification:

* With **HashiAPI:** a offchain component used to retrieve the **Storage Proof** of a specific storage slot (the one holding the USDC total supply).
* With **HashiProver:** a onchain contract provided by Hashi which can verify the block proof provided by **HashiAPI**. **HashiProver** must be deployed on the target chain (**Gnosis Chain** in this case) and can be used in a custom contract which can use the Event proof verification provided by **HashiProver** itself.
* The proof will be verified using the latest block header that was relayed to Hashi from **Optimism** to **Gnosis Chain** (check the [Hashi explorer](/hashi/meta/explorer.md)).

Steps followed in this example:

* Fetch the storage proof for the USDC total supply on **Optimism**.
* Deploy a custom contract on **Gnosis Chain** that will verify the event proof using **HashiProver**.
* Submitting the proof to the custom contract.


---

# 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://crosschain-alliance.gitbook.io/hashi/getting-started/quick-start/reading-foreign-state/setting-the-scene.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.