# Primary Vault Claims

## **Burn to Earn**

The Primary Vault Claim is your shot at cashing in on the vault’s treasure at the end of a cycle. It’s simple, powerful, and designed to reward those who play the game.

***

### **How It Works**

**Burn Your Tokens 🔥**\
During the Cycle End phase, head to the dApp and burn **the exact number of tokens recorded for you in the snapshot**.

* If the snapshot recorded you with **5,000,000 MONSTA**, you must burn **all 5,000,000** to claim your vault share for that cycle.
* Burning less than your full snapshot amount is not possible and means you **do not qualify** for any vault claim that cycle.

The dApp/claim logic will enforce this: only wallets that burn their full snapshot amount within the claim window will receive their share of that cycle’s vault.

**Claim Your Share 🏆**\
The vault assets are split proportionally based on:

* Your **snapshot balance**, and
* Whether you fully burned that snapshot amount during the claim window.

Bigger snapshot stack = bigger share of the vault, **as long as you complete the full burn**.

***

### (Cycle 1 Only) Bonus C2 Airdrop 🚀

For the transition from Cycle 1 to Cycle 2, eligible burn participants also receive a **one-time $MONSTA airdrop** from a dedicated Cycle 2 airdrop pool of 1 Billion MONSTA tokens.

* To be eligible, you must complete the **full burn** of your snapshot allocation during the Cycle 1 burn window.
* Among all addresses that fully burn, your share of the airdrop pool is **proportional to your burned amount** compared to the total burned.
* There are **no additional MONSTA airdrops** promised for later cycles—after Cycle 2, it’s all about the vault, rollover, and yield.

The token itself does **not** reset each cycle. $MONSTA continues forward—what resets each cycle is the vault accounting and the optional chance to cash out by burning your full snapshot allocation.

***

### **Claim Deadline**

For Cycle 1:

* Snapshot: **January 8th, 2026**
* Burn/claim window: **January 10th** **until January 31st, 2026**

If you **do not** complete the full burn of your snapshot allocation within the claim window:

* You **forfeit your vault share** for that cycle, and
* Your entire share of that cycle’s vault is treated as **unclaimed** and rolls into the **next cycle’s vault** for remaining holders—no exceptions.

You are free to trade your tokens after the snapshot. But if you want to claim your vault share, you must:

* Hold or rebuy back up to your **exact snapshot amount**, and
* Burn that full amount before the claim window closes.

This is where the game theory comes in—some players may sell after the snapshot at higher prices and try to buy back cheaper before the deadline to still complete their burn.

Deadlines will be announced and highlighted, so stay sharp. ⏳

***

### **What to Expect from the dApp**

The dApp will handle the heavy lifting. Once live, it’ll guide you through:

* Burning the **exact snapshot amount** securely 🔥
* Calculating your vault rewards 💰
* (For Cycle 1) Showing your eligibility and share of the Cycle 2 airdrop

***

### **Get Ready to Burn**

Whether you’re cashing in for gains or playing the post-snapshot game to optimize entry/exit, this is your chance to stay Based and keep stacking.

<figure><img src="/files/u6ZG0HMCEXzHyKDNQEvn" alt=""><figcaption><p>We're not saying he's a pyro...but we're also not <em>not</em> saying that ;)</p></figcaption></figure>


---

# Agent Instructions: 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:

```
GET https://docs.monstacorp.com/based-monsta/cycle-end-overview/primary-vault-claims.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
