> For the complete documentation index, see [llms.txt](https://docs.golddiggersnft.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.golddiggersnft.com/tokens-gold-dust-flake-nugget.md).

# Tokens: Gold Dust → Flake → Nugget

**Nugget is the meme coin of Robinhood Chain.** 1,000,000,000 supply, minted exactly once. Dust and Flake are the wash — the work the camp does before the ticker is live, so Nugget launches with a story.

Every token is fixed supply, minted once. No inflation at any level.

| Token     | Ticker | Supply          | Role                             |
| --------- | ------ | --------------- | -------------------------------- |
| Gold Dust | DUST   | 100,000,000,000 | What the camp pans               |
| Flake     | FLAKE  | 10,000,000,000  | The wash; Dust's trading partner |
| Nugget    | NUGGET | 1,000,000,000   | The meme coin                    |

### They don't all go live at once

Dust launches first. After about 3 weeks of Dust collection, Flake goes live as Dust's trading partner. About 3 weeks after that, Nugget.

Each stage is a participation check: if people are actually earning and holding, the next token has a reason to exist. That's how volume gets incentivized.

### Converting up the ladder

Once the next token is live:

* Burn 10 DUST → 1 FLAKE
* Burn 10 FLAKE → 1 NUGGET, drawn from a fixed, pre-funded pool
* The 100:10:1 ratio is deliberate — the entire Nugget supply is reachable through the ladder, nothing gets permanently stranded.
* Leftover that isn't a clean multiple of 10 ("tailings") stays in your wallet — not lost, just not enough yet to convert.

### What you can do with them

All three are standard, fully transferable ERC-20s. Hold them, send them, convert them once the next token is live, or trade them when the pair is up. Nugget is the coin.


---

# 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.golddiggersnft.com/tokens-gold-dust-flake-nugget.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.