> For the complete documentation index, see [llms.txt](https://docs.krystal.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.krystal.app/products/others/point-system.md).

# Point System

> **The Krystal Point System is designed to reward our dedicated users who support Krystal by using our product and providing valuable feedback to help us achieve product-market fit.**

There are 3 groups of users who will be rewarded Krystal Points:

* Legacy users who had interacted with Krystal smart contract before January 1st, 2024
* Early adopters who (1) swapped or performed any LP transaction on Krystal from January 1st, 2024 to March 24th, 2024, or (2) minted an NFT from our 2 Galxe campaigns: [Celebrating 2 Years campaign](https://galxe.com/krystalwallet/campaign/GCkk1U6xRM) and [LP campaign](https://galxe.com/krystalwallet/campaign/GCbyhU7YgL)
* Current users who are using Krystal since the Point System started on March 25th, 2024

Further information about each user group can be found in the following sections.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.krystal.app/products/others/point-system.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.