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

# 🪂 Airdrops

#### What Will Be Airdropped <a href="#what-will-be-airdropped" id="what-will-be-airdropped"></a>

HellStreet introduces a structured airdrop system designed to reward active users, creators, and early participants of the ecosystem. A total of **120,000** **Utility Assets** will be distributed in phases through **Digital Drop Packs**, each containing in-game items, access utilities, and progression-based rewards.

**These packs are categorized by rarity and purpose, ensuring both new and advanced users receive meaningful value:**

| Drop Pack             | Max Supply | Items per Pack | Content Type Distribution                                | Rarity Distribution                            |
| --------------------- | ---------- | -------------- | -------------------------------------------------------- | ---------------------------------------------- |
| **Starter Drop Pack** | 70,000     | 1–2            | <p>Wearables: 50% Access Keys: 30%</p><p>Boosts: 20%</p> | Common: 100%                                   |
| **Creator Drop Pack** | 25,000     | 1              | <p>Tools: 60%</p><p>Assets: 40%</p>                      | Common: 70% Uncommon: 30%                      |
| **Premium Drop Pack** | 18,000     | 1–3            | <p>Assets: 50%</p><p>Access Keys: 25% Boosts: 25%</p>    | <p>Uncommon: 40% Rare: 40%</p><p>Epic: 20%</p> |
| **Elite Drop Pack**   | 7,000      | 2–4            | <p>Exclusive Assets: 60%</p><p>Event Access: 40%</p>     | Epic: 50% Legendary: 35% Mythic: 15%           |

#### Eligibility <a href="#eligibility" id="eligibility"></a>

To qualify for HellStreet airdrops, users must meet at least one of the following activity conditions within the ecosystem:

* Active participation in gameplay (missions, events, or sessions)
* Ownership of HellStreet assets or collectibles
* Interaction with creator content (buying, attending, supporting)
* Holding or staking $HST

*Eligibility is evaluated on a rolling basis, meaning consistent engagement increases the likelihood of receiving higher-tier rewards*

***

#### Reward Allocation <a href="#reward-allocation" id="reward-allocation"></a>

HellStreet uses a **Dynamic Activity Score (DAS)** system to determine airdrop distribution. This system evaluates user behavior across multiple dimensions:

* Gameplay Activity → completing missions, time spent in-world
* Asset Ownership → quantity and rarity of owned items
* Economic Participation → marketplace usage, $HST transactions
* Creator Interaction → supporting or publishing content

Each user is assigned a score, and rewards are distributed proportionally within each drop cycle.

***

**Important notes:**

* Higher engagement = higher allocation probability
* Limited supply per drop → not all eligible users receive rewards
* Rewards scale with long-term participation, not one-time actions

**This ensures the airdrop system remains sustainable, merit-based, and aligned with real platform usage rather than passive holding.**


---

# 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://hellstreet.gitbook.io/hellstreet-docs/economy/airdrops.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.