> 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-overview/entities-used.md).
# Entities Used
Contents
[#usdeve-evedex-token](#usdeve-evedex-token "mention")
[#usdsteve-staked-usdeve](#usdsteve-staked-usdeve "mention")
[#achievement-badges](#achievement-badges "mention")
## $EVE (EVEDEX Token)
* Utility token of the EVEDEX protocol;
* Used for transaction fee payments, discounts, and access to premium platform features;
* Fungible ERC-20 standard token;
* Fixed supply of 100 million tokens;
* Distributed among various ecosystem participants (team, investors, users, etc.) according to the tokenomics model;
* Can be staked in the protocol in exchange for non-transferable $stEVE tokens to get governance rights through the DAO
## $stEVE (Staked $EVE)
* Token received as a result of staking $EVE in the EVEDEX protocol
* Used for protocol governance through voting in the DAO. Voting weight is proportional to the user's $stEVE balance
* Non-transferable ERC-20 — standard token that cannot be directly transferred to another address;
* To convert $stEVE into liquid $EVE, the user must unstake it first, which takes a period set by the DAO. At protocol launch, the unstaking period is one year
* During the unstaking period, $stEVE tokens are converted to $EVE every second. The user loses the right to participate in governance for the amount of tokens being unstaked;
* Users can withdraw $stEVE from staking early, subject to penalties of up to 50% of the staked tokens. The penalty decreases linearly to zero as the unstaking period reduces. A DAO vote can change the penalty amount.
**Example**: A user initiates unstaking of `100 $stEVE`, withdrawing available tokens monthly, but decides to withdraw them early after six months `(180 days)`. In this case, the user will withdraw `100 / 365 * 30 = 8,2192 $EVE` monthly, totaling `8,2192 * 6 = 49,3151 $EVE` over six months. The remaining $stEVE after six months of unstaking, which the user will withdraw with a penalty of `50% * (365 - 180) / 365 = 25,34%`, amounts to `100 - 49,3151 = 50,6849 $stEVE`. As a result, the user will receive `49,3151 $EVE + 37,8493 $EVE = 87,1644 $EVE`.
## Achievement Badges
* Special non-fungible tokens issued by the EVEDEX project team during the protocol's early development stages
* Serves as additional incentives for the most active and loyal community members.
* Can be obtained by users through direct minting on the project website, completing special tasks, reaching certain activity levels, or as part of promotional campaigns and giveaways
* Various Achievement Badges issued by the protocol and acquired by users through the rewards program may have unique designs and characteristics that determine their rarity, value, and subsequent evaluation in reward points.
* During the Retrodrop, each Achievement Badge will be assigned a specific value in reward points. Some Badges can also be used as multipliers when calculating the share of $EVE due to each user.
## Reward Points
* Internal tracking unit for user activity metrics within the EVEDEX rewards program.
* Awarded for performing various actions that contribute to the growth and development of the protocol ecosystem, such as trading on the platform, attracting new users, providing liquidity, participating in new feature testing, as well as actions within various quests and activities in Reward Discovery
* It is not stored on the blockchain but in the rewards program's internal database. It may also be published and regularly updated in a centralized repository, for example, through publishing spreadsheets on the project's GitHub or any other publicly verifiable platform;
* Serves as the basis for calculating the amount of $EVE available for claiming after the TGE
---
# 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-overview/entities-used.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.