A user opens their Rabby Wallet to find a new token in their portfolio, flagged as “unverified” with a warning icon. The token arrived from a DeFi protocol interaction, a bridge swap, or an airdrop. The natural question is immediate: is this a scam, a rug pull waiting to happen, or a legitimate new project that simply hasn’t yet been added to established token lists? Rabby doesn’t make that determination for you. Its security interface instead shows the flag and explains why, leaving the actual investigation to the wallet holder.

This transparency reflects a fundamental design choice in self-custodial wallets. Rabby cannot prevent you from holding any EVM token that exists on-chain, nor can it verify the legitimacy of every new contract. Instead, it provides the tools to research tokens yourself: contract source code review, on-chain transaction history, holder distribution, and integration with auditing services. Understanding how Rabby’s verification system works—and what it doesn’t do—is essential for distinguishing between a genuine nascent project and a scam that relies on users making quick, uninformed decisions.

Token verification interface in a self-custodial wallet showing unverified token warnings and contract details

How Rabby determines token verification status

Rabby’s verification system relies on established token lists and contract registries rather than its own internal approval process. A token is considered “verified” if it appears on widely recognized lists such as the Ethereum token list, chain-specific official lists (like Arbitrum’s list or Optimism’s list), or integrated data from services like CoinGecko and DefiLlama. These lists operate independently of Rabby and are maintained by their respective communities or data providers. A token that does not appear on any recognized list receives the “unverified” flag in Rabby’s interface.

This approach scales across multiple EVM networks. Since Rabby supports Arbitrum, Optimism, Base, Polygon, BNB Smart Chain, Avalanche, and many other EVM-compatible blockchains, each network may have its own token lists and verification standards. An ERC-20 token on Ethereum may be fully verified, while the same token’s wrapped version on an alternative chain might not yet be added to that chain’s official lists. The distinction matters because token lists exist partly to reduce user confusion and partly to filter out obvious scams, but they are not comprehensive guarantees of security.

Rabby also displays risk warnings based on contract characteristics rather than manual review. These warnings flag contracts with specific red flags: contracts that can arbitrarily increase supply, contracts missing standard audit trails, contracts with concentrated ownership, or contracts that have been flagged by services such as OpenZeppelin’s contract analysis. The presence of a risk warning does not necessarily mean the token is a scam; some legitimate projects are built with minimal governance or intentionally non-upgradeable contracts that lack certain features. The warning is meant to prompt investigation, not to condemn.

The critical gap is this: Rabby cannot assess intent or token economics. A contract can be technically sound, execute exactly as written, and still be economically designed to extract value from retail participants. A contract can also be genuinely experimental—built by a small team with novel mechanisms that auditors haven’t yet reviewed. The verification status alone does not distinguish between these cases.

Why new projects appear unverified when they launch

Legitimate projects often launch with unverified tokens because the process of getting on established lists requires time and can involve fees, community votes, or simply waiting for curators to review and add new contracts. A genuine project might deploy a contract today, announce it on social media tomorrow, and not appear on major token lists for weeks. During that period, every holder in Rabby sees “unverified” displayed prominently.

The timeline is important for distinguishing patterns. A token that has been unverified for six months despite billions in trading volume across exchanges is likely a scam that deliberately avoids listing processes. A token that launched three days ago, has small transaction volume, and shows active development communication is more consistent with a genuine new project. Neither status proves anything, but the history provides context.

New EVM projects also proliferate on secondary networks where token standards are newer and lists are less mature. A Base network token or Arbitrum token launched yesterday may legitimately not appear on that chain’s lists because Base’s own verification infrastructure is still growing relative to Ethereum’s decade-old ecosystem. The same token deployed on Ethereum would face higher scrutiny and faster potential listing once it meets basic standards. Conversely, scammers specifically target newer networks hoping that less mature infrastructure means less oversight.

Another common scenario involves tokens created through legitimate protocols that automatically generate new assets. Some DeFi protocols, for instance, allow users to mint new tokens against collateral or create governance tokens programmatically. The resulting contract is real and auditable, but it did not exist until moments before, so no list curator could have pre-approved it. A user interacting with a legitimate protocol might suddenly hold an unverified token not through scam but through protocol mechanics.

Red flags that typically indicate scams versus legitimate experimentation

Scam tokens exhibit consistent behavioral patterns that can be identified through on-chain research. The most obvious is a honeypot contract, a token designed to allow users to buy but block or severely restrict selling. On-chain inspection using contract explorers and analysis tools can reveal this by checking the token’s transfer function. If the contract code includes logic like “if sender is not owner, revert on sell,” or if the actual contract is proxy-upgraded to prevent sells, the token is deliberately trapping money. A self-custodial wallet like Rabby cannot prevent you from purchasing such a token, but you can identify the trap before sending money if you review the contract source code first.

Supply manipulation is another hallmark of scams. A scam token might have 1 billion total supply shown on block explorers, but the contract includes a hidden function (such as `mint` callable only by the deployer) that can increase supply without limit. This is rarer now because major auditors check for it, but it remains possible. Check the contract’s total supply against its actual minting logic on the explorer, and verify that any supply-increase functions are actually restricted to appropriate roles.

Extreme centralization is a risk, though not always a scam. If one address holds 90% of a token’s supply and that address is a known team wallet moving tokens to exchange liquidity pools, that is normal early-project behavior. If one address holds 90% and has been holding it untouched for weeks while the token trades, that is consistent with a pre-minted scam waiting for price appreciation before a dump. The distinction requires looking at both the holder distribution and the transaction history of large holders.

Legitimate new projects often exhibit uncertainty rather than deception. The contract might be unaudited not because it is hidden but because the team is small and audits are expensive. The token supply might concentrate in one address because the project just launched and hasn’t yet distributed it. The team might be anonymous not because they are scammers but because they want to focus on the product rather than personal branding. These are risks, certainly, but they are different from the deliberate entrapment and deception that characterize scams.

Using block explorers and contract analysis to research unverified tokens

The most practical research begins with the contract address itself. Copy the token address from Rabby and paste it into Etherscan (for Ethereum), Arbiscan (for Arbitrum), Basescan (for Base), or the equivalent block explorer for your network. This shows the contract creation transaction, deployment date, transaction count, and basic holder information. A token created five minutes ago with no transactions except the initial mint is either brand new or abandoned. A token created two years ago with millions of transactions has history you can examine.

On the contract’s details page, locate the “Contract” tab and verify that the source code is verified. Verified means the contract code is publicly readable and matches what is running on-chain. If source code is not verified, you cannot reliably inspect the token’s mechanisms without using a bytecode decompiler, which is technical and error-prone. A scammer often deliberately unverifies or obscures the code. A legitimate project usually verifies because doing so builds trust and most deployment tools now verify automatically.

Read the token’s transfer function and any special mechanisms. Standard ERC-20 tokens have straightforward transfer logic: take tokens from sender, reduce sender balance, increase recipient balance, emit event. If the contract includes extra logic—fees, burns, access controls on transfers, or external calls to other contracts during transfer—investigate what each does. Tools such as Dedaub or ChatGPT (feeding it the contract code) can help decode uncommented bytecode, though the accuracy depends on complexity.

Check the holder distribution using the explorer’s “Holders” or “Token Holders” tab. Legitimate projects typically show a relatively distributed holder base once enough time passes. Very new projects may show concentration in the deployer’s address, which is normal. Very old projects with extreme concentration, especially if large holders match known scam addresses or exchange deposit addresses controlled by scammers, are warning signals. Also identify whether holders are smart contracts (like DeFi protocols) or externally-owned accounts; smart contract holders suggest the token is integrated into real applications.

Finally, search for independent audits. Visit the token’s website or GitHub (if it has one), and check whether audits from firms like OpenZeppelin, Trail of Bits, or Certora are linked. Audits are not guarantees—auditors can miss issues, and a token can be audited and still be economically designed to scam—but an audit history suggests the team has invested in legitimacy. An unaudited token is not necessarily a scam, but it is higher risk because you have less third-party verification.

Using Rabby’s security interface to interpret warnings and risk flags

When you interact with an unverified token or a token flagged with warnings in Rabby, the wallet displays specific information before you approve the action. The security interface shows the contract address, the network, the token symbol and decimals, and any risk flags detected by the contract analysis systems Rabby integrates. The goal is to make you pause and verify before committing.

A common warning is “high-risk contract” or “unaudited contract.” This does not mean the contract is a scam; it means no audit firm has formally reviewed it or it exhibits characteristics common to scams (like a mint function, or unusual transfer logic). A token with a high-risk flag can still be legitimate, especially if it was only deployed days ago or if it uses experimental mechanisms that auditors haven’t yet seen.

Rabby also shows “contract is still being watched” or similar messages if the contract has been flagged by community detection tools. Scamsniffer, Aegis, and other security services maintain databases of detected rug pulls and scams. If a contract appears in these databases, Rabby will typically alert you. However, these databases are reactive—they detect scams after they happen, not before. A newly deployed scam will not yet appear in any database, which is why they succeed temporarily.

The human-readable transaction details feature in Rabby is particularly useful here. When you approve an interaction, Rabby attempts to decode and explain what the transaction will do in plain language. Instead of seeing raw contract function calls, you see “Send 1000 TOKEN to 0x1234…” or “Approve unlimited tokens to DEX contract.” This helps catch scams that use social engineering: you might approve what appears to be a simple token transfer but is actually granting infinite allowance to an untrusted address. Review these details carefully before signing.

Distinguishing between nascent projects and exit scams through transaction patterns

The key difference between a legitimate new project and a planned exit scam often emerges in transaction patterns and timing. A genuine project shows sustained development activity: regular additions to liquidity pools, integration with DeFi protocols, participation in governance, or accumulation of real trading volume from independent users. These activities leave transaction trails that auditors and community members can verify.

An exit scam, by contrast, follows a recognizable sequence. The scammer deploys the contract, mints a large supply in one or a few addresses, deploys liquidity pools with their own capital, promotes the token on social media and community channels, and then, once retail money has flowed in, empties the liquidity pools and transfers the proceeds to a new address. The time from deployment to exit can be weeks or months if the scammer is patient, but it can also be days if volume builds quickly. On-chain, this shows up as a sudden liquidation event: large outflows from liquidity pools, price collapse, and zero remaining incentive for liquidity providers to hold.

Legitimate projects can also experience price collapse and poor performance, but for different reasons. A token might drop because the market doesn’t believe in the project’s mechanics, the team loses interest, or a competitive project launches. The economic failure is real, but it was not designed as a trap. The holder base gradually sells at declining prices; no single liquidation event occurs. The team address may retain tokens because they believe the project still has value, not because they are waiting for a buyer to appear.

For an unverified token you are considering using, check the transaction history of any “team” addresses mentioned in the project’s documentation. If those addresses have withdrawn coins to exchanges at regular intervals, especially when price is rising, that is consistent with scammers cashing out. If they have been reinvesting or transferring to protocols, that suggests genuine commitment. Neither guarantees the project will succeed, but intention can be partially inferred from action.

Why Rabby cannot and should not attempt to pre-approve all tokens

The design of Rabby as a non-custodial wallet means it does not control which tokens you can hold or receive. Your assets remain on the blockchain; Rabby is merely the interface you use to interact with them. Because anyone can deploy an ERC-20 token to Ethereum or any EVM chain, there is no practical way to pre-approve every legitimate token and reject every scam before the user sees it. Attempting to do so would require centralized gatekeeping, which would contradict the open nature of blockchain technology and concentrate control in Rabby’s hands.

Instead, Rabby provides information and defaults to user responsibility. You can obtain the Rabby Wallet download and gain access to a self-custodial security wallet built to show you what you are doing and why, rather than hiding complexity behind approvals. The wallet can warn you, explain the risk, and suggest verification steps, but it cannot prevent you from making decisions you have researched and chosen.

This is intentional. If Rabby had a pre-approved list of “safe” tokens and showed a green checkmark only for those, it would be making editorial decisions about which projects deserve to exist. That would necessarily exclude legitimate projects that haven’t yet gotten approval, and it would create a centralized point of failure. If Rabby’s approval process was compromised or corrupted, attackers could get scam tokens approved or hide legitimate tokens. A decentralized system instead pushes verification responsibility to the user, which is harder but more robust.

The trade-off is real. Users must invest time in research rather than trusting Rabby’s judgment. But this trade-off exists for all self-custodial tools; it is not a flaw of Rabby specifically but a feature of truly open blockchains. The more verification you do yourself, the less likely you are to be caught by a scam. The more you rely on any single gatekeeper, the more you are exposed to that gatekeeper’s failure or compromise.

A practical checklist for evaluating unverified tokens before using them

Before you add an unverified token to your portfolio or approve an interaction involving it, use this sequence. First, confirm the token’s address. Copy the address directly from Rabby’s token details rather than trusting any URL or social media link. Phishing often works by redirecting you to a fake address that looks similar. Cross-reference the address on the official project website or verified social media channels.

Second, check the contract source code on the appropriate block explorer. If the code is not verified, stop and decide whether you trust the unverified token enough to risk money on it. If code is verified, read the transfer function and any custom mechanisms. Flag any unusual behaviors and research their purpose. If you cannot understand the code, ask an experienced user or avoid the token until you can verify it independently.

Third, examine the holder distribution and transaction history. Look for concentration in one address, large recent transfers to exchanges, or liquidation events. Check whether the project team’s stated addresses match what you see on-chain. If the project claims team tokens are locked, verify the lock using the explorer’s notes on the locking contract.

Fourth, search for audits. If the project links audits, read the audit report’s summary. If no audits exist, accept that you are taking additional risk. If negative findings are mentioned in the audit, understand what they mean before proceeding.

Fifth, evaluate the project’s maturity and integration. A token that has been running for six months with activity on multiple DeFi protocols is lower risk than a token deployed yesterday by an anonymous account. Community size, GitHub activity, and partnerships can be assessed via the project’s website and social channels.

Finally, size your exposure appropriately. Even after research, unverified tokens are higher risk. Commit only money you can afford to lose entirely, and never bet your entire portfolio on unverified projects, no matter how legitimate they appear.

Frequently asked questions

What does “unverified” mean in Rabby Wallet, and is every unverified token a scam?

Unverified means the token does not appear on established token lists like the Ethereum token list or chain-specific registries that Rabby uses for verification. It does not mean the token is a scam; many legitimate new projects are unverified for weeks after launch. However, most scam tokens are also unverified, so the flag should prompt independent research before you hold or interact with the token.

How can I check if an unverified token is a honeypot or scam on the blockchain?

Use the token’s block explorer (Etherscan for Ethereum, Arbiscan for Arbitrum, etc.) to view the contract source code. Verify the code is published, then check the transfer function for restrictions that block sells. Look at the holder distribution to identify extreme concentration, and examine transaction history for sudden liquidity pool drains. Tools like Dedaub can decompile unverified contracts, though accuracy depends on complexity.

Why doesn’t Rabby just pre-approve all legitimate tokens to protect users?

Rabby is a self-custodial wallet with no control over which tokens exist on blockchains. Anyone can deploy any ERC-20 token, so pre-approval at scale is impossible without Rabby becoming a gatekeeper and centralized authority. Instead, Rabby shows warnings and integrates risk analysis to help you research before you decide. This approach preserves the open nature of blockchains while putting verification responsibility on you.

Leave a Reply

Your email address will not be published. Required fields are marked *