# Cross Chain

Our cross-chain infrastructure architecture adopts a hub-and-spoke model with Ethereum as the main chain and other chains serving as side chains. All message passing is aggregated on the main chain, which then performs computations and distributes the results to the respective side chains. This approach ensures data consistency between the chains and delegates all computational processes to the more secure Ethereum network.

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

Initially, we will follow Pendle's footsteps and deploy on Ethereum and Arbitrum. To address the high cost of participating in PENDLE votes, we have optimized the voting functionality of EQB and deployed it on multiple chains. This way, if users do not want to accept the high costs associated with the mainnet, they can choose to vote on Arbitrum.

Moreover, to ensure the unity of the token economy, we have implemented a deflation mechanism that synchronizes across all chains.

All the cross-chain features are built on top of Layerzero.

#### Consolidated Reporting Fee Sharing

Protocol fees will be generated across multiple chains, but we believe that a multi-chain ecosystem should not operate independently. Instead, it should function as a unified entity with shared token mechanisms and fees. This approach allows users to freely choose the chain they prefer to use. Unlike deploying on individual chains separately, where fee calculations may differ, we employ a consolidated reporting method to calculate the fees generated by each chain.&#x20;

Then, based on the proportion of ePENDLE held on each chain, their respective fees are determined. After calculation, rewards are distributed to each chain. In cases where time discrepancies occur due to bridges, we will utilize reserve funds to facilitate the timely disbursement of rewards.

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


---

# 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://docs.equilibria.fi/mechanism/cross-chain.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.