> For the complete documentation index, see [llms.txt](https://docs.fiefdom.gg/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.fiefdom.gg/core-apps/troves.md).

# Troves

<figure><img src="/files/C0kZJQT8AOSGiaQ6jadt" alt=""><figcaption></figcaption></figure>

### Visit Site: <https://troves.fiefdom.gg/>

***

What are Troves?

Troves are custom designed token indices that provide specialized insights into token categories.

#### What pain point does Troves solve?

Troves were born out of a frustration with current analytics platforms that design category trackers with limited granularity. This is compounded by the issue that most platforms build categories using requests from projects that are often not fully accurate.

#### Are Troves Tradable?

No, not currently. Troves are meant to provide curated information; however, tokenization via Fief Protocol or independent third party on the Fiefdom network is a potential path. This would require improvements to data oracles, among other considerations.

If you are a developer and want to contribute to the Troves project, or build your own app on top of it, reach out to the Fief team.


---

# 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.fiefdom.gg/core-apps/troves.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.