> 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/usdfrost-token-utility.md). # $FROST Token Utility $FROST is the native token of the Frost Yield protocol. The purpose of $FROST is to support access, alignment, governance, and participation within the Frost Yield ecosystem. As the protocol grows, $FROST is designed to become the core utility layer connecting users, vaults, strategy access, protocol incentives, and long-term governance. $FROST is not designed to represent ownership of any underlying yield strategy, vault, treasury product, credit instrument, or real-world asset. Instead, it is designed as a utility token used within the Frost Yield platform. ### Core Utility $FROST may support several forms of protocol utility, including: * vault access * fee discounts * staking benefits * strategy tier eligibility * governance participation * reward boosts * referral incentives * ecosystem status levels The exact utility available to a user may depend on how much $FROST they hold, stake, or use within the platform. ### Vault Access Certain Frost Vaults may be available to all users, while higher-tier vaults may require $FROST participation. For example, more conservative vaults such as Snowcap may have broader access, while advanced vaults such as Aurora or Blizzard may require users to meet specific $FROST holding, staking, or eligibility thresholds. This creates a simple access model: **Basic access** allows users to interact with entry-level vaults.\ **Enhanced access** may unlock additional strategy options.\ **Premium access** may unlock higher-tier vaults, advanced analytics, or increased allocation limits. This structure allows $FROST to function as an access layer for the protocol without making yield participation dependent on unrealistic promises or guaranteed returns. ### Fee Discounts $FROST may be used to unlock reduced protocol fees. Users who hold or stake $FROST may qualify for lower fees on certain platform activities, such as vault participation, strategy routing, withdrawals, rebalancing, or other supported protocol functions. The purpose of this utility is to reward users who are more deeply aligned with the Frost Yield ecosystem. A possible fee-discount structure may include: | Tier | $FROST Requirement | Fee Benefit | | -------- | ---------------------- | --------------------- | | Frost | Entry level | Standard fees | | Snow | Moderate participation | Reduced fees | | Glacier | Higher participation | Greater fee reduction | | Aurora | Advanced participation | Premium fee reduction | | Blizzard | Highest participation | Maximum fee reduction | Specific thresholds and fee rates may be defined closer to launch based on protocol design, compliance review, and market conditions. ### Staking Benefits Users may be able to stake $FROST to unlock additional protocol benefits. Potential staking benefits may include: * reduced fees * increased allocation limits * access to advanced vaults * eligibility for strategy boosts * priority access to new vaults * enhanced referral rewards * governance participation Staking is intended to create long-term alignment between users and the protocol. However, staking $FROST does not guarantee profit, yield, or protection from loss. Any staking benefits should be understood as platform utility, not guaranteed investment returns. ### Strategy Tier Eligibility Some strategies may require additional user eligibility before access is granted. This may be especially important for strategies with higher complexity, lower liquidity, longer redemption windows, or elevated risk. $FROST may help determine which strategy tiers a user can access. For example: **Snowcap Access** may be open to all users.\ **Glacier Access** may require basic $FROST participation.\ **Aurora Access** may require higher $FROST participation.\ **Blizzard Access** may require advanced eligibility and clear risk acknowledgement. This gives Frost Yield a flexible way to organize access while keeping higher-risk strategies separated from basic user flows. ### Reward Boosts $FROST may be used to unlock reward boosts within the platform. These boosts may apply to platform points, referral rewards, loyalty programs, fee rebates, or other non-guaranteed protocol incentives. Reward boosts should not be understood as guaranteed yield or fixed returns. They are intended to support user engagement, long-term participation, and protocol growth. ### Referral Incentives $FROST may be used within Frost Yield’s referral system. Users who refer new participants may be eligible to receive $FROST-based rewards, bonus allocation, platform points, or other protocol-defined incentives. Referral incentives can help grow the Frost Yield user base while rewarding users who introduce others to the protocol. Any referral system should be clearly structured, transparent, and subject to abuse-prevention rules. ### Governance Participation As the Frost Yield protocol matures, $FROST may support governance participation. Governance may allow eligible $FROST holders or stakers to vote on selected protocol matters, such as: * supported strategy categories * vault parameters * risk framework updates * fee structures * new integrations * treasury usage * incentive programs * protocol upgrades Governance should be introduced carefully. Some decisions, especially those involving risk controls, legal compliance, security, or emergency actions, may require additional oversight or may not be fully delegated to token voting. ### Alignment With the Protocol $FROST is designed to align users with the long-term growth of Frost Yield. Users who participate more deeply in the protocol may gain access to additional tools, lower fees, stronger referral benefits, governance rights, or enhanced platform features. This creates a utility model where $FROST supports protocol access and participation rather than relying only on speculation. ### What $FROST Does Not Represent It is important to define what $FROST is not. $FROST does not represent: * ownership of Frost Yield as a company or legal entity * ownership of underlying vault assets * a claim on tokenized treasuries, private credit, or other RWAs * a guaranteed right to revenue * a guaranteed yield product * a promise of profit * insurance against losses * a risk-free financial instrument $FROST is intended to function as a utility token within the Frost Yield platform. Its value, use, and benefits may depend on adoption, demand, market conditions, protocol development, available features, and user participation. ### Why $FROST Matters Frost Yield is designed to make RWA and stablecoin yield easier to access, understand, and evaluate by risk. $FROST supports that mission by acting as the protocol’s utility layer. It can help organize access, reduce fees, unlock features, support referrals, enable governance, and align users with the long-term development of the platform. As Frost Yield grows, $FROST is intended to become the token that connects users to the broader Frost Yield experience. --- # 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/usdfrost-token-utility.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.