# Staking

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

Staking is the primary way users earn yield on iTRY. When users deposit iTRY into the staking contract, they receive wiTRY, a yield-bearing token representing their proportional claim on the staking pool. The protocol distributes iTRY staking rewards into the staking pool, increasing the value of wiTRY over time. The staking pool implements the ERC-4626 Token Vault standard, ensuring it remains composable across DeFi.

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

1. Users stake iTRY in exchange for wiTRY.
2. The protocol distributes iTRY staking rewards into the staking pool.
3. wiTRY appreciates relative to iTRY as the pool grows.

When users unstake, they burn wiTRY and withdraw their principal plus their pro rata share of accrued iTRY rewards.

There are no minimum deposits or lock-ups, however, unstaking is subject to a [cooldown period](#unstake-cooldown).

{% hint style="info" %}
Select institutional users, like exchanges, are eligible for direct distribution of iTRY. For more information, see [Broken mention](broken://pages/TaKtwaraG3pSzsUOOV1A)
{% endhint %}

## Yield source

Staking rewards are derived from the underlying money market funds that ultimately back iTRY. As underlying money-market funds accrue interest, the protocol mints and distributes a proportional amount of staking rewards to the staking contract.

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

{% hint style="info" %}
Staking rewards ultimately depend on the performance of underlying money market funds. Yield can fluctuate.
{% endhint %}

## Yield schedule

The protocol distributes staking rewards on a scheduled cycle. At the end of each cycle, it calculates the difference between the underlying NAV at the start and end of the cycle to determine TRY-denominated yield. That NAV delta defines the amount of iTRY that will be minted as staking rewards for the cycle.

{% hint style="info" %}
At launch, this process is expected to operate on a weekly cadence. The schedule may change as the protocol evolves and operational requirements mature.
{% endhint %}

## Reward vesting

iTRY deposited into the staking contract vests linearly over a defined period. This ensures rewards accrue fairly based on how long a user remains staked.

Reward vesting prevents short-term opportunistic behavior, such as staking immediately before a reward deposit and exiting right after, and reduces abrupt price movements in wiTRY that could otherwise create predictable arbitrage windows.

## Unstake cooldown

Unstaking is subject to a 3-day cooldown period, during which the portion of wiTRY being unstaked stops earning staking rewards.

Behind the scenes, when users initiate an unstake, wiTRY is immediately burned and their principal and pro-rata rewards are sent to the iTRYSilo smart contract. When the cooldown period has concluded, users can withdraw their iTRY from the silo smart contract.

{% hint style="info" %}
Cooldown duration may change as the protocol evolves and operational requirements mature. The cooldown is configurable to a maximum of 90 days.
{% endhint %}

{% hint style="warning" %}
Unstaking additional iTRY while a cooldown is in progress will restart the cooldown. If a cooldown is active, users cannot withdraw iTRY balances that have previously completed cooldown.
{% endhint %}

If immediate liquidity is needed, users may be able to swap wiTRY or iTRY on secondary markets. Secondary markets are operated by third-parties; availability and slippage are not guaranteed.

## Crosschain Staking

The staking contract is deployed on Ethereum, which serves as the canonical layer for staking logic and accounting. When users stake, unstake, or withdraw from MegaETH, the system performs the required cross-chain operations to settle transactions on Ethereum. Cross chain operations are implemented using LayerZero's [OVault](https://docs.layerzero.network/v2/developers/evm/ovault/overview), which allows users to perform transactions on MegeETH without needing to manually bridge tokens first.

* **Stake:** When users stake iTRY on MegaETH, iTRY is bridged to Ethereum and staked. wiTRY is then bridged back to MegaETH.
* **Initiate Unstake:** When users initiate an unstake on MegaETH, wiTRY is bridged to Ethereum, where the cooldown period is started.
* **Withdraw:** When users withdraw iTRY on MegaETH, iTRY is claimed on Ethereum and bridged back to MegaETH.

{% hint style="info" %}
When performing staking-related transactions on MegaETH, please be aware that transactions can take some time.
{% endhint %}

## Examples

### Staking iTRY

1. Alice and Bob each stake 100 iTRY.
2. The contract issues 100 wiTRY to each, creating a 200-iTRY pool.
3. Each user holds a 50% share.
4. The protocol later deposits 100 iTRY into the pool, increasing it to 300 iTRY.
5. Alice and Bob now have a claim on 150 iTRY in the staking pool.

### Unstaking iTRY

1. Alice holds 100 wiTRY, representing a 50% share of a 300-iTRY pool.
2. Alice initiates an unstake.
3. A three-day cooldown begins.
4. After the cooldown completes, Alice withdraws 150 iTRY: her original 100 iTRY plus 50 iTRY in yield.

## Security and execution

Reward distribution is executed through a MultiSig wallet. Newly minted iTRY is first delivered into custody before distribution, ensuring secure handling of supply expansion. Yield is then deposited into the staking contract.


---

# 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.brix.money/itry/staking.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.
