> For the complete documentation index, see [llms.txt](https://docs.tezos-homebase.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.tezos-homebase.io/why-create-a-dao/tokens.md). # Tokens To create a DAO on Homebase, your community needs to have a token. Tokens give members voting rights. DAOs typically have two types of membership tied to tokens: token-based memberships, where members govern a decentralized protocol together and can purchase tokens through liquidity pools or decentralized exchanges; and shares-based memberships, where a DAO is pooling financial resources to fund development, charity, or investments.\ \ Governance tokens can be 1:1, one membership one vote, or they can be allocated according to reputation, where community members earn tokens through contributing to DAO, and their voting power is proportional to their investment of time, money, labor, or other kinds of resources.\ \ **Please note that on Tezos you cannot use an NFT token as your voting token.** --- # 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://docs.tezos-homebase.io/why-create-a-dao/tokens.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.