> For the complete documentation index, see [llms.txt](https://azoth.gitbook.io/azoth-white-paper/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://azoth.gitbook.io/azoth-white-paper/alchemy-rush/editor.md).

# Points System

## **1. What is Alchemy Rush?**

**Alchemy Rush** is **Azoth’s RWA trading platform** exclusive loyalty and rewards program, designed to incentivize long-term user engagement. By holding eligible tokens, maintaining VIP status, or owning NFTs, users accumulate **Alchemy Points (P)** each season, which can be redeemed for future platform benefits such as **airdrops, fee discounts, and exclusive perks**.

## **2. Points Calculation Mechanism**

Alchemy Rush employs a dynamic points model where a user’s total score **P** is determined by:

#### **Core Formula**

P=∫t0t1\[∑i=1NAi(t)⋅wi(t)]⋅V(t) dtP=∫t0​t1​​\[∑i=1N​Ai​(t)⋅wi​(t)]⋅V(t)dt

**Key Variables**

| Variable         | Meaning                                      | Impact                                |
| ---------------- | -------------------------------------------- | ------------------------------------- |
| **Ai(t)Ai​(t)**  | Amount of **Token \*i\*** held at time \*t\* | More holdings = higher points         |
| **wi(t)wi​(t)**  | **Dynamic weight** of Token \*i\*            | Higher weight = more points per token |
| **V(t)V(t)**     | **Boost multiplier** (VIP, NFT bonuses)      | Increases overall points earned       |
| **t0→t1t0​→t1​** | **Season duration**                          | Longer participation = more points    |

#### **Discretized Calculation (For On-Chain Implementation)**

Since blockchain data is discrete, the formula is computed as a sum over blocks:\
P≈∑j=1M(∑i=1NAi(tj)⋅wi(tj))⋅V(tj)⋅ΔtP≈∑j=1M​(∑i=1N​Ai​(tj​)⋅wi​(tj​))⋅V(tj​)⋅Δt\
Where:

* **tjtj​** = Timestamp of block \*j\*
* **ΔtΔt** = Time between blocks
* **MM** = Total blocks in the season

### **3. How to Maximize Points?**

Users can optimize **Alchemy Points** by:\
**Holding high-weight tokens** (assets with larger wi(t)wi​(t))\
**Boosting V(t)V(t) with VIP tiers or NFTs**\
**Participating long-term** (points accumulate over time)

### **4. Points Utility**

Alchemy Rush points can be used for:

* **Governance voting rights**
* **Token airdrops**
* **Trading fee discounts**
* **Exclusive NFT/VIP rewards**

### **5. Season Rules**

Each season runs for a fixed period (e.g., 3 months), with rewards distributed afterward.

**Token weights (wi(t)wi​(t)) may adjust** (e.g., seasonal promotions for certain RWAs).

**V(t)V(t) boosts stack** (e.g., holding an NFT + VIP yields higher multipliers).

### **6. Why Alchemy Rush?**

&#x20;**Transparent & Fair**: Fully on-chain verifiable scoring.\
&#x20;**Long-Term Incentives**: Rewards loyal users, not short-term speculation.\
&#x20;**Dynamic Optimization**: Adjustable weights adapt to market conditions.

**Join Alchemy Rush today and turn your holdings into rewards!** 🏆<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://azoth.gitbook.io/azoth-white-paper/alchemy-rush/editor.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.
