# $GENESIS Token

## $GENESIS Token

## Our Token

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

$GENESIS serves as the fundamental token that drives the Genesis Protocol ecosystem.

$GENESIS serves as the fundamental token that drives the Genesis Protocol ecosystem.

As our governance and reward token, $GENESIS is distributed through token emissions to lenders and stakers across multiple blockchain networks. It is important to note that $GENESIS does not function as an investment vehicle nor does it represent ownership. Instead, it operates within a free market, inherently carrying volatility and associated risks. At launch and in the future, the token offers a diverse range of utilities, including staking, lending, accessing our decentralized autonomous organization (DAO), and facilitating payments within our ecosystem. To participate in lending and voting, lenders are required to acquire and stake a minimum quantity of $GENESIS.

Moreover, $GENESIS holds the capability to be used for minting our unique non-fungible tokens (NFTs). We are excited to unveil more thrilling use cases as we introduce additional features in subsequent phases following the launch of our main product. Stay connected for the latest updates and developments!

### Tokenomics

The tokenomics for $GENESIS are simple. **Each buy and sell gets taxed 4%.**\
\
2% of the tax goes toward strengthening GENESIS’s  LP.\
1% of the tax goes toward our Marketing and Operations.\
1% of the tax goes toward our **stakers in the form of Rewards.**\
\
$GENESIS token sustains the project, governing lenders and stakers with various utilities.


---

# 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://genesis-protocol.gitbook.io/genesis-protocol/genesis-ecosystem/usdgenesis-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.