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

# ALPHA Airdrops

The ALPHA tokenomics are designed to reward and incentivize the community that are actively participating in the ecosystem.

Here's how it works:

* **Revenue Allocation:** 50% of all protocol fees are used to purchase ALPHA, which is subsequently deposited into the Airdrop Reserves.
* **Staking Benefits:** ALPHA holders who stake their tokens in the ALPHA auto-compounding vault become eligible for regular airdrops. The size of these airdrops for each user is directly proportional to the amount of ALPHA staked.
* **Eligibility Requirements:** To qualify for airdrops, you must maintain active participation in the ALPHA Vault. The more ALPHA you stake and the longer you stake, the greater your potential rewards.
* **Transparency and Accessibility:** Details of each airdrop will be announced in advance. Additionally, you can view your anticipated share of the airdrop directly within the app, ensuring full transparency and easy access.

These tokenomics ensure that those who contribute to and engage with the ecosystem will be eligible for ALPHA airdrops, driving both growth and sustainability.


---

# 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.alphafi.xyz/alpha-token/alpha-airdrops.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.