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

# Staking

In February 2022 we started the creation and introduction of the Dracards metaverse.

![](/files/GeYjmlouNX4Mxagbwddc)

We launched our world map, and with that a showcase of different regions of this environment. The first region launched and marketed was the High Market, located in the city of Markevia, new regions will come later on.

![Overview of buildings on High Market](/files/QasVXADOjzyN0P4cIyvZ)

Within this region, several structures and buildings were made available that could be acquired by players/investors. These buildings are the first phase for our staking system, which will work differently from other known systems, aiming at the economic sustainability of our metaverse. Buildings have slots in which cards of different rarities can be allocated, as well as different amounts. 

Suppose you have a building that contains a slot that holds up to 3 rare cards, so you can add a rare and two uncommon cards, for example. Or, following the same slot example, you can add two rare cards and one common. But you will never be able to add an epic or legendary card to that slot, as it goes beyond the maximum rarity limit. 


---

# 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://dracards.gitbook.io/main/whitepaper/staking.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.