> For the complete documentation index, see [llms.txt](https://saberbothq.gitbook.io/saberbot-documentation-v2/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://saberbothq.gitbook.io/saberbot-documentation-v2/key-features/token-safety-check.md).

# Token Safety Check

<figure><img src="/files/lLsYc8odBK52icObrIvu" alt="" width="366"><figcaption><p>Token Safety Page</p></figcaption></figure>

**Note:** This feature is currently in BETA, please report any inaccuracies to the team on Telegram.

**Disclaimer:** There are always ways for bad actors to bypass checks - use your discretion and never trade more than what you are willing to lose. The best check is and always will be common sense.

### How to Unlock

Users who hold at least 100K Saber tokens in their SaberBot wallet will automatically unlock access to this feature.

### Checks Explanation

#### Mint Cap

**States:**

* ✅ Mint Cap reached! No more mints can occur:
  * If the mint cap is reached, the minter cannot mint more supply at the current moment.
  * If the circulating supply falls below the mint cap (e.g., in the event of a burn), the minter can still mint tokens up to the mint cap.
  * Allows dynamic token supply within set parameters, especially when the minter is a smart contract.

#### CW20 Minter

**States:**

* 🛑 Mint Cap not reached! Mints can still occur:
  * Minter can mint more tokens above the current supply.
  * Best paired with the minter renounced check as assurance that there can be no further mints on the token.

#### Minter Renounced

**States:**

* ✅ Minter renounced!:
  * If the minter role is renounced, no more tokens can be minted, even if the circulating supply falls below the minting cap.
* 🛑 Minter not renounced:
  * The minter contract still retains the ability to mint if the total token supply falls below the max cap (e.g., if tokens are burnt).

#### Contract Admin Renounced

**States:**

* ✅ Contract admin renounced!:
  * Contract admin has renounced their ability to migrate the contract to a new contract unilaterally.
* ❗️ Contract admin not renounced. Contract might be migratable:
  * Contract admin is not renounced. This means that the contract admin may be able to migrate the contract to a new one unilaterally.

#### Liquidity Pool Tokens Burn

**States:**

* 🟢 LP burn XX.XX%
* 🔴 LP burn 0.00%

### Conclusion

Each individual check by itself does not inherently determine whether a contract is safe or unsafe. Use your own discretion and understand the motives behind why a contract admin might or might not have done something.


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://saberbothq.gitbook.io/saberbot-documentation-v2/key-features/token-safety-check.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.