> For the complete documentation index, see [llms.txt](https://docs.rujira.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.rujira.network/core-products/ruji-index/ytcy.md). # yTCY {% hint style="info" %} yTCY live via . {% endhint %} Similar to yRUNE, Yield Bearing TCY (yTCY) is an **auto-rebalancing basket of TCY and RUNE**. ### How are the weights between TCY and RUNE determined? The weights of RUNE and TCY are set to maximize returns captured from: * **TCY Yield (THORChain System income):** TCY is a unique asset, as it captures 10% of THORChain's system income. Our contract is whitelisted to receive these staking rewards, enabling yTCY to fully benefit from the TCY component of the index. * **RUNE / TCY mean reversion:** Due to price fluctuations, particularly for TCY caused by shallow liquidity, yRUNE captures volatility by automatically rebalancing towards the "cheaper" asset during price swings. This is achieved by keeping yTCY close to a predefined target ratio between RUNE and TCY. * **Liquidity:** Safeguards are implemented in the contract to ensure that rebalancing minimizes price impact and slippage. Taking these three factors into account, initial weights are set to **80% TCY : 20% RUNE**. The contracts will initiate rebalancing if the weight is at least 1 percentage point off its target weight. Current & target weights can be seen on the RUJIRA UI at . *** ### Rebalancing Rebalancing occurs automatically with each contract crank (at least once per minute). If insufficient liquidity prevents executing a rebalance, the contract will attempt again later to minimize price impact and slippage. ### Risks Key risks for yTCY include: * Asset risk of RUNE and TCY. * Smart contract risk of RUJI Nav Index contract (audited). * Rebalancing/Trading risk: The automated rebalancing algorithm aims to maximise returns from trading, but those are not guaranteed and may depend on other factors such as market conditions, liquidity & more. Safeguards are in place to minimize this risk.
--- # 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://docs.rujira.network/core-products/ruji-index/ytcy.md?ask=&goal= ``` `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.