> For the complete documentation index, see [llms.txt](https://docs.cira.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cira.app/cira-app-2.0/overview/multi-sender.md).

# Multi-Sender

Our multi-sender dApp is an efficient tool designed for mass distribution of digital assets on various blockchain networks. Here's how it stands out:

* **Multi-Asset Distribution:** It can send both native blockchain currencies (like ETH on Ethereum) and tokenized assets, catering to diverse transaction needs.
* **Multiple Chain Support:** The dApp operates on several blockchain networks, offering users the flexibility to choose their preferred blockchain.
* **No Cross-Chain Transfers:** While it supports multiple chains, it does not facilitate cross-chain transfers. Each transaction occurs within the boundaries of its native blockchain.
* **Mass Transactions:** Designed for efficiency, it allows users to send assets to multiple recipients in a single transaction, saving time and reducing network fees.
* **User-Friendly Interface:** The dApp features an intuitive interface, making it accessible for users with varying levels of blockchain experience.

This dApp is an ideal solution for users looking to execute batch transactions on different blockchains without the complexity of cross-chain transfers.


---

# 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://docs.cira.app/cira-app-2.0/overview/multi-sender.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.