> 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/gold-diggerusd.md).

# Gold Digger$

Gold Digger$ is a gold rush on **Robinhood Chain**: 198 prospectors, each one secret until the moment it mints, working a claim that prints the chain's meme coin.

You're not flipping a JPEG. You're in the camp. Stake a Digger, pan **Gold Dust**, wash it into **Flake**, and **Nugget** is what comes out of the ground — 1,000,000,000 supply, minted once, no more. That's Robinhood Chain's meme coin.

## The short version

* Mint or buy a **Claim Deed**, then redeem it for a **Digger** — instantly revealed the moment you mint. 198 claims. Five Legendaries hit the mother lode. The rest still pan.
* Earn **Gold Dust** by staking any Digger (Legendaries earn 2.5x), or by joining the Ambassador program.
* Tokens launch in stages: about 3 weeks of Dust collection, then **Flake** as Dust's trading partner, then **Nugget** — the meme coin. Each stage is why you were on the last one.
* 10:1 burns up the ladder. All three tokens are capped, minted once, no inflation.

## What's in this wiki

* **NFTs** — Claim Deeds and Diggers, including the 5 Legendaries
* **Tokens** — Gold Dust, Flake, and Nugget (the Robinhood Chain meme coin)
* **Earning Gold Dust** — staking and the Ambassador program
* **How to Get In** — minting, buying, and getting started
* **FAQ** — quick answers to the questions we hear most


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.golddiggersnft.com/gold-diggerusd.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
