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

# Staking/Rewards

## Staking of Souls

Kami will collect souls over time from our proprietary non-custodial staking platform and exchange Souls for rewards and unique experiences.

Souls are not a token, it is earned by kami through a 'proof of history' approach (we are Solana after all). An experience point system just makes sense, right? We are Gods-in-training.

## Souls

Once you have collected enough souls you get to choose how you wish to exchange them:

1. Take advantage of discounted SaaS products
2. Eclipse ecosystem's point of entry
3. Events and experiences
4. Premium-grade merchandise and collectables
5. Unique collaborations with artists that are limited to just one-of-a-kind.
6. Trait shop
7. Craft a narrative for your Kami
8. ????

<figure><img src="/files/Ie19BKrj7NeSNDdTeK78" alt=""><figcaption><p><mark style="color:red;">Souls is not a shit coin, it is power &#x26; when you give, you shall receive.</mark></p></figcaption></figure>


---

# 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://kami-1.gitbook.io/kami/utility/staking-rewards.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.