> 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 198-piece NFT collection of gold-rush prospector figurines, live on **Robinhood Chain** (an Arbitrum L2). Every Digger's real artwork stays completely secret until the exact moment it mints — nobody, including the team, can see a piece's traits ahead of time.

## The short version

* Mint or buy a **Claim Deed**, then redeem it for a **Digger** NFT — instantly revealed the moment you mint.
* Earn **Gold Dust** by staking any Digger (Legendaries earn 2.5x), or by joining the Ambassador program.
* Work Dust up through **Flake** into **Nugget** through a fixed 10:1 burn ladder — all three tokens are capped supply, minted once, no inflation, ever.

## What's in this wiki

* **NFTs** — Claim Deeds and Diggers, including the 5 Legendaries
* **Tokens** — Gold Dust, Flake, Nugget and how they convert
* **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 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/gold-diggerusd.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.