> For the complete documentation index, see [llms.txt](https://scalex.gitbook.io/scalex/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://scalex.gitbook.io/scalex/token/omnichain-reflections.md).

# Omnichain reflections

To allow for fastest possible transmission of reflections across chains using LayerZero, we came up with a unique inter-chain communciation protocol.

A swap on a higher gas chain, e.g. Ethereum main net, is transmitted to all lower gas chains. At the same time, the lowest gas chain we are present on is asked for its local state. The lowest gas chain has always the most recent local state since it receives updates from all other chains. That makes it the perfect target for requests. The lowest gas chain (in our example Polygon) then answers to the chain that made the request with its current local state, which the higher gas chain integrates into its respective own local state.

That means in practice, that transactions happening on higher gas chains are always instantly transmitted to lower gas chains (due to the nature of inter-chain communication this might still take a few minutes to settle on all chains). Transactions happening on lower gas chains are reported to the higher gas chains as soon as a transaction happens on them again.

This architecture brings the benefit that users never thave to pay the fees of a higher gas chain when transacting on a lower gas chain, e.g. a BSC user never has to pay the gas fees of Ethereum main net. The higher gas chain users on the other hand barely notice the impact of e.g. the additional cost of a transaction on Polygon when paying for gas on Ethereum.

This enables maximum user experience with the least amount of delay involved, so that all chains are as close to the correct global state as possible.<br>

<figure><img src="/files/CLi3t0suwEySmhgiHVh8" alt=""><figcaption></figcaption></figure>


---

# 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://scalex.gitbook.io/scalex/token/omnichain-reflections.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.