> 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/itry/overview.md).

# Overview

iTRY is an [ERC-20](https://ethereum.org/developers/docs/standards/tokens/erc-20/) Turkish Lira pegged stablecoin backed by a tokenized basket of highly liquid Turkish money market funds.

iTRYs price stability is maintained through arbitrage between its primary and secondary markets. The primary market allows eligible, whitelisted participants to mint and redeem iTRY at a fixed price. When secondary-market prices diverge, arbitrage activity closes the gap across trading venues.

Users may stake iTRY to receive wiTRY, a yield-accruing token that represents a proportional claim on the [ERC-4626](https://ethereum.org/developers/docs/standards/tokens/erc-4626/) staking pool. wiTRY increases in value over time as the protocol deposits iTRY rewards into the staking contract. These rewards are sourced from the yield generated by the underlying money market funds backing iTRY.

iTRY and wiTRY are available on Ethereum and MegaETH. MegaETH serves as the exclusive chain for DeFi, while Ethereum is used as the settlement layer. Cross-chain functionality is powered by LayerZero, allowing iTRY to move between supported chains without fragmenting liquidity.

{% hint style="info" %}
Staking is coming soon.
{% endhint %}


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.brix.money/itry/overview.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.