> For the complete documentation index, see [llms.txt](https://guida-2.gitbook.io/guida-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guida-2.gitbook.io/guida-docs/reference/ecosystem.md). # Ecosystem Guida's long-term vision extends beyond a single app into an **ecosystem** where strategists, users, and the platform all benefit from good strategy being created and shared. This page outlines the direction. It's forward-looking — see the [Roadmap](/guida-docs/reference/roadmap.md) for sequencing. > This page describes intentions, not commitments. Details will be finalized and shared as these features approach release. Nothing here is an offer, a solicitation, or financial advice. ## The principle: reward real value Many crypto ecosystems reward activity for its own sake — trade more, earn more — which tends to produce noise rather than value. Guida's guiding principle is different: **reward genuine, verifiable value.** In practice, that means designing incentives around outcomes that are real and measurable — like the actual performance a strategy delivers — rather than vanity metrics like how many people clicked "copy" or how loud a strategy's marketing was. ## A marketplace for strategies The [strategy library](/guida-docs/features/strategy-library.md) is being built toward a full marketplace where: * **Creators** can publish strategies and be recognized for their skill. * **Users** can discover and copy strategies with proven, transparent track records. * **Rewards flow to creators based on real results** — the value their strategies actually generate for the people who use them. The emphasis on *verified performance* is deliberate. A healthy marketplace rewards strategists whose ideas genuinely work — not those best at manufacturing hype or gaming popularity. Getting this incentive design right is central to building a community worth trusting. ## Premium capabilities Beyond the marketplace, the ecosystem is expected to include premium capabilities for power users — more advanced tools and access for the most active strategists. The intent is to tie premium features to real costs and real value, so that what you pay for is genuine capability, not artificial scarcity. ## A note on any future token Guida's ecosystem may in time include a token to power these mechanisms. If and when it does, the guiding philosophy will be **utility grounded in real value** — tied to actual capabilities and verified performance — rather than speculation. Any specifics will be shared clearly and only when they're ready. We're deliberately building the product and community first. An ecosystem is only worth building once there's genuine usage and value for it to serve. *** **Related:** [Strategy Library](/guida-docs/features/strategy-library.md) · [Roadmap](/guida-docs/reference/roadmap.md) --- # 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, and the optional `goal` query parameter: ``` GET https://guida-2.gitbook.io/guida-docs/reference/ecosystem.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.