> For the complete documentation index, see [llms.txt](https://evorium.gitbook.io/evorium-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://evorium.gitbook.io/evorium-docs/evo-economy/total-supply.md). # Total Supply ## Total Supply The total supply of EVO is fixed at **150,000,000 EVO**. This supply represents the full amount of EVO within the Evorium blockchain economy. As the native coin of the network, EVO is designed to support gas fees, validator participation, smart contract execution, ecosystem activity, and future governance utility. A clear total supply gives the Evorium ecosystem a defined economic foundation from the beginning. ### Fixed Native Supply EVO is not only an asset for transfers. It is the native coin that powers the Evorium Layer 1 blockchain. By setting the total supply at **150 million EVO**, the network has a clear supply structure that can be understood by users, developers, validators, and ecosystem participants. This matters because a blockchain economy needs transparency. Users should understand the native asset.\ Validators should understand the coin that supports network participation.\ Developers should understand the asset used for gas and contract execution.\ The ecosystem should understand the foundation behind its economy. ### Why Total Supply Matters Total supply is one of the most important parts of a blockchain’s economic design. It defines the maximum native coin structure of the network and helps create a clearer reference point for the ecosystem. For Evorium, the EVO supply supports the network’s core functions: * Gas fees for transactions * Smart contract execution * Validator staking and participation * Network incentives * Ecosystem activity * Future governance participation Every blockchain needs a native asset that connects network usage with economic participation. In Evorium, that asset is EVO. ### Designed for Network Utility The value of EVO inside the Evorium ecosystem is connected to its utility. EVO is used when users send transactions, developers deploy smart contracts, validators participate in securing the network, and applications operate on-chain. This gives EVO a practical role inside the network. It is not designed only to exist as a circulating asset. It is designed to support real blockchain activity across the Evorium ecosystem. ### Supply and Ecosystem Trust A transparent supply model helps strengthen ecosystem trust. When users know the total supply, they can better understand the structure of the native coin. When developers and validators understand the supply, they can evaluate how EVO connects to network usage and participation. For Evorium, transparency around EVO is part of the broader goal of building a blockchain economy that is easier to understand and easier to verify. ### The Foundation of EVO Economy The **150,000,000 EVO** total supply forms the base of the Evorium economy. From this foundation, EVO supports the most important activities of the network: Transactions.\ Gas fees.\ Smart contracts.\ Validators.\ Applications.\ Ecosystem participation. EVO is the native asset that connects these parts into one blockchain economy. It gives Evorium a clear economic layer for a Layer 1 network built around usability, security, and real Web3 utility. --- # 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://evorium.gitbook.io/evorium-docs/evo-economy/total-supply.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.