> For the complete documentation index, see [llms.txt](https://docs.nftx.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.nftx.io/v1.0/ecosystem/token-distribution.md). # Token Distribution ## Token Rights & Distribution The NFTX smart contract uses an upgradeable proxy which is controlled by the NFTX Dao (on Aragon). This means that NFTX token holders have the power to change the NFTX smart contract if we reach consensus. Right now all changes require 80% of participating (i.e. voting) tokens to support a proposal in order for it to pass, with the voting period lasting for 24 hours. In the future we will propose decreasing the support threshold and increasing the duration (e.g. 65% support over 5 days), but for now the shorter duration allows our platform to make updates faster, and the 80% threshold helps protect against governance attacks. The NFTX token supply is 650,000, and the distribution is as follows: * 10% vested over 5 years for founder * 30% distributed for NFT contributions (community raise) * 30% distributed for ETH contributions (community raise) * 10% earmarked for NFTX liquidity * 20% earmarked for farming ![NFTX Token Distribution](/files/-MQ4J7W9K9DDB9e9GMW-) Keeping popular funds liquid is important, so the community raise will be accepting ETH as well as NFTs (in the form of D1 fund tokens) in exchange for vested NFTX tokens. The idea is for the NFTX Dao to raise enough NFTs and ETH to bootstrap AMM pools with liquidity. Being an LP makes sense for our Dao because it improves the liquidity of funds (i.e. our product) while also earning yield for our treasury. --- # 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.nftx.io/v1.0/ecosystem/token-distribution.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.