> For the complete documentation index, see [llms.txt](https://docs.layerhub.xyz/untitled/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.layerhub.xyz/untitled/wallets-checking/leaderboard-and-ranking.md).

# Leaderboard and Ranking

In the ever-evolving landscape of crypto projects and ecosystems, the need for mechanisms to evaluate user performance, engagement, and contribution is of paramount importance. Among these mechanisms, ranking and leaderboard creation stand out as powerful tools that provide not only a sense of achievement but also serve as key drivers of community engagement and ecosystem growth. The essence of ranking and leaderboard creation lies in their ability to motivate users, encourage active participation, and foster a sense of community within crypto projects.

Creating a leaderboard for individual projects involves the development of a methodology to rank users' contributions and activities within the project's ecosystem. This methodology should be fair, transparent, and data-driven, and it should encompass a range of metrics relevant to the project's goals and objectives.

{% hint style="info" %}
Ranking methodologies for each project can be found in the next section.
{% endhint %}


---

# 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.layerhub.xyz/untitled/wallets-checking/leaderboard-and-ranking.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.