# Access Model (Bot Token Gating)

Nano token is used for access control to the bot.

* Holders at or above 1% receive full bot access.
* Initial users at full-access tier have no cap on how much they can snipe.
* Tiered access is available through configured threshold levels (to be defined).
* The access model is designed to evolve as the ecosystem expands beyond bot-only usage.
* Staking period details are in draft and will be finalized in the next few days.

#### Revenue and Development Allocation

Nano takes 10% of realized profit on snipes as the baseline fee, and only when a snipe closes in profit—there is no comparable fee on losses; with longer committed staking, that rate scales down over time (from 10% at 1 month to 5% at 6+ months) while revshare eligibility scales up, so long-term stakers pay less and qualify for more upside. Because charges are tied to positive outcomes instead of a flat cut on every buy/sell, heavy losing or scratch periods can cost users less in bot fees than typical volume-based Telegram bots, and in some usage patterns realized costs can actually end up lower than always-on percentage fees—even though the headline rate on profit is higher than a tiny per-trade commission.

Fee structure can vary by user profile and risk mode.\
High-risk / high-return sniper profiles can access lower fee settings.

Thresholds, tier rules, and fee parameters may be adjusted over time to balance usage, performance, and protocol growth.

Disclaimer: By using Nano Bot, users acknowledge and accept all trading risk. The operator is not responsible for any losses, damages, or missed opportunities incurred through use of the bot.


---

# 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://nano-5.gitbook.io/nano-docs/documentation/getting-started/access-model-bot-token-gating.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.