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

# Intro

Crypto yield is entering a new phase.

For years, much of decentralized finance was driven by short-term incentives, speculative liquidity programs, and reward models that depended heavily on token emissions. High APYs attracted attention, but many of those yields were difficult to sustain because they were not always connected to durable economic activity.

As the market matures, the next generation of crypto yield is moving toward a different foundation: **real-world assets, stablecoins, tokenized treasuries, private credit, and on-chain financial infrastructure that connects blockchain markets with real economic activity.**

Frost Yield is built for this shift.

Frost Yield is a risk-aware RWA and stablecoin yield protocol designed to help users access real-world yield strategies through a simple and transparent framework. Instead of asking users to manually compare dozens of vaults, protocols, APYs, liquidity conditions, lockups, counterparty risks, and yield sources, Frost Yield organizes opportunities through a clear system called **Yield Temperature**.

The Yield Temperature system categorizes supported strategies based on risk, liquidity, yield source quality, counterparty exposure, smart contract considerations, and market conditions.

This allows users to understand yield through a more practical lens:

**Cold Yield** represents more conservative, lower-volatility strategies.\
**Cool Yield** represents balanced strategies with moderate return potential.\
**Warm Yield** represents higher-yield strategies with increased risk.\
**Hot Yield** represents aggressive opportunities that may offer higher returns but require greater caution.

At the center of Frost Yield is a simple principle:

> **Yield should not be judged by APY alone.**

A higher return does not automatically mean a better opportunity. In many cases, the highest advertised APY can carry hidden risks around liquidity, sustainability, counterparty exposure, smart contract design, or market volatility.

Frost Yield is designed to make those risks easier to understand.

The protocol does not aim to eliminate risk. No yield system can do that. Instead, Frost Yield aims to help users evaluate the quality of yield itself by combining risk-scored strategy routing, transparent categorization, adaptive vault design, and protective mechanisms such as **Freeze Mode**.

When market conditions change, liquidity tightens, or a strategy becomes less attractive from a risk-adjusted perspective, Frost Yield is designed to help users stay disciplined instead of blindly chasing the highest available return.

This is the meaning behind the Frost Yield brand:

> **Real-world yield, routed by risk.**

The future of crypto yield will not only belong to the protocols offering the highest number on a screen.

It will belong to the protocols that make yield more understandable, more transparent, and more risk-aware.

Frost Yield is being built for that future.


---

# 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/intro.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.
