# Risks FIVA is a yield tokenization protocol on the TON ecosystem that allows users to split yield-bearing assets into Principal Tokens (PT) and Yield Tokens (YT). While this creates powerful new financial instruments and opportunities, it also introduces various risks that participants should understand before interacting with the protocol. This section outlines the risks associated with participating in the FIVA protocol, covering both general risks that affect all participants and specific risks relevant to different token holders (PT, YT, and LP). While FIVA implements robust risk management strategies across all identified risk vectors, participation in any DeFi protocol involves inherent risks. We encourage users to: 1. Start with smaller positions to understand the system before committing significant capital 2. Diversify exposure across different assets and token types 3. Properly assess their risk tolerance, especially for the more volatile YT positions 4. Consider their investment time horizon, particularly relative to maturity dates 5. Stay informed through FIVA's educational resources and community channels FIVA is committed to transparency regarding protocol risks and continuously works to enhance risk mitigation measures. We welcome community feedback and regularly update our risk models and mitigation strategies as the protocol and TON ecosystem evolve. For any questions or concerns about risks associated with FIVA, please reach out through our [Telegram community](https://t.me/fiva_community). --- # 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.thefiva.com/security/risks.md?ask= ``` 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.