> For the complete documentation index, see [llms.txt](https://docs.yakkamon.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.yakkamon.com/pre-registration/free-mint.md).

# Free Mint — 14th September

**👉 Mint here:** [**marketplace.roninchain.com/launchpads/mints/yakkamon**](https://marketplace.roninchain.com/launchpads/mints/yakkamon)

<figure><img src="https://3777468385-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FPCjLqiFAZZfmuQmc2nG9%2Fuploads%2F9y8UUGrZDbpHGc2fATfE%2Flegendaries.png?alt=media&amp;token=39a26c69-8c1b-4069-b08f-4908218f0123" alt=""><figcaption></figcaption></figure>

On **14th September**, the Yakkamon free mint goes live on the **Ronin Launchpad**. The NFTs are minted on the **Ronin blockchain**, so you'll need a Ronin wallet. Free to mint — you only pay gas.

### Hidden NFTs — reveal on 14th October :tada:

**10,000 Genesis 'Hidden' Monster NFTs** are available to *mint*. You mint blind; every NFT is revealed on **14th October**.

Hidden in the drop are **68 legendaries** — 3 Raigo, 5 Ondi, 10 Kova and 50 Salu (all Dragon type) — plus 50 Rare Malandrix (Psychic) and 10,316 Uncommon Brazito (Fire). See the [Yakkapedia](/content/yakkapedia.md) for the full monster list.

Each monster will have unique stats & usable in game.

### Whitelisted waves

The free mint goes live in waves. **Check your eligibility — including the full wave schedule, supply and details — at** [**yakkamon.com/whitelist**](https://yakkamon.com/whitelist)**.**

{% hint style="warning" %}
**This snapshot is only for the Ronin free mint.** It does not lock the **trainer airdrop** — that leaderboard keeps running and finalises separately, one week before early access launch (see [Important Dates](/pre-registration/important-dates.md)).
{% endhint %}

### How to mint?

1. **Pre-register and verify** your account before 10th September.
2. **Deposit 5 $FLOWER** if your wave requires it — check [yakkamon.com/whitelist](https://yakkamon.com/whitelist).
3. **Connect your Ronin wallet** to the Ronin Launchpad on mint day.
4. **Mint** when your wave opens. Keep gas in your wallet.
5. **Wait for the reveal** on 14th October to see which monster you got.

### FAQs

*What blockchain is the free mint on? Ronin — the NFTs are minted on the Ronin blockchain via the Ronin Launchpad, and you'll need a Ronin wallet with a little RON for gas.*

*What is the total supply that will be revealed on 14th of October - 10,434*

*Can I mint more than one? Yes, if you meet the eligibility requirements in each wave. You can only mint a maximum of 1 per wave.*

*How do I use them? Once early access begins, you will be able to deposit them into the game*

*Can you trade hidden NFTs? Yes, these are NFTs that can be traded prior to reveal.*

{% hint style="info" %}
An extra 1,500 hidden egg NFTs will be minted after the free mint and distributed out in special events before the reveal happens.
{% 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://docs.yakkamon.com/pre-registration/free-mint.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.