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

# Points Program

The QuBitDEX Points Program is a pre-TGE (Token Generation Event) initiative designed to reward users who contribute to the long-term success of the protocol.The system is based on a dual-layer mechanism designed to quantify both the "quantity" and "quality" of user contributions.

<mark style="color:$primary;">**Layer 1: Base Points**</mark>

* **Definition:** Users earn "Base Points" in real-time from the trading fees they generate. This serves as the quantifiable metric for a user's direct contribution to the protocol's core revenue.

<mark style="color:$primary;">**Layer 2: Daily Dynamic Multiplier**</mark>

* **Definition:** Each day, a "Dynamic Multiplier" is calculated for each active user. This multiplier is determined by a confidential algorithm that assesses multi-dimensional contribution metrics (e.g., PnL, position health, ecosystem participation). The multiplier is then applied to the Base Points calculation to determine the user's final daily points.

The program will be structured in multiple seasons to maintain long-term engagement and ensure fairness.Between seasons, the points rules, weights, and multiplier caps may be periodically updated to adapt to the protocol's evolving needs and reward more diverse forms of participation.

To maintain the integrity and fairness of the Points Program, the following rules apply:

* **Anti-Sybil & Malicious Activity:** The protocol will employ on-chain and off-chain methods to detect and penalize Sybil attacks and other malicious activities designed to unfairly game the system. Accounts identified as engaging in such activities may have their points partially or fully revoked.

### FAQ <a href="#faq" id="faq"></a>

* <mark style="color:$primary;">**What is the QuBitDEX Points formula?**</mark>

The formula is dynamic and opaque by design, updated as usage evolves.

* <mark style="color:$primary;">**What activities earn points?**</mark>

Many activities are tracked by our points program, and attribution for different activities may happen immediately or be applied over-time over several distributions.

* <mark style="color:$primary;">**Do people with multiple accounts have an advantage over me?**</mark>

No. Discrete or costless actions do not yield rewards in isolation. Having 100 accounts provides no advantage over one.

* <mark style="color:$primary;">**Do early users have an advantage?**</mark>

Pacifica's points program is structured to balance both early supporters and long-term contributors fairly.

* <mark style="color:$primary;">**Can I buy points?**</mark>

No. There was no prior allocation and there is no way to purchase points. They can only be earned by trading, providing feedback, and spreading the word.<br>


---

# 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://qubitdex.gitbook.io/main/qubitdex-program/points-program.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.
