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

# Overview

The Hunt is the Hyperlynx points program. **Trade. Provide. Refer. Every move earns points.** Points decide your share of the $LYNX airdrop.

## The creed

* **Trade** — swaps and (soon) more surfaces earn points.
* **Provide** — in-range liquidity earns points.
* **Refer** — bring hunters and earn an override on what they earn.

## How the airdrop works

* **30% of total supply — 300,000,000 $LYNX — is committed** to the program. That number is public and fixed.
* At TGE, points convert to $LYNX on a **share basis**: your share = your points ÷ all hunters' points.
* The exact per-point value stays **sealed until TGE**. You always see your own rank and standing — never a number that could be farmed or gamed.

{% hint style="info" %}
You see your rank. You never see the conversion rate or the network total. That's deliberate: a sealed denominator can't be farmed, and the suspense is part of the hunt.
{% endhint %}

## Genesis

The first month is **Genesis** — a **2× multiplier** on points, for everyone, from launch. It's the single best window to build a lead, and it only happens once.

## What earns

| Surface              | Status    |
| -------------------- | --------- |
| Spot swaps           | Live      |
| Liquidity (in-range) | Live      |
| Tokenized stocks     | Live      |
| Referrals            | Live      |
| Perps                | Soon      |
| Outcome markets      | After TGE |

## Next

Learn to stack your rate: [How to earn](broken://pages/09244a5fb9122245754388300b064457bf76e409).


---

# 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://hyperlynx.gitbook.io/hyperlynx-docs/overview.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.