> For the complete documentation index, see [llms.txt](https://ohm3.gitbook.io/ohm3/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ohm3.gitbook.io/ohm3/tokenomics/key-functions-of-ohm3-tokens.md). # Key Functions of OHM3 Tokens **Rewards** OHM3 tokens are distributed as rewards to contributors who support the development, maintenance, and security of the OHM3 Energy Network. This includes energy producers, storage providers, and users who participate in staking. **Transaction Fees** OHM3 tokens are used to pay transaction fees within the network, such as fees for peer-to-peer energy trading and accessing smart grid management tools. **Payments for Services** OHM3 tokens can be used to pay for services provided by the network, including external entity payments for using the energy data and other related services. **Ecosystem Participation** OHM3 tokens can be used to participate in partnering projects within the ecosystem, facilitating collaboration and integration across various initiatives and platforms. **Governance** OHM3 token holders have voting rights on key decisions regarding network upgrades, development priorities, and other governance matters, ensuring that the network evolves according to the community’s needs and interests. --- # 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://ohm3.gitbook.io/ohm3/tokenomics/key-functions-of-ohm3-tokens.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.