> 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/roadmap.md). # Roadmap The Frost Yield roadmap is designed to move the protocol from presale participation to platform launch, vault development, risk framework expansion, and long-term strategy routing. The roadmap is not only focused on releasing features. It is focused on building Frost Yield in a structured way, with each phase supporting the protocol’s core mission: > **Real-world yield, routed by risk.** Frost Yield’s development path is organized into several major stages. ### Phase 1: Foundation and Presale The first stage focuses on establishing the Frost Yield brand, token structure, presale system, and core protocol framework. Key objectives include: * finalizing the Frost Yield whitepaper * launching the official website * opening the $FROST presale * deploying presale dashboard infrastructure * implementing wallet connection * supporting approved payment methods * displaying current phase price and next phase price * showing purchased allocation and bonus allocation * building referral and campaign tracking * publishing core risk disclosures * beginning community growth and marketing campaigns This phase is designed to build early awareness, distribute $FROST to presale participants, and prepare the foundation for the full Frost Yield platform. ### Phase 2: Security, Token Launch, and Claim System The second stage focuses on launch preparation, token deployment, security review, and user claiming. Key objectives include: * finalizing $FROST token contracts * completing smart contract testing * conducting security reviews or audits where applicable * preparing the token generation event * launching the official claim portal * publishing official contract addresses * setting up initial liquidity * activating token claiming * confirming vesting or unlock schedules, if applicable * improving dashboard security messaging * warning users against phishing, fake contracts, and unofficial links This phase is designed to give users a secure and transparent path from presale participation to token launch. ### Phase 3: Frost Dashboard Expansion The third stage focuses on expanding the user dashboard beyond basic presale tracking. Key objectives include: * displaying user $FROST balances * showing claim status and vesting details * displaying referral rewards * adding vault education pages * introducing Yield Temperature visuals * showing Snowcap, Glacier, Aurora, and Blizzard vault previews * adding strategy-risk explanations * improving wallet-based user history * publishing platform updates and development progress This phase helps users understand how Frost Yield will operate after the presale and prepares them for vault participation. ### Phase 4: Vault Simulation and Risk Model Testing Before live vault routing is introduced, Frost Yield may launch vault simulation tools and risk model previews. Key objectives include: * publishing sample vault structures * displaying sample Yield Temperature classifications * testing strategy scoring models * showing example allocation breakdowns * comparing Cold, Cool, Warm, and Hot strategy profiles * gathering user feedback on vault design * refining risk category definitions * testing Freeze Mode logic in simulated environments This phase allows Frost Yield to educate users and refine the user experience before live strategy routing begins. ### Phase 5: Initial Vault Rollout The fifth stage focuses on launching the first Frost Vaults. Key objectives include: * launching selected vault categories * introducing Snowcap and Glacier as initial lower-risk vault options * adding additional vaults as infrastructure matures * displaying estimated APYs, liquidity terms, and risk categories * integrating approved RWA and stablecoin yield sources * publishing vault-specific disclosures * enabling user deposits where supported * monitoring vault performance * tracking liquidity and risk signals * preparing future vault expansion The initial vault rollout should prioritize clarity, safety, and operational control over aggressive expansion. ### Phase 6: Strategy Routing and Freeze Mode Activation Once initial vault infrastructure is operational, Frost Yield may begin expanding its strategy routing framework. Key objectives include: * activating strategy routing logic * monitoring supported yield sources * assigning active Yield Temperature ratings * adjusting vault allocations based on risk conditions * displaying strategy updates in the dashboard * enabling Freeze Mode warnings * pausing or reducing exposure to strategies when needed * publishing risk updates for users * improving data feeds and monitoring tools This phase brings Frost Yield closer to its full risk-aware yield routing model. ### Phase 7: Advanced Vault Expansion As the protocol matures, Frost Yield may expand into additional vault categories and supported strategies. Key objectives include: * expanding Aurora and Blizzard vault access where appropriate * adding new RWA and stablecoin yield categories * supporting more advanced strategy types * improving allocation controls * introducing additional user analytics * expanding strategy monitoring * adding more detailed risk reports * improving withdrawal and redemption transparency * refining vault performance reporting This phase should be approached carefully, especially for higher-risk strategies. ### Phase 8: Governance and Long-Term Protocol Development The final roadmap stage focuses on long-term protocol maturity, governance, and continued development. Key objectives include: * introducing governance participation for eligible $FROST holders * proposing vault parameter updates * allowing community feedback on new strategy categories * publishing regular strategy and risk reports * expanding platform integrations * improving compliance and risk review processes * developing additional utility for $FROST * strengthening protocol transparency * improving user education * continuing long-term ecosystem growth Governance should be introduced gradually and should not override critical security, legal, or emergency risk controls. ### Roadmap Flexibility The Frost Yield roadmap may evolve over time. Development timelines, feature releases, vault availability, integrations, and launch milestones may change based on technical requirements, security reviews, legal considerations, market conditions, user demand, and operational readiness. Frost Yield may adjust its roadmap to prioritize user safety, platform reliability, compliance, and sustainable growth. The roadmap is intended to provide direction, not a guarantee that every feature will launch on a fixed schedule. ### Roadmap Goal The goal of the Frost Yield roadmap is to build the protocol carefully and transparently. Frost Yield is not designed to rush into every available yield opportunity. It is designed to create a more structured way for users to understand and access RWA and stablecoin yield strategies. Each roadmap phase supports that larger mission: > **Make real-world yield easier to understand, easier to access, and easier to evaluate by 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: ``` GET https://frost-yield.gitbook.io/frost-yield-docs/roadmap.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.