> For the complete documentation index, see [llms.txt](https://frost-yield.gitbook.io/frost-yield-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://frost-yield.gitbook.io/frost-yield-docs/the-problem.md). # The Problem Crypto users have more access to yield than ever before, but access alone does not solve the real problem. The real problem is understanding what kind of yield they are actually taking on. Across DeFi, stablecoin markets, and emerging RWA products, users are often shown yield as a single headline number. A vault may advertise 5%, 12%, 20%, or higher, but that number rarely tells the full story. A higher APY can look more attractive at first glance, but it may come with hidden tradeoffs: * lower liquidity * longer withdrawal windows * greater smart contract exposure * higher counterparty risk * weaker yield sustainability * more complex strategy mechanics * bridge or chain-specific risks * dependence on temporary incentives * reduced transparency around how returns are generated This creates a major issue for retail users. Most users are not professional analysts. They do not have the time, tools, or experience to deeply evaluate every strategy, protocol, vault, custody structure, liquidity profile, or counterparty relationship behind a yield product. As a result, many users default to the most visible metric: > **APY.** That is dangerous. APY is useful, but it is incomplete. It shows the potential return, not the quality of the opportunity. It does not explain whether the yield is coming from real economic activity, temporary emissions, lending demand, treasury exposure, private credit, leverage, liquidity incentives, or speculative market behavior. Two opportunities can show the same APY while being completely different under the surface. A 7% yield from a conservative treasury-based strategy is not the same as a 7% yield from a thinly traded DeFi vault.\ A 12% stablecoin lending opportunity is not the same as a 12% private credit strategy.\ A 20% promotional APY is not the same as a 20% sustainable yield source. Yet to many users, these opportunities appear side by side as if they are directly comparable. This creates a distorted market where users are encouraged to chase the biggest number rather than evaluate the strongest risk-adjusted opportunity. Frost Yield is designed around the belief that this needs to change. Users need a clearer way to answer basic questions before entering a yield strategy: **Where does the yield come from?**\ **How liquid is the strategy?**\ **What risks are involved?**\ **Is the APY sustainable?**\ **What happens if market conditions change?**\ **Is the strategy conservative, balanced, aggressive, or high-risk?** Without a clear framework, users are left to make decisions in a noisy environment filled with dashboards, protocols, marketing claims, and yield tables that often emphasize return while minimizing risk. This problem becomes even more important as real-world assets move on-chain. RWA yield may sound simple, but it can involve complex structures such as tokenized treasuries, credit exposure, collateralized loans, institutional counterparties, redemption mechanics, custody arrangements, and off-chain legal frameworks. For retail users, this complexity can be difficult to interpret. The result is a gap between access and understanding. Users may be able to access more yield opportunities than ever before, but they still need a better way to compare them, evaluate them, and understand the risks behind them. Frost Yield exists to close that gap. The goal is not to make yield risk-free. The goal is to make yield more understandable. --- # 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://frost-yield.gitbook.io/frost-yield-docs/the-problem.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.