# Token Distribution ![](/files/SXebKWdhlBFvwpawpnYZ) The token distribution will be divided into 5 parties: The community, app chain validators, the DAO, the investors and the DeBio Network team. Each owning a lesser percentage than the last. Both community and app chain validators will receive a total of 50% of the pie, while the team behind the project will only receive 12.5%. There are 4 rounds for investments in the DeBio project with a total sum of 17.5%. As of today, the DeBio Network team has finished two investment rounds giving away 7.5% of the stake to both angel and seed investors. ### **Mainnet Coin (stable coin, etc)** The Mainnet coin will be backed by a stable coin. We decided to use a stable coin because the Mainnet coin is intended to be used for transactional purposes, or fees for work being done by the corresponding labs. We are intending to use USDT, USDC, and USDT.e as our stable coin. Governance Token ($GBIO)\ \ Governance tokens are intentionally made for the labs. Because The DeBio Network is essentially a decentralized organization, the labs would need a token to be used for voting in the DAOGenics marketplace. The Governance Token can also serve as a method for lab onboarding. ### **Validator & Transaction Rewards ($DBIO)** The Validator Token is used to incentivize the node owners to validate transactions and protect the dApp from unauthorized users. The intended incentives provided for validators are LP rewards and Governance tokens. --- # Agent Instructions: 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: ``` GET https://docs.debio.network/tokenomics/token-distribution.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.