> For the complete documentation index, see [llms.txt](https://docs.wlos.dev/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wlos.dev/pack-purchase-splits.md).

# Pack Purchase Splits

**Each pack purchase follows this breakdown:**

| Destination           | Percentage | Description                                                                                        |
| --------------------- | ---------- | -------------------------------------------------------------------------------------------------- |
| 🧑‍🌾 Farming Pool    | 30%        | Fuels the rewards pool for Farmers. This ensures continuous yield distribution for active holders. |
| 🔐 Staking Pool       | 30%        | Enhances staking reward pools, incentivizing long-term commitment.                                 |
| 🔥 Burn               | 10%        | Reduces total supply by permanently removing WLOS from circulation.                                |
| 🧠 Development Wallet | 25%        | Supports backend infrastructure, game expansions, and overall platform improvements.               |
| 🏦 Treasury Reserve   | 5%         | Stored for future use, emergencies, or platform scaling decisions.                                 |

***

### Pack Pricing (in WLOS)

To maintain internal economy and stimulate demand, packs are priced in SOL:

* Common Pack → 0.1 SOL
* Rare Pack → 0.4  SOL
* Legendary Pack → 1 SOL

> These prices are fixed in SOL and allow early users to benefit from lower token prices. The actual dollar cost will vary based on token market price.

***

### Real Utility for WLOS

By purchasing packs, users:

* Actively reduce token circulation via burns,
* Reinforce reward mechanisms for staking and farming,
* Directly fund future updates and innovation.

> Pack purchases are the heartbeat of the WLOS economy


---

# 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.wlos.dev/pack-purchase-splits.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.