Token security checks
The “Security and risks” block shows contract capabilities and observations from the automated GoPlus and RugCheck scanners. Each check applies to one address on one network. A green check mark confirms only that check’s result, not the safety of the token as a whole.
Where the data comes from
Holder retrieves a scanner report, matches its address to the requested address, normalizes the data into consistent states and stores the result. This module does not perform an independent code audit, verify data through a Holder blockchain node or execute a test purchase and sale.
Supported networks are Ethereum, BNB Chain, Base, Polygon, Arbitrum, Optimism and Avalanche C-Chain through GoPlus; Solana primarily through RugCheck. GoPlus for Solana is a fallback when RugCheck cannot supply a usable report for an address. Rate limits or a general service outage alone do not trigger that fallback.
Addresses come from CoinGecko’s network data. Matching tickers or logos are not enough. A token on several networks is checked separately; a result for one contract does not apply to another. A provider logo means its report is available, not that two providers independently checked every row. Sources and dates are available in the expanded check and “About the data”.
Reading the colors and labels
| Display | Meaning |
|---|---|
| Green check mark | The scanner explicitly reported that a specific capability or feature is absent, such as no mint authority. This is not an overall endorsement of the token. |
| Orange exclamation mark | The scanner detected a capability or feature. An administrative permission does not prove that it has been abused. |
| No data | The source did not provide a usable answer. Unknown is neither an absent risk nor a detected risk. |
| Sources disagree | The selected evidence contradicts itself across providers. Holder does not choose the more favorable answer. |
| Previously: … | A known but outdated observation remains available. Its neutral presentation does not confirm the current state. |
“Other checks” includes additional rows, including unknown results. “Detected: N” counts positive flags among them, including retained historical values. It is not a count of attacks or a numerical risk score.
Ethereum and other EVM network checks
These seven checks come from GoPlus. The table explains a detected feature.
| Check | What is detected and how to interpret it |
|---|---|
| Minting | The ability to issue additional tokens. The check does not measure how many tokens have already been issued. |
| Transfer pause | A mechanism for suspending operations. Transfers are not necessarily paused now; some addresses may be exempt. |
| Selling restriction | GoPlus flagged selling restrictions as a honeypot. Holder does not execute its own test trade. “Not detected” does not guarantee a sale from every wallet or through every route. |
| Proxy contract | A proxy architecture. This flag alone does not establish who can upgrade the implementation or under what conditions. |
| Blacklist | A mechanism for restricting addresses. This does not mean the token is on a scam list or that your wallet is blocked. |
| Whitelist | A mechanism for giving approved addresses special treatment. List membership and your wallet’s permissions are not checked here. |
| Balance changes | The ability to change holders’ balances administratively. A permission does not prove that any balance has been changed. |
Solana checks
RugCheck supplies three primary checks: minting, freezing and metadata. A fallback GoPlus report can contain up to ten checks, so different tokens may have different sets of rows.
| Check | What is detected and how to interpret it |
|---|---|
| Minting | Authority to issue additional tokens remains available. |
| Freezing | Authority to freeze token accounts remains available. This does not establish that any account has actually been frozen. |
| Metadata | The token’s on-chain metadata can be changed. “Immutable” does not guarantee that an image or JSON file at an external URI cannot change. |
| Balance changes | The source reports authority to change users’ balances. |
| Token closure | The source reports a token closure capability; this does not mean the token has already been closed. |
| Non-transferable token | The token is flagged as non-transferable. |
| New accounts frozen | New token accounts are frozen by default. This does not describe the state of all existing accounts. |
| Account state changes | The default state for new accounts can be changed. |
| Transfer fee changes | The transfer fee can be changed. This block does not measure the fee amount. |
| Transfer hook changes | The transfer hook can be changed. Its code is not separately analyzed. |
Liquidity and locked LP
Each result applies only to the named pool. Its address, venue and available measurements are shown. Up to ten pools are listed, with greater known liquidity first. When liquidity is unknown, the first pool is not necessarily the largest.
Holder obtains the locked or burned LP percentage from RugCheck. 100% for one pool does not mean 100% of the token’s total liquidity. Locked and burned LP are not separated; Holder does not independently verify the lock duration or the reliability of the locking service.
For EVM, GoPlus can supply pools and liquidity, but this block does not calculate a locked LP percentage from that response. “No data” is not 0%. Known values of 0% and 100% are provider observations, not guarantees about whether funds can be lost.
Linked wallets
RugCheck may detect groups of addresses linked by transactions. Holder shows the group count, the address count reported by the scanner and the largest group’s supply share when it can be calculated from the report.
A group’s share = its current token holdings / total supply in the same report × 100%. The largest group uses the maximum; if any group’s share cannot be reliably determined, the result remains unknown. This is not a share of the circulating supply in Holder’s catalog.
Transfer links do not prove common ownership. Groups may overlap, so their shares and address counts are not added together. Zero detected groups does not prove that hidden links are absent. An empty general warning list in RugCheck does not override detected groups either.
Updates and disagreements
Reports are collected in the background and visitors see a saved snapshot. “Received by Holder” is when a usable response was received, not a verified time of the scanner’s blockchain analysis: the provider may return cached data.
The planned refresh cycle is roughly every seven days, with requests spread out to manage load. This is not a guaranteed deadline. Evidence is stale once it is at least seven days and six hours old, its next check is due, or the latest update attempt after a successful retrieval failed. A missing or future retrieval date is not treated as fresh either.
When combining sources, known fresh values take priority over old ones. An unknown answer does not count as either yes or no. If no known fresh values exist, a historical result can be shown as “Previously”. Opposing answers in the selected evidence produce “Sources disagree”.
Liquidity and linked wallets are selected separately, each section entirely from one usable report. Fresh evidence is preferred to old evidence; when freshness status is equal, RugCheck takes priority. Pools from different providers are not automatically merged.
Why a block or check may be missing
The block appears for an active token when a usable saved report exists for its current address on a supported network. Network support does not guarantee a scanner response for every address. Data about liquidity or wallet groups alone can produce a block while the primary checks remain unknown.
A native asset without a suitable token contract, an unsupported network, an inactive token or an address without a usable report may have no block. Absence says nothing about safety. Some addresses of a token on several networks may be covered while others are not. A visible block does not mean every check is filled in.
All language versions use the same observations. A link from a project page leads to checks for its associated token and is not an audit of the entire project.
Scope and sources
The block does not assess team integrity, stablecoin backing, issuer solvency, bridge or wallet security, spending approvals, legal status or price prospects. RugCheck’s overall score and general risk list are not used to produce a verdict. There is no overall safety rating here.
Source field descriptions: GoPlus for EVM and GoPlus for Solana. A token’s RugCheck report is available through the source link in its block.
To report an error, use feedback and include the page URL, network, full token address and check name. Distinguish an incorrect address mapping, stale data and a disputed scanner result: correcting one does not confirm the token’s other properties.
