> For the complete documentation index, see [llms.txt](https://docs.hadeswap.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.hadeswap.com/whitepaper/usdhades-tokenomics/usdhades-emission-schedule-and-use-case.md).

# $HADES - Emission Schedule & Use case

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

Use cases of the $HADES token:

* Governance
* Delegation
* Auctions of Hades NFT
* Things we can't reveal yet or they'll be copied...
* 90% Protocol-Owned liquidity profit buy back (burned)

**Deep Dive: Auctions of Underworld NFT and other NFTs**

* Hadeswap will be holding daily auctions for the Underworld NFTs in $HADES only.
* All $HADES used for auctions will be burned in exchange for emitting the NFTs.
* MInimum 5 daily auctions taking place.
* **Standard auctions** that will have a duration of 24 hours and won't be extended if there is a price war happening at the last minute. Last valid bid wins the auction.

**Deep Dive: ABC & Underworld NFTs Staking**

* ABC NFTs supply = 10,000
* Underworld NFTs supply = 30,000
* Unstaking has a 21 days cool down period. No emission take place during that period.
* $HADES is emitted per second (0.1902379039 $HADES per second), with 500,000 $HADES to be distributed each month.


---

# 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.hadeswap.com/whitepaper/usdhades-tokenomics/usdhades-emission-schedule-and-use-case.md?ask=<question>&goal=<endgoal>
```

`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.