> For the complete documentation index, see [llms.txt](https://docs.superteam.fun/the-superteam-handbook/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.superteam.fun/the-superteam-handbook/community/the-reputation-system/case-study-superteam-earn.md).

# Case Study: Superteam Earn

## About the Project

All earning opportunities in the Solana ecosystem, aggregated in one place: <https://earn.superteam.fun/>

## Self-reported milestone: Mainnet Launch

### Teamwide XP Info

1. Total Time Taken: 303 Hours
2. Multiplier: 3.5 (since it's an critical flagship project that everyone within the ecosystem will benefit from)
3. Total XP = Total Time Taken \* Multiplier \* 10 = 10605

### Individual XP Info of Team Members

1. **Kash**

   * Responsible for: Product Development, BD
   * %age contribution: 25%
   * XP earned: 25% of Total XP, rounded to the nearest whole number = 2652

2. **Yash**

   * Responsible for: Product Design, UI/UX
   * %age contribution: 22&#x20;
   * XP earned: 22% of Total XP, rounded to the nearest whole number = 2334

3. **Bolt**

   * Responsible for: Fullstack Development
   * %age contribution: 27
   * XP earned: 27% of Total XP, rounded to the nearest whole number = 2864

4. **Srijan**

   * Responsible for: Fullstack Development
   * %age contribution: 15
   * XP earned: 15% of Total XP, rounded to the nearest whole number = 1591 **(Despite the fact that he was responsible for 7% of the total project hours)**

5. **Pratik**

   * Responsible for: Operations and Data Management
   * %age contribution: 10&#x20;
   * XP earned: 10% of Total XP, rounded to the nearest whole number) = 1061

6. **Srijani**
   * Responsible for: Operations
   * %age contribution: 1
   * XP earned: 1% of Total XP, rounded to the nearest whole number = 107


---

# 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.superteam.fun/the-superteam-handbook/community/the-reputation-system/case-study-superteam-earn.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.