> For the complete documentation index, see [llms.txt](https://docs.brix.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.brix.money/technical/crosschain.md).

# Crosschain

iTRY and wiTRY are designed to operate seamlessly across multiple blockchains while maintaining a single, unified supply. To enable this, the protocol leverages LayerZero’s messaging infrastructure, which provides a reliable system for transferring tokens and communicating across chains without introducing security risks associated with traditional bridges.

## Hub-and-spoke design

Ethereum serves as the canonical hub chain. On Ethereum, iTRY exists as a standard ERC-20 token and represents the authoritative supply used for accounting, minting, and redemption. All core logic, including supply management and backing, originates on Ethereum.

On MegaETH, iTRY is deployed using LayerZero’s OFT (Omnichain Fungible Token) model. OFTs behave exactly like standard ERC-20 tokens but include LayerZero’s cross-chain transport functionality. This allows iTRY and wiTRY to move between spoke chains without fragmenting liquidity. The MegaETH deployment uses distinct token contracts with their own balances, deployed on a unified address and logically linked to the canonical supply on Ethereum through LayerZero’s messaging layer.

When iTRY is bridged from Ethereum to MegaETH, the tokens are locked on Ethereum and an equivalent amount is minted on the destination chain. When iTRY is bridged from a Layer 2 back to Ethereum, the tokens on MegaETH are burned and the corresponding amount is unlocked on Ethereum.

This architecture allows iTRY to operate seamlessly across multiple networks while maintaining a single source of truth for supply, accounting, and risk management.


---

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

```
GET https://docs.brix.money/technical/crosschain.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.