> For the complete documentation index, see [llms.txt](https://docs.wingbits.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wingbits.com/tge-mainnet/claiming-grace-period.md).

# Claiming Grace Period

### **What's the Claim Grace Period?**

All earned tokens will have a 7-day grace period before they become claimable. This means your daily rewards will be visible in your dashboard immediately but become available to claim after 7 days.

### **Why We Do This?**

Following best practices from successful projects in the space, this security buffer protects against unforeseen issues and ensures accurate token distribution. This is about protecting the long-term value and stability of the network for everyone.

**How It Works:**

* Earn today (for previous day) → Rewards placed in Pending
* After 7 days in Pending → Rewards available as Claimable

### **Important Notes for Beta Participants:**

* Your total beta rewards are based on all earnings prior to the 7 days before Mainnet.
* You'll have claimable tokens ready from day one.
* New stations on Mainnet follow the standard 7-day wait before their first rewards become claimable.


---

# 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.wingbits.com/tge-mainnet/claiming-grace-period.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.