> For the complete documentation index, see [llms.txt](https://teamdchess.gitbook.io/dchess/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://teamdchess.gitbook.io/dchess/english-1/dchess-game/lootboxes.md).

# Lootboxes

![](/files/hkWPMUvFmGb3SFd1JHk8)

LOOTBOXES arise in response to the need to keep the economy sustainable and durable. LOOTBOXES are "lucky boxes" that contain an initially undetermined digital asset inside. When purchased, the user will obtain a digital asset that will be found inside the LOOTBOXES. These may be purchased exclusively using KING tokens, having a value associated with a stablecoin (cryptocurrency designed to reduce volatility in its value, often associated with the value of a fiat currency, such as the US dollar, so 1 stablecoin=1usd).

The proceeds from LOOTBOXES will go 75% to the burning of the KING and the remaining 25% will be used to finance the project.

The lootboxes will be categorized by:

* **Avatars**
* **Frames**
* **Cards**
* **Deluxe Box**
* **Boards**


---

# 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://teamdchess.gitbook.io/dchess/english-1/dchess-game/lootboxes.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.