> For the complete documentation index, see [llms.txt](https://elevex.gitbook.io/elevex-whitepaper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://elevex.gitbook.io/elevex-whitepaper/elvx-foundation/elvx-token.md). # ELVX Token ### **The Core of the Elevex Ecosystem** The **$ELVX token** is the cornerstone of the Elevex ecosystem, designed to fuel its functionality and governance. More than just a utility token, it integrates seamlessly into the platform’s operations, ensuring a dynamic and thriving ecosystem for investors, developers, and the broader Elevex community. As the backbone of Elevex’s business model, $ELVX enables a range of vital functionalities, driving both innovation and sustainability. Key Areas Powered by $ELVX: * **Governance**: Participate in decentralized decision-making through the Elevex DAO, shaping the future of the platform. * **Platform Access**: Unlock premium features, exclusive project listings, and secondary market tools. * **Transaction Fees**: Serve as the primary medium for paying platform fees, including trading, staking, and liquidity activities. * **Loyalty & Rewards**: Gain benefits such as discounts, priority access, and special incentives through token staking. * **Value Accrual**: Capture the growth and success of the Elevex ecosystem via token-based utility and demand. * **Ecosystem Backbone**: Support tokenization, liquidity pools, and marketplace operations as the foundational asset of Elevex. In the following sections, we’ll explore how $ELVX integrates into Elevex’s **governance model**, **staking mechanisms**, and **ecosystem incentives**, demonstrating its critical role in advancing real estate tokenization and decentralized finance. --- # 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://elevex.gitbook.io/elevex-whitepaper/elvx-foundation/elvx-token.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.