# Multi-Chain Interaction

Modern applications require interaction with multiple blockchains for different functionalities, such as payments, identity management, and data storage. This trend is accelerating with the increasing adoption of Layer-1 and Layer-2 solutions.

Traditional synchronized and even light clients are impractical for multi-chain interaction due to their resource-intensive nature. Trusted RPC endpoints are also not a viable solution, as they require users to blindly trust responses without cryptographic verification, introducing centralization risks and potential attack vectors.

Stateless and trustless clients offer a scalable and trustless alternative. As long as cryptographic proofs are available, these clients can efficiently retrieve and verify data from multiple blockchains without relying on trusted intermediaries. This approach is particularly beneficial for IoT applications, mobile applications, and web-based platforms, where devices operate under strict resource constraints but still require secure blockchain interaction.

By leveraging stateless verification, blockchain-based applications can seamlessly integrate with multiple chains, ensuring efficiency, scalability, and security without unnecessary synchronization overhead.


---

# Agent Instructions: 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:

```
GET https://corpus-core.gitbook.io/whitepaper-colibri-stateless/technical-concept/multi-chain-interaction.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
