> For the complete documentation index, see [llms.txt](https://docs.vapordex.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vapordex.io/vapordex/vape-token/genesis/role-of-various-community-driven-valuations.md). # Role of Various Community-Driven Valuations Our community-driven valuation design is a source of immense pride for us and a token launch model that we believe others will use or take inspiration from in the future. By designing our initial emission event in this way, we’ve put the future of VAPE fully in the hands of our capable community. Here’s a quick rundown on why each of these community-driven values is important. * Cost to Acquire creates and quantifies an organic profitability floor * Initial Valuation uses Cost to Acquire plus a subjective/aspirational markup value to establish a new valuation * Market Valuation requires individuals to pair their VAPE with the real value of VAPE, ensuring that someone isn’t likely to create the secondary market at a 1000x the token’s cost to acquire * Cost to Acquire also ensures that the Market Valuation isn’t less than the initial genesis valuation, unless the community is willing to lose value on the secondary market --- # 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://docs.vapordex.io/vapordex/vape-token/genesis/role-of-various-community-driven-valuations.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.