# Introduction to $EARNS

<figure><img src="/files/Dr76OU5VqeKjezKTXTmS" alt=""><figcaption></figcaption></figure>

$EARNS is a tokenized gaming experience point, used to **level up your gaming, increase earnings, enable more monetization options, and unlock new abilities** within the Earnscape ecosystem.\
\
`“Progress is impossible without change, and those who cannot change their minds cannot change anything” - George Bernard Shaw`

The $EARNS token represents a tradable "experience point" earned by playing games and completing various other tasks. The ecosystem the token powers merges Web2 and Web3 to supercharge gamers' experience playing while also increasing the metrics and viability of the games they play. &#x20;

$EARNS is a **utility token** which closely resembles in-game experience points, and carry the benefits you expect from such an asset:

* Gamers earn $EARNS as they play games, with the amount of tokens earned determined by how long they play, what game they play, and what ecosystem tasks they complete.
* Gamers use their $EARNS to unlock perks by staking their tokens into a smart contract while designating which perk they wish to unlock in the process.
* Perks unlocked by staking $EARNS enable new monetization pathways for gamers who have them, many of which come from outside the Earnscape ecosystem.
* Staking $EARNS increases your player level, conferring greater exposure to the user which further increases their ability to monetize their gameplay sessions.
* Actions like unstaking $EARNS return a portion of the unstaked tokens back to the community reward pool, ensuring value remains with the users.

In this litepaper, we explore $EARNS' ecosystem objectives, utility, token economy, and targeted user personas. We explore real use cases, partnerships, and possibilities which demonstrate $EARNS' progress towards becoming:

`“The experience points of Web3 gaming”`


---

# 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://earnscape.gitbook.io/earns-litepaper/introduction/introduction-to-usdearns.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.