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

# Season One

Season One will run prior to token launch and will be based on a points system. 

The season will help battle-test the Ithaca Ecosystem tokenomics and incentivize growth ahead of token launch. 

The airdrop will be based on a transparent points incentive program. 

#### Summary:

* Airdrop at the end of Season One. 
* Timing of TGE will be subject to protocol traction and market conditions so as to optimize ecosystem value.
* You can earn points for trading and engagement according to transparent formulas.
* Tokens will be issued in proportion to points earned; Season One to distribute up to 2bln points. 
* Season One Airdrop will distribute up to 2% of the total token supply.


---

# 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.ithacaprotocol.io/docs/ecosystem/airdrops/season-one.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.