> 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/lynx/claiming.md).

# Claiming

At the Token Generation Event (\~Q4 2026), your Hunt points convert to **$LYNX** and you claim.

## How the conversion works

* Conversion is **share-based**: your $LYNX = your points ÷ all hunters' points × the committed **300M**.
* The exact per-point value is revealed at TGE — the **Reveal**. Until then the denominator stays sealed (see [The Hunt overview](broken://pages/dae99a8e97a4d11fc36696470bf3c03bdb8c6989)).

## The claim

* **Full and unlocked.** Your full allocation is claimable at TGE — **no vesting, no lock, no penalty.**
* **Two paths:**
  * **Claim to $LYNX** — receive the liquid token.
  * **Claim into yLYNX** — stake in one step and start earning the fee share immediately. See [yLYNX & staking](broken://pages/bae1fe548632b69c50ae561a7cc9e3aaede6ca4c).

{% hint style="info" %}
Why no lock? The protocol is a [fee machine](broken://pages/963dfe997652672f82bd42aa0bf79d4466e42f7d). It doesn't need to trap anyone — even selling is volume that pays the holders who stake. So claiming is your call, with no strings.
{% endhint %}

## After TGE

TGE is a level-up, not a finish line. After it:

* **Pool-2 liquidity mining** opens from the liquidity allocation.

{% hint style="warning" %}
Dates are targets and can move. Watch the official channels (see [Links & community](broken://pages/b453cc6a5b14c9af600cd2038a7531bfc0900662)) for the confirmed TGE and claim window. Nothing here is financial advice.
{% endhint %}


---

# 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/lynx/claiming.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.