> For the complete documentation index, see [llms.txt](https://docs.evedex.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.evedex.com/tokenomics/tokenomics-roadmap.md). # Tokenomics Roadmap The implementation of EVEDEX's tokenomics is divided into several stages, involving a gradual decentralization of the governance model and the progressive transfer of all ecosystem elements to community control. {% stepper %} {% step %} ### Stage I: Pre-MVP During Stage I (Pre-MVP), the project team plans to release several series of collectible badges, which will be available for minting by early protocol users. These badges can also be distributed among the most active and loyal community members for various activities and interactions with the community. #### Key Changes: * The reward program starts by allowing users to earn reward points for various activities, such as collecting unique badges for contests and other community initiatives. * Users may be unaware of the future token releases tied to their activities, creating an additional element of surprise and engagement. * This stage continues until the mainnet (MVP) launch and can last several months. The audience does not interact directly with the points and may not even know that their actions influence the number of points earned, engaging with the protocol primarily through Achievement Badges and various quests. **Project Governance**: During this stage, protocol governance is fully centralized and managed by the project team. {% endstep %} {% step %} ### Stage II: Testnet Launch The launch of the testnet version of the protocol to limited number of users. At this stage users will engage with the protocol in test mode to check the protocol features. {% endstep %} {% step %} ### Stage III: Mainnet Launch Stage III (MVP) begins with the launch of the mainnet version of the protocol. Following the start of this stage and the launch of the MVP, several new activities will be added to the rewards program to motivate users to engage more with the protocol, thereby increasing the volume of collected fees. At this stage, the Governing Council is formed, initiating the further execution of decisions and managing the protocol's development. #### Key Changes: * The protocol generates real revenue through fees from trading operations and access to additional services. * A portion of the fees collected by the Protocol may be transferred to the DAO Treasury, where the accumulated funds can be used according to the Governing Council decisions, including adding the new Network Incentives or other bonuses directed to ecosystem users to foster protocol & community development. * Users gain access to a personal dashboard displaying all the achievement badges they have accumulated and any other badges they can or could have earned by performing activities in the protocol. * This stage continues for about six months after the mainnet launch. **Project Governance**: During the second stage, decisions regarding protocol development are made by the Governing Council, which includes team members as well as potential public partners, community members, and project advisors. {% endstep %} {% step %} ### Stage IV: $EVE Token Launch & Governance Decentralization Stage IV begins approximately 6-18 months after the MVP mainnet launch, along with the release of the protocol's final version. This stage marks the launch of the Governing DAO and the gradual transition to full decentralization. Upon the beginning of this stage and the platform token launch, achievement badge holders will have the opportunity to receive a share of 6% of the total supply allocated for distribution among early platform users (retroactive airdrop) of the platform’s utility token, $EVE. When calculating the $EVE share for each user, the user's achievement badges and all additional achievements earned through various activities in the rewards program will be considered. Users eligible for the $EVE token distribution will have an option to immediately stake these tokens in the DAO, obtaining an equivalent amount of $stEVE tokens and a bonus in $stEVE. The bonus amount will depend on the user's airdrop share and will also be staked. The Network Incentives pool is used to distribute tokens allocated as rewards. #### **DAO and Protocol Governance** * The DAO, which governs the protocol through $stEVE token holder voting, is established. * The DAO can propose and vote on General Proposals for protocol development and the Proposal Creation and Voting Guidelines. * Proposal submission for voting will be available to DAO participants with a certain voting power (holding a specified amount of own or delegated $stEVE, as determined by the DAO). * The initial required voting power to submit a general proposal is set at 0,1% of the $EVE supply (at least `100 000 $stEVE`). The DAO can adjust this threshold in the future. * To submit a Funding Proposal, the initial required voting power is set at 0,5% of the $EVE supply (at least `500 000 $stEVE`). The DAO can also adjust this threshold in the future. #### **Staking and $stEVE token** * The staking mechanism for $EVE is launched, where tokens can be temporarily locked in exchange for $stEVE tokens. * $stEVE is a non-transferable token that grants governance rights. * $stEVE can be converted back to $EVE through an unstaking process that takes one year. The process is linear, updated every second, and users can withdraw the unfrozen tokens at any time (e.g., if a user has 1 000 000 $stEVE and initiates unstaking for all tokens, they can withdraw 1,9 $EVE each minute). * During the unstaking period, users lose the right to governance participation. #### **Further Ecosystem Development** * To support a controlled transition to a fully decentralized governance model, the EVEDEX Governing Council will be formed, consisting of team members, project partners, advisors, and community members. * The Governing Council will be able to manage the DAO Treasury for the Protocol Development within the DAO Constitution, in line with the ecosystem's goals and values. * Decisions made by the Council will be considered approved by default and will be automatically executed after a mandatory waiting period (7 days). * $stEVE holders with the voting power to create a DAO proposal can veto a decision, sending it back for revision with a justified refusal. After that, the Council can initiate a transaction with modifications. * As the protocol evolves, the formation of the Governing Council will be decentralized. It will be handed over to the DAO for further governance by community members with the highest voting power. #### **Rewards Program Relaunch** * After the DAO launch, participants can decide to relaunch the rewards program and issue new achievement badges for various activities. * Rewards for the updated rewards program can be formed from the Treasury pool and from the Network Incentives pool. {% endstep %} {% step %} ### Stage V: Further Ecosystem Development Subsequent decisions regarding the further development of the protocol will be transitioned under the governance of the DAO. An unlocking schedule is provided to mitigate the potential impact of token unlocks on the ecosystem and to ensure predictable growth of the circulating supply and controlled inflation. #### **Emission Control Mechanics** Several mechanisms to reduce volatility and further stabilize the price of the $EVE token are expected, such as token buybacks from the open market using a portion of the collected fees, burning a part of the collected fees, and forming a special reserve fund for price stabilization. {% endstep %} {% endstepper %} --- # 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.evedex.com/tokenomics/tokenomics-roadmap.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.