> For the complete documentation index, see [llms.txt](https://coreszn.gitbook.io/coreszn-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://coreszn.gitbook.io/coreszn-docs/roadmap.md). # Roadmap CORESZN's phased path from community building to ecosystem utility. ## CORESZN roadmap CORESZN develops in phases. Each stage builds on the last. The focus is steady progress, clear communication, and practical utility across Core. ### Phase 1: Community building **Building the foundation.** CORESZN establishes its identity and grows an engaged community on X and Telegram. The project communicates its vision and encourages genuine participation within the Core ecosystem. ### Phase 2: Tokenomics and project structure **Establishing transparency.** CORESZN finalizes and publishes its tokenomics. This includes total supply, allocation, liquidity, vesting, and community rewards. This phase defines how tokens are allocated and distributed. It gives the community essential project information. ### Phase 3: CORESZN launch **Bringing CORESZN to market.** CORESZN prepares for its official token launch. The project publishes essential information on its website and GitBook. It also establishes its presence on Core Chain. This phase lays the foundation for token-based ecosystem activity. ### Phase 4: Utility and ecosystem growth **Strengthening participation through utility.** CORESZN introduces farming and staking rewards. These rewards incentivize participation and encourage liquidity provision across the ecosystem. The focus is market liquidity and rewards for eligible participants. ### The road ahead CORESZN begins with community, establishes a clear token structure, and grows through practical utility and ecosystem participation. Each phase supports the broader vision of bringing retail participation into the evolving Bitcoin economy. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://coreszn.gitbook.io/coreszn-docs/roadmap.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.