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

# Seasons & leaderboard

Asteroid Shiba is played in **seasons**. Each season has a fixed pool of valuable asteroids, its own hunt, and its own competition.

## Explorer Points & the leaderboard

As you research your asteroids, you earn **Explorer Points**. Points determine your place on the **season leaderboard** — a race among all explorers to build the most valuable operation.

```
Find asteroids → Research them → earn Explorer Points → climb the leaderboard
```

## Season 1 leaderboard reward

The **$ASTEROID token has not been issued yet.** What Season 1 does is decide who is standing in line when it is.

At the end of Season 1, the **top 100 explorers** on the leaderboard are added to the **token whitelist**, and **2% of the future token emission** is reserved for that group — distributed by rank. The higher you finish, the bigger your share.

{% hint style="info" %}
No token exists today and nothing is claimable yet. Exact per-rank allocations, token details, and claim & vesting terms will be published with the tokenomics ahead of the token generation event (TGE).
{% endhint %}

## What's coming

Seasons are the frame for everything ahead: seasonal gameplay, **tournaments**, special events, new mechanics, and an ever-expanding world to explore. Each season is a fresh hunt with new opportunities.

{% hint style="info" %}
Exact season length, leaderboard reward size, and distribution are set per season and announced ahead of each one.
{% endhint %}

**Next:** [Founder Phase →](/asteroid-shiba-docs/founder-phase/overview.md)


---

# 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://asteroid-shiba.gitbook.io/asteroid-shiba-docs/seasons-and-competition/overview.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.