> For the complete documentation index, see [llms.txt](https://docs.allstake.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.allstake.org/technical-architecture/cross-chain-interoperability.md).

# Cross-Chain Interoperability

Allstake combines Light Clients and Chain Signature to achieve cross-chain interoperability. Allstake synchronizes native (re)staking states from client chains to Allstake Hub on NEAR with reliable cross-chain communication technologies such as Light Clients and Wormhole's message passing solution. Allstake performs operations on client chains with Chain Signature.

Allstake utilizes both classical light clients and ZK light clients that are built between NEAR and client chains. This includes Rainbow Bridge between NEAR and Ethereum, NEAR-IBC, LayerZero and ZK light clients built by Wormhole Foundation and Electron Labs, etc..


---

# 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.allstake.org/technical-architecture/cross-chain-interoperability.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.
