> For the complete documentation index, see [llms.txt](https://doc.ave.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.ave.ai/tutorial/quick-guide-for-beginners/how-do-i-avoid-rug-pulls.md).

# How Do I Avoid Rug Pulls?

No platform can guarantee that a token is safe. A security scanner reduces information gaps; it does not eliminate trading risk.

Ave.ai provides contract-security checks powered by GoPlus, covering indicators such as:

* Proxy-contract risk
* Blacklist functionality
* Administrator permissions
* Additional minting capability
* Top-holder concentration
* Liquidity-pool locks or burns

Ave.ai explicitly notes that these results are for reference and should not be the sole basis for evaluating a contract.

Its token interface also displays a Rug Pull Index with information such as the developer’s history and previous incidents involving liquidity removal or token dumping.

Press enter or click to view image in full size

<figure><img src="https://miro.medium.com/v2/resize:fit:700/1*Rg1M7hKZso-RbHVwu1MMRg.png" alt="" height="326" width="700"><figcaption></figcaption></figure>

#### Before buying, check the following <a href="#b5b0" id="b5b0"></a>

**Can the token be sold?**\
Review live transactions for successful sells. A chart full of buys with no sells is a major warning.

**Is liquidity locked or burned?**\
Unlocked liquidity may allow the provider to withdraw the trading pair’s assets.

**Can more tokens be minted?**\
Unlimited minting can dilute existing holders and enable sudden dumping.

**Can addresses be blacklisted?**\
Blacklist functions may allow the contract owner to prevent selected wallets from selling or transferring.

**Can taxes be changed?**\
A low current tax is not enough if the developer can later raise the sell tax dramatically.

**Has ownership been renounced?**\
Renouncement can reduce certain administrative risks, although it does not prove that a project is legitimate.

**Who controls the supply?**\
A clean contract does not prevent a developer or insider cluster from dumping a large allocation.

**Does the developer have a suspicious history?**\
Review linked tokens and past rug-pull behavior where data is available.

Treat every check as one layer of defense. Contract analysis, holder distribution, liquidity, developer behavior, and real trading activity should all support the decision.