# Token Security Check **Token Security Check:** Liquidity Lock, Honeypot Detection, Rug Probability ⚠️ **Disclaimer:** Token security checks are for reference only and cannot guarantee 100% accuracy.\ Please compare results across multiple audit tools before trading. ### Example of Solana
| Mint Authority Revoked | “Yes” indicates higher safety — the project cannot mint new tokens and dilute supply. | | ---------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | Top 10 Holders | “Yes” indicates safety — the top 10 holders own less than 30% of the total supply. | | Blacklist |

“No” indicates safety — the project cannot blacklist arbitrary wallets, reducing honeypot risk.
“Yes” means your wallet is blacklisted — you cannot sell this token, and your wallet may be frozen.

| | Burned |

Displays liquidity burn percentage. The higher the percentage, the safer the project.
100% means the project cannot withdraw liquidity.

| ### Example of Ethereum Also available for other EVM Chains, like BSC, Polygon, Base, and so on.
| Honeypot |

“Yes” means the token is a honeypot — its smart contract restricts selling, causing user losses.
Honeypot detection relies on third-party data sources such as GoPlus. Due to possible delays, Debot cannot guarantee absolute accuracy or timeliness. Always cross-check with multiple token audit tools before trading.

| | ------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | Verified | The token contract is verified and open-source on **Etherscan**, allowing users to review the code. | | Renounce |

The project has renounced ownership permissions.
⚠️ Some contracts may fake renouncement but still retain upgrade access — allowing developers to change code, turn it into a honeypot, or blacklist users.

| | Lock |

Evaluates if there is a risk of liquidity removal.
LP tokens may be locked (retrievable after expiry) or burned (sent to a blackhole address, permanently locked).

| | Buy/Sell Tax |

Displays the transaction tax percentage.
If the sell tax is excessively high (e.g., 99%), it indicates a honeypot — you won’t be able to sell. Exit immediately!

| ### Additional Notes DeBotAI currently integrates results from two third-party security providers (e.g., **GoPlus**). These tools offer **preliminary** contract risk analyses and warnings, but their conclusions may **not** always be accurate. Reasons include: 1. **Smart contract complexity**\ Contracts can contain intricate logic or dynamic behavior that automated tools cannot fully interpret. Certain techniques may alter behavior at runtime, making outcomes hard to predict. 2. **Evolving attack vectors & new vulnerabilities**\ The crypto ecosystem moves quickly. New exploits emerge faster than tools can adapt, especially those not yet widely documented, reducing detection effectiveness. 3. **Tool evasion by design**\ Experienced developers may deliberately structure code to bypass automated checks—e.g., hiding or delaying malicious behavior—so audits appear “clean” while runtime risk remains. 4. **Upgradable/proxy contracts**\ Many contracts are upgradeable. Even if the **current** version passes checks, future upgrades (via admin or governance) can introduce bugs or malicious logic that static tools cannot foresee. 5. **Disguised honeypots**\ Honeypot logic can be gated behind complex conditions or specific interactions, appearing normal under typical checks and only activating in edge cases that tools may miss. 6. **Timelocks & delayed triggers**\ Some malicious behaviors activate only after a delay or once certain conditions are met. Static analysis struggles to catch these. As a result, a token’s risk indicator may turn from **green to red within seconds**. Delayed-honeypot patterns are not reliably detectable by any audit provider at present. > DeBotAI does **not** validate nor assume responsibility for the quality of third-party assessments. Always perform your own due diligence before purchasing any token. ⚠️ **Disclaimer:** Token security checks are for reference only and **cannot guarantee 100% accuracy**. Compare results across multiple security tools **before trading**. --- # 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.debot.ai/en/basic-features/token-security-check.md?ask= ``` 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.