> 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/verifying-foreign-event/setting-the-scene.md).

# Setting the scene

What we have:

* A **ERC20** `Transfer` **Event** emitted in **Sepolia** USDC contract**.**

What we need:

* The verification on **Chiado** chain of the actual **Sepolia** `Transfer` **event**.

How Hashi enables the Event verification:

* With **HashiAPI:** a offchain component used to retrieve the E**vent Proof** for the specific Sepolia Event emitted.
* 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 (**Chiado** in this case) and can be used in a custom contract which can use the Event proof verification provided by **HashiProver** itself.

Steps followed in this example:

* Fetch the event proof for `Transfer` event from **Sepolia**.
* Deploy a custom contract on **Chiado** 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 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://crosschain-alliance.gitbook.io/hashi/getting-started/quick-start/verifying-foreign-event/setting-the-scene.md?ask=<question>&goal=<endgoal>
```

`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.