> 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/pushing-a-message/waiting-for-the-cross-chain-execution.md).

# Waiting for the cross-chain execution

<figure><img src="/files/7ju63cY9RHKGg4QUqW8r" alt=""><figcaption></figcaption></figure>

Here’s what happens after you send the message:

1. **Message Dispatch on Sepolia**:
   * When `sendMessageToChiado` is called on the **SepoliaSender** contract, the message is dispatched through **Yaho** on Sepolia.
   * The message is sent with the **targetChainId**, **threshold**, **reporters**, and **adapters**, and the data (in this case, the message string).
2. **Oracles and Relaying**:
   * Hashi’s **oracles** pick up the message and relay it to **Chiado**.
   * The oracles validate the message and check the block headers for consensus.
3. **Message Receipt and Callback on Chiado**:
   * On **Chiado**, the **Yaru** contract receives the message and triggers the `onMessage` function on the **ChiadoReceiver** contract.
   * The callback validates the message by ensuring that the message is from the expected **Yaru** contract, the **source chain**, and the correct **sender**.
   * After validation, the message is decoded and stored in the contract.

***

#### **Example Scenario**

* You deploy **SepoliaSender** on **Sepolia** and configure it with the appropriate **Yaho** contract and oracle parameters.
* You deploy **ChiadoReceiver** on **Chiado** to handle the incoming message and validate it against Hashi’s oracle system.
* When you call `sendMessageToChiado` from **SepoliaSender**, the message is dispatched to **Chiado**, where the callback function processes it and updates the state.


---

# 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/pushing-a-message/waiting-for-the-cross-chain-execution.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.