> 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/core-concepts/message-dispatching.md).

# Message Dispatching

Beyond block headers, Hashi supports **secure message dispatching** between blockchains. This allows dApps to send messages across chains while ensuring that the messages are verified and valid according to the state of the originating blockchain.

* **How it Works**\
  Messages are dispatched after the validation of block headers, ensuring that any message relayed between two blockchains is consistent with the blockchain state. Hashi uses its **multi-oracle validation system** to verify these messages, making sure that only messages based on valid block headers are dispatched.
* **Use Cases**\
  Message dispatching can be used in cross-chain token transfers, governance voting, or any application where information needs to be relayed from one blockchain to another securely and reliably.


---

# 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/core-concepts/message-dispatching.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.