# EDV Token

The EDV token is the native digital cryptographically-secured utility token of edverse.

<figure><img src="https://1353182722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwkshVX8uRWFRmPK31clk%2Fuploads%2Fq1F4mNcQafWVH3VtzlxS%2Fimage.png?alt=media&#x26;token=238eff0a-6493-45bd-809f-b68998b1c7b4" alt="" width="181"><figcaption><p>EDV Token</p></figcaption></figure>

As the native platform currency, EDV plays the role of the settlement medium, staking (for privileges) and utility token within the entire edverse ecosystem. This will be supported by an in-game currency to facilitate operational transactions amongst various stakeholders.

**EDV token has a total supply of 1 Billion units.**

The following sections cover how to earn and utilize tokens, the overall allocation and drivers of token supply and demand.

**Balancing EDV supply and demand**

**EDV supply:** The overall supply of EDV is limited. The factors affecting the token supply in circulation are:

1. Sale from existing token holders - investors & stakeholders
2. Balancing act by the platform to increase or decrease supply if required from allocation pool

**EDV demand:** The demand for token is generated by the following factors:

1. Investors (retail and institutional) purchasing token (HODLers).
2. Educators and Promoters purchasing EDV from the market to buy advertising or subscription services from edverse
3. Learners purchasing token from the market to buy courses from other Educator or content providers
4. Institutions that pay edverse for its services using EDV (to get a discounted price).
5. Platform will purchase token from the open market. This will be a percentage of commissions earned by the platform and will go towards reward pool and token burn.


---

# 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://edverse.gitbook.io/edverse-whitepaper/overview/edv-token.md?ask=<question>
```

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.