> For the complete documentation index, see [llms.txt](https://wiki.openloot.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://wiki.openloot.com/ol-token/ol-tge-airdrop.md).

# $OL TGE Airdrop

The Open Loot Airdrop Reward Program is a special initiative to reward users with Open Loot Reward Points based on their activity in Big Time and on the Open Loot marketplace.

#### Purpose of the Airdrop

This airdrop is designed to reward Open Loot’s best users and to kick start the use of $OL for transactions on openloot.com/marketplace.

#### Eligibility

To be eligible for this airdrop, players must have transacted on the Open Loot marketplace or completed a Prestige Portal since October 2023. One of the key $OL utilities is that it can be used on Open Loot for sale discounts, exclusive sales, and early access to new Open Loot titles, so we want to reward our most active players.

#### How to Get the Rewards

Your Open Loot Reward Points rewards are determined based on two factors:&#x20;

1. Participating in the Open Loot marketplace, including acquiring NFTs or items from any Open Loot game.
2. Completing Prestige Portals in Big Time.

More recent purchases and gameplay activities are weighed more heavily than older events. Your rewards are also tied to your current rank in Big Time by the time of the TGE.

#### Rewards:

TBA


---

# 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://wiki.openloot.com/ol-token/ol-tge-airdrop.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.
