> For the complete documentation index, see [llms.txt](https://docs.trnch.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.trnch.fun/guides/how-to-avoid-rugs-on-robinhood-chain.md). # How to avoid rugs on Robinhood Chain A practical checklist to protect your wallet when trading new Robinhood Chain tokens. The full guide, with live numbers, is on trnch.fun: [Robinhood Chain rug checker](https://trnch.fun/robinhood-chain/rug-checker). A practical checklist to protect your wallet when trading new Robinhood Chain tokens. ## What a rug pull is A rug pull is when the people behind a token take the value out and leave buyers with tokens they cannot sell at a fair price. The common forms: * **Liquidity pulled**: the pool is emptied, and the price collapses. * **Honeypot**: you can buy, but selling fails or is blocked. * **Heavy sell tax**: selling works, but most of the value is taken on the way out. * **Fake ticker**: a new token copies the name of a known one. ## Before you buy: six checks 1. **The address.** Take the contract address from the project's own channels, never from a ticker search alone. 2. **Liquidity.** Thin liquidity moves fast in both directions. Check whether the liquidity is locked or burned, and for how long. 3. **Holders.** A few wallets holding most of the supply can sell into you. 4. **Can you sell?** A token you cannot sell is worth nothing to you. Start with a small buy and a small sell. 5. **Socials.** The website and social accounts should link back to the same contract address. 6. **The name.** Several tokens can share a ticker. The first one is not always the real one, and the real one is not always the first. ## Use the tools * **TRNCH Analytics**, in [Tools](https://trnch.fun/tools), explains what it found on any token, without a wallet. * On the [Heat](https://trnch.fun/heat), tokens set aside show in the **Flagged** tab with a public risk category, and tokens whose liquidity was pulled show in **Rugged**. * No tool catches everything. Treat every new token as high risk. ## Protect your wallet * Approve the exact amount you trade. TRNCH always asks for the exact amount, never an unlimited allowance. * Remove old approvals with **Revoke**, in [Tools](https://trnch.fun/tools). * Never share your recovery phrase. TRNCH will never ask for it, and nobody legitimate will. * Be wary of private messages offering help, airdrops or early access. ## Fake TRNCH tokens TRNCH has no token. Any token using the TRNCH name is not ours, and TRNCH shows it with a **Not a TRNCH token** notice. Official news only comes from trnch.fun, [@trnchfun](https://x.com/trnchfun) and [Telegram](https://t.me/trnchfun). ## If something goes wrong 1. Revoke the approvals you gave to the token or the contract involved. 2. Move what is left to a fresh wallet if you think your wallet is exposed. 3. Report the token or the link to . --- # 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.trnch.fun/guides/how-to-avoid-rugs-on-robinhood-chain.md?ask=&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.