Skip to content
Security7 min readJohn Davis

Avoiding Rug Pulls on Arc Mainnet: A Buyer's Verification Guide

How to spot an Arc rug pull before you buy: ownership and mint authority, tax surface, holder concentration, whether the liquidity is locked or withdrawable.

Most Arc rug pulls are liquidity removals: the deployer creates a pool, buys come in, and the deployer withdraws the USDC side of the pool, leaving a token with no market. Almost every other version — minting supply into the pool, raising sell tax to 100%, blacklisting sellers — is also visible in the contract's state before you buy. The Arc Token Checker reads all of it for free, needs no wallet, and links every finding to the onchain evidence.

This guide is the buyer's side of the checklist: what to look at, what each finding actually means, and what you fundamentally cannot tell from contract state.

The five Arc rug pull mechanics that take money from buyers

Mechanic What it looks like Where to look
Liquidity removal LP tokens sit in a normal wallet; one day the pool is emptied LP token holder address; is it a locker or a wallet?
Mint and dump Owner mints new supply and sells it into the pool owner() plus any mint function and its guard
Tax escalation Buy tax is 5%; sell tax becomes 100% a day later Whether tax setters are owner-guarded and still callable
Honeypot restriction Only some wallets can sell; others revert Blacklist/restriction mappings, pause and transfer guards
Never trading Buys work, sells revert because trading was never enabled for sellers Trading switch state and who can flip it

Four of those five are contract capabilities. Only the first one requires you to look at the market rather than the code — and it is the most common.

The two-minute check

Do these in order. If any of the first three fails, stop reading the chart.

  1. Find the pair and the LP token holder. Every Uniswap V2 pair on Arc has an LP token. Whoever holds it can redeem the reserves. A locker contract with a public unlock timestamp is the good outcome; an ordinary wallet is the bad one.
  2. Read owner(). If it returns a live address, every owner-guarded function is still available to that address. A zero address means the contract is permanently unchangeable.
  3. Check for mint authority. If supply can be increased, your share of the token can be diluted at will, and the new supply can be sold into the pool.
  4. Read the tax surface. Buy tax, sell tax, transfer tax, fee recipients, and whether those values can still change.
  5. Check concentration. What share do the top 10 wallets hold, and how much is the deployer? A contract that cannot be changed can still be dumped by whoever holds 60% of it.

Steps 1 through 4 are exactly what the free checker reports, with links to the reads. Step 5 is what the Arc Token Snapshot tool measures, and it is worth understanding on its own: how concentration metrics are calculated.

Green flags, and what they are worth

Signal What it proves What it does not prove
Ownership renounced Taxes, supply and restrictions are frozen That liquidity is safe, or that holders will not sell
Mint authority removed Your share cannot be diluted That the initial supply was distributed fairly
LP locked with a public timestamp The pool cannot be pulled before that date That it will not be pulled after it
LP burned The pool can never be pulled Anything about the token's value
Pool holds a large share of supply with real USDC depth Selling has to walk down a curve instead of collapsing That the deployer will not sell their own allocation
Trading live, taxes low, no restriction functions Sells work for everyone That demand exists

Read that third column carefully. Every green flag is a statement about a capability, not about intent, and not about price.

Red flags that are not always rugs

Being precise here matters, because false alarms cost real projects.

  • A live owner is normal for a new token. Teams need to configure taxes and limits after launch. What matters is whether the owner eventually renounces, and whether they said they would.
  • Unlocked liquidity in a tiny test pool is usually not a rug. A 300 USDC pool on a token with no community is a test, not a honeypot. The risk scales with how much money is in the pool.
  • A high tax can be legitimate. Rebase, treasury-funded development and buyback mechanics all take fees. The question is whether the fee is disclosed, capped, and changeable by someone you cannot see.
  • Mint authority with a published cap and schedule is a design, not a crime. Read the cap, then decide.
  • A deployer holding tokens is not automatically bad. A team with 15% and a vesting contract is standard. A team with 15% and no plan, in a token whose only product is the chart, is not.

What you cannot see from contract state

This is the honest limit of any checker, including this one.

  • Intent. A contract can be perfectly clean and the deployer can still hold a large allocation and sell it. Nothing onchain distinguishes "committed founder" from "patient seller".
  • Wallet relationships. Fifty wallets that all funded from one exchange withdrawal look like fifty independent holders. Clustering them requires offchain analysis and heuristics, and it can be wrong in both directions.
  • Whether the product is real. No contract read tells you if the roadmap exists.
  • Coordinated social behaviour. Groups that pump a token in a chat are not visible in the bytecode.

A checker moves the question from "is this a scam?" — unanswerable — to "what can this contract do to me, and can I see who holds it?" That second question has a defensible answer, and it eliminates the majority of the ways people lose money on new tokens.

Arc-specific details that matter when you verify

  • Everything is on one public explorerhttps://explorer.arc.io. Contract reads, LP holders and launch transactions are all there, and the chain id is 5042.
  • Finality is sub-second and deterministic. One confirmation is final, so a launch transaction and a liquidity removal cannot be reordered or hidden by a reorg. What you see is what happened.
  • A transaction that never lands is usually a dropped one. Arc enforces a minimum maxFeePerGas of 20 Gwei, and anything below it is silently dropped by the mempool — no error, no receipt. If a deployer claims an action failed, check whether it was ever included at all. Details in Arc's gas and fees reference.
  • There is no onchain randomness. PREVRANDAO returns 0, so any "provably fair" mechanic built on block randomness on Arc is not fair. Mechanisms that need randomness must bring an oracle.
  • SELFDESTRUCT moves a contract's native USDC balance. A contract that self-destructs is not a burn; the funds go somewhere.

If you are already holding a bad token

Be realistic about the options, because most advice on this topic is dishonest:

  • If the contract blocks sells, you cannot force one. No external tool can override a revert. Anyone promising to "unblock" a honeypot is selling you a second loss.
  • If the rug was liquidity removal, the pool is gone. The USDC left with the LP holder. There is no recovery mechanism onchain.
  • If the contract is still open and liquidity remains, exit is your decision — and it is a market decision, not a moral one. Selling into a thin pool moves the price a long way; that is the same slippage arithmetic that protects you when you buy.
  • The one thing worth doing is documenting it. Post the deployer address and the transaction onchain; it is the only contribution that helps the next buyer.

If you are on the launching side of this and want your token to survive the check, the fix is mechanical: revoke ownership after you finish configuring, lock or burn the liquidity, keep concentration defensible, and say all of it in public with transaction hashes.

Run the check

Open the free Arc Token Checker, paste the contract address, and read the findings — ownership and mint authority, tax and restriction surface, holder concentration, and liquidity status. It runs in a browser, needs no wallet, spends nothing, and links every conclusion to the evidence so you can disagree with it and verify for yourself.

Then read the token's market, not just its code. A clean contract with a 90% deployer holding and no liquidity is a rug waiting for a buyer, and no scanner can tell you that part.

Arctools is an independent tool suite for Arc Mainnet, is not affiliated with Circle or the Arc Foundation, and does not provide investment advice.

Covered in this post

Arc rug pullArc rug checkArc Mainnet token scanneris token safe Arc MainnetArc honeypot checkerrug pull scanner ArcArc Mainnet token riskArc token safety check

Read next

Liquidity

Lock Liquidity vs Burn: Which One Actually Protects Buyers

Lock liquidity vs burn: locking keeps a defined exit for you and a verifiable commitment for buyers, burning gives up the LP forever. Which to choose, and when.

Read it
Security

How to Revoke Token Ownership (And Why It Is a One-Way Door)

Revoke token ownership permanently: what renouncing does, which functions stop working, why buyers check it, and when you should not do it. Plus a checklist.

Read it
Distribution

Arc Token Snapshot Guide: Holders at Any Block, Exported to CSV

An Arc token snapshot freezes holder balances at a block you choose and exports a CSV. Here is how snapshots work, what they cost and where they go wrong.

Read it