> For the complete documentation index, see [llms.txt](https://docs.unich.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unich.com/unich-network/competitive-context-and-closing-statement/development-roadmap.md). # Development Roadmap The roadmap is organized into three phases, not tied to specific years — each phase only transitions when the network health conditions of the current phase are met. **Phase 1: Building the Foundation** Three product pillars built simultaneously: * **User Path** — optimize the mining mechanism, Boost Multipliers, and Node upgrade activities. Goal: Users operate Nodes effectively without needing blockchain technical knowledge. * **Mastery Path** — an advanced financial and blockchain education program. Completing lessons earns Boost Multipliers from Knowledge Proof. Knowledge is a form of Node upgrade — not technical knowledge, but the capability of the Node's owner. * **Ambassador Path** — the roadmap to becoming an Anchor Node and building local community. What Users gain: stable Node mining; long-term Trust Circles through real Peer Meets; upgraded financial knowledge through Mastery Path; UN IDO participants have the option to convert to FC or receive the 120% refund. *** **Phase 2 — Network Expansion and FC Utility** When the network reaches sufficient stable Node density: Anchor Nodes expand into new regions; advertising and premium subscription revenue grows; FC use cases expand through internal transactions and premium features. What Users gain: FC has concrete use cases before TGE; Mining Rate accumulates over time (long-standing Nodes have an advantage over new ones); Anchor Nodes at level 3 with 100+ directly referred Nodes have the option to join Network Revenue Sharing — receiving a liquid USDT/bank transfer revenue stream in exchange for 40% Mining Rate; the Buy-back reserve accumulates steadily, ready to activate at TGE. *** **Phase 3 — Open Ecosystem and FC TGE** When three conditions are met: FC has real utility Users actively use, revenue has reached sufficient scale, and network density has reached a level where virtual machines cannot outperform real Nodes. Third-party API access opens; specialized sub-networks are developed (for example, a job-matching platform where a User's Node serves as a verified credential through Peer Meet history, and FC functions as the settlement currency); FC TGE proceeds on immutable commitments — no one on the team has the authority to shorten the process for market reasons or short-term pressure. **What Users gain:** Nodes become verifiable digital assets with history and provable value, usable across multiple sub-networks; FC has broad liquidity and utility; Users who joined from Phase 1 benefit from accumulated advantage (the longest-standing Nodes, the highest Mining Rates, the most stable FC). *** **Cross-Cutting Principles** * **First: No phase prioritizes one group of Users over another.** Every special benefit comes with a proportional contribution requirement. * **Second: FC is the backbone at every phase.** No phase abandons FC. Every new product, sub-network, or business feature must have a clearly defined role for FC within it. --- # 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://docs.unich.com/unich-network/competitive-context-and-closing-statement/development-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.