> For the complete documentation index, see [llms.txt](https://degen-skulls.gitbook.io/degen/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://degen-skulls.gitbook.io/degen/tokenomics/dgn-tokenomics.md).

# DGN Tokenomics

## **A fair launch utility token built for memes, not speculation.**

$DGN is the utility token of **Degen** — powering meme visibility, creator tools, and community incentives across X1 and Solana.

There are no insiders, no pre-sale, and no VC allocations. $DGN was **fair-launched**, meaning the people who use it, earn it, and burn it are the ones who drive its value.

***

#### 🧾 Token Details

| Parameter         | Value         |
| ----------------- | ------------- |
| **Token Name**    | Degen Token   |
| **Ticker**        | $DGN          |
| **Total Supply**  | 1,000,000,000 |
| **Launch Method** | Fair launch   |
| **Initial Chain** | Solana        |
| **Future Chain**  | X1            |

***

### ⚙️ Utility Overview

$DGN is used directly within Degen — not just traded or held. Its value is tied to platform usage and ecosystem activity.

| Feature                      | Utility Description                                                   |
| ---------------------------- | --------------------------------------------------------------------- |
| 🚀 **Shill Board Boosting**  | Promote your meme or token to the top of the Shill Board              |
| 🎨 **Unlock Creator Tools**  | Spend DGN to access overlays, badges, premium templates               |
| 💸 **Earn Through Activity** | Receive DGN for launching tokens, making leaderboards, or referrals   |
| 🔁 **Burnable Token**        | A % of spent DGN may be burned to reduce supply and increase scarcity |

***

### 🧼 Fair Launch Principles

$DGN is designed to align with Web3 values and regulatory best practices:

| Principle                       | What It Means                                                    |
| ------------------------------- | ---------------------------------------------------------------- |
| ❌ No Private Sale               | No early buyers or token deals                                   |
| ❌ No Team Allocation            | No hidden wallet, no “stealth dump” risks                        |
| ❌ No Promised Profits           | DGN is a tool, not a security                                    |
| ✅ Transparent Distribution      | All DGN is earned via usage, protocol incentives, or skull perks |
| ✅ Platform Utility from Day One | Used for boosts, visibility, and creator access                  |

***

### 🌐 Cross-Chain Strategy

* ✅ **Launch on Solana first** for wallet and liquidity access\
  ✅ **Bridge to X1** after mainnet stabilizes\
  ✅ **X1 becomes the native execution environment** for boosts, farming, and governance logic

***

### 🔥 TL;DR

> $DGN is a **fair launch utility token** — not a speculative asset.\
> It powers meme boosts, creator rewards, and visibility across Degen.
>
> If you want to **ape, create. If you want to earn, contribute.**
>
> 🚫 No insiders. 🚫 No promises. ✅ Just pure degen fuel.


---

# 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://degen-skulls.gitbook.io/degen/tokenomics/dgn-tokenomics.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.