# $HOTKEY

The tokenomics of $HOTKEY have been updated to reflect our commitment to building a sustainable and value-driven ecosystem. With a fixed total supply of 100 million tokens, the distribution ensures long-term growth and community trust.

{% hint style="success" %}
**Total supply:** 100,000,000

**Circulating supply:**  95,000,000

**Burned supply:** 5,000,000
{% endhint %}

<figure><img src="https://assets.hotkeyswap.com/aPNG/HKStaking.png" alt=""><figcaption></figcaption></figure>

## Allocation Breakdown

#### 95% – Circulating Supply

A total of 95 million tokens are in circulation, fueling the ecosystem, supporting user participation, and driving adoption across the DeFi space.

#### 5% – Burned Supply

5 million tokens have been permanently burned, reducing the total supply and introducing a deflationary mechanism that enhances the scarcity and potential value of $HOTKEY over time.

With **5 million tokens burned**, we are actively working to reduce the circulating supply, potentially increasing the scarcity and value of the $HOTKEY token over time.

***

### Dashboard & Analytics

For a comprehensive view of our financial and operational performance, please refer to our Dune dashboard:\
[**Hotkey Dashboard**](https://dune.com)

***

### Official Smart Contracts

All $HOTKEY contracts are verified and secure across supported networks:

* **Ethereum:** 0x018DD3A0Dd7F213cc822076b3800816d3CE1ED86
* **Base / BSC / Arbitrum:** 0x374Ad0440Cd5c8E1A8412C156BeeEcE108EF4bB6

🔗 Bridge your $HOTKEY here: [bridge.hotkeyswap.com](https://bridge.hotkeyswap.com/)

Powered by LayerZero, our bridge infrastructure ensures seamless, trustless transfers across chains.


---

# 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://docs.hotkeyswap.com/introduction/usdhotkey.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.