> 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/tools.md). # Tools TRNCH Analytics reads any token on Robinhood Chain and explains its score. Revoke removes the token approvals you no longer need. TRNCH Analytics reads any token on Robinhood Chain and explains its score. Revoke removes the token approvals you no longer need. Stats shows what TRNCH routed. {% hint style="success" %} **Live.** Analytics, Revoke and Stats are available now at [trnch.fun/tools](https://trnch.fun/tools). {% endhint %} Tools has three tabs, **Analytics**, **Revoke** and **Stats**, side by side at the top of the page. On a computer, open Tools from the top bar, after Play. On a phone, open it from **More** in the bottom bar. On [Trade](/trade.md), **Verify on TRNCH Analytics** opens a token's report from the Info panel and from every folded line of Your wallet. The tab and the token you analyze are part of the page address, so a shared link opens the same report. ## TRNCH Analytics Paste a token contract address, or a link that contains one, such as a block explorer link. You don't need to connect a wallet. TRNCH reads the token from the chain, from our own records and from free public sources, then shows one report. * **Score.** A score out of 100, its band ("High risk signals", "Mixed signals" or "Fewer red flags") and how many of the seven core checks it is based on. * **Why this score.** Folded by default: a summary such as "12 checks, 2 warnings" and, on a larger screen, one box per check with its points. **Show all** opens one line per signal: what was looked at, what was found, the source, and the points it takes off. * **Pools and market.** The price (the median of our pools when our relay has one), liquidity, volume, FDV, price changes, buys and sells, whether our routers find a route, our reference pool, and the most liquid pools with their age. * **Holders.** The number of holders, the share of the top 10 wallets (pools and burn addresses left out), the deployer, the developer's share, and the top 10 holders with labels. * **Contract.** Verified code, proxy, creation date, first pool, owner, taxes, and the permissions GoPlus reports. * **Heat signals.** Whether the token is in the race, its Heat, momentum and trust, what lowered its trust, and why it is out when it is. * **Imitations.** A warning when the token copies TRNCH, ETH, WETH or USDG, and the other tokens with the same ticker in our records, each with its own report. * **Socials and sources.** The links the project declares, and whether each source answered. Links open the token on Trade (except an imitation or a token with no pool), in the explorer and in a search on X. A pool opens in the explorer when it has an address. Tools has no links to other trading sites. DexScreener and GeckoTerminal are named as sources, in text only, and a DexScreener or GeckoTerminal page declared by a project is left out of its socials. ### The score * It starts at 100. Each unfavorable signal we can see takes points off, and its line says how many. * Data a source could not give takes nothing off. Its line says "Not checked", and the report says how many core checks the score rests on. * A serious alert from a named source caps the score at 10, and the report names the alert and its source. Examples: the token imitates another one, its sell tax is 50% or more, or its owner can change balances. * With fewer than four of the seven core checks and no serious alert, there is no score at all. * Holder concentration is judged with the same thresholds as the [Heat](/heat.md). {% hint style="warning" %} **The score is never a guarantee.** It sums up public signals. A low score does not prove a scam, and a high one never makes a token safe. Sources can be late or wrong. See the [Risk Disclosure](/legal/risk.md). {% endhint %} ### Sources | Source | What it gives the report | | --------------- | --------------------------------------------------------------------------------------- | | Robinhood Chain | Name, symbol, decimals, supply and the deployer's balance, read from the public RPC. | | TRNCH | Our token records, our reference price and reference pool from the relay, and the Heat. | | GeckoTerminal | Holders, the top 10 share and socials, and the pools when DexScreener has none. | | DexScreener | Every pool of the token, with liquidity, volume, changes and the project's links. | | GoPlus | Taxes, owner permissions, the creator and the top holders, from its free public API. | | Blockscout | Verification, creator, proxy, the top 50 holders and the creation date. | Each source is asked with the token address only. A busy or silent source leaves its part "not checked", and the report says so. A report is kept for up to five minutes, less when it is incomplete. Up to 20 reports a minute can be run from one IP address. ## Revoke An approval lets a contract move a token from your wallet. Approvals you gave elsewhere, or that were never used up, stay open until you remove them. **Revoke** lists the ERC-20 approvals your connected wallet has left open on Robinhood Chain: * the token; * the spender, named when it is a known contract (such as the KyberSwap router, the Uniswap Universal Router, the LI.FI Diamond, 0x AllowanceHolder or Permit2), otherwise "Unknown contract", with a warning when the spender is a wallet and not a contract; * the amount allowed, "Unlimited" when it is; * the date of the last approval. The riskiest come first: approvals to a wallet, then unlimited ones. Tick the approvals you want to remove, or select them all, and press **Revoke selected**. Before anything is sent, TRNCH tells you how many signatures to expect: * **One confirmation for all of them**, when your wallet can group calls. * **One signature per approval, one after the other**, when it cannot. Revoke works with these wallets too. When TRNCH cannot tell in advance, it says your wallet may group them, and it falls back to one signature per approval if it cannot. Each revoke sets the allowance back to zero. You sign every one yourself, and nothing is sent until you confirm it in your wallet. TRNCH also checks that your wallet is connected to the page, on the account you signed in with, before anything is sent. ### The result is read on the chain Once your wallet has sent the revokes, TRNCH reads each allowance again on the chain, not from your wallet's answer or from the explorer, and waits a few seconds for a revoke that is not visible yet. Then it says what happened: * how many approvals were revoked; * a revoke that was reverted on chain, with its token still approved; * revokes that are sent but not confirmed yet, with a hint to refresh in a minute; * or why it stopped: you declined in your wallet, your wallet was on another network or another account, or it could not send the revoke. If you decline a signature, nothing more is sent. The approvals that were revoked are unticked, the others stay ticked so you can try again, and the list is read again. The list comes from the block explorer, which covers your wallet's whole history. When the explorer does not answer, TRNCH reads recent blocks on the chain instead, and the page says from which date approvals are listed. {% hint style="info" %} Approvals given inside Permit2 are not listed one by one. Revoking the approval you gave to Permit2 for a token cuts all of them for that token. Revoke covers Robinhood Chain only. {% endhint %} ## Stats **Stats** shows what TRNCH routed on this chain, counted from on-chain swaps. You don't need to connect a wallet. * **Volume, swaps and traders** over 24 hours, 7 days and 30 days. * **Most traded tokens** over the same windows, each one opening on Trade. * **Latest swaps**, each linking its transaction in the block explorer. * **Heat figures**: how many new tokens entered the race, how quickly the Heat spotted them, and their volume. Every figure is read from our database. Traders are a count, not a list, and addresses are shortened. The page says when its figures were last updated. --- # 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://docs.trnch.fun/tools.md?ask=&goal= ``` `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.