Why the Same Token Shows Up Twice on Arbitrum

Open a wallet on Arbitrum One and there is a decent chance you are holding two things called USDC. One says USDC. One says USDC.e. Both are worth a dollar, both were sent to you by something legitimate, and neither is a scam. They are different tokens, at different contract addresses, and no amount of staring at the ticker will tell you which is which.

This is not a bug in your wallet. It is the direct consequence of how assets get onto a rollup, and it is the thing that most often makes an Arbitrum portfolio harder to read than an Ethereum one.

What actually happens when a token is bridged?

Nothing moves. That is the part worth internalising, because every duplicate token on every rollup follows from it.

The canonical bridge works by locking. Send USDC to Arbitrum's gateway on Ethereum and the mainnet USDC contract still holds your balance, now credited to the gateway. The bridge then mints a matching amount of a new ERC-20 contract deployed on Arbitrum, one the bridge itself controls. That contract is a different token at a different address, and its only claim to be USDC is that the gateway is holding real USDC against it.

Bridged USDC on Arbitrum One lives at 0xff970a61a04b1ca14834a43f5de4533ebddb5cc8 and was eventually renamed USDC.e to distinguish it from what came next. In 2023 Circle deployed native USDC directly on Arbitrum at 0xaf88d065e77c8cC2239327C5EDb3A432268e5831, issued and redeemed by Circle without a bridge in the middle, and that is now the version exchanges credit and Circle honours one-for-one for dollars.

So the chain carries both, permanently, and so does your wallet. Which one you received depends entirely on which protocol paid you and when. The same story repeats for WETH, WBTC and most of the long tail: the Arbitrum address bears no relation to the Ethereum one, because it was created by a bridge rather than by the original issuer.

For tracking, this cuts in two directions. A tracker that maps both contracts to "USDC" gives you a clean total and hides a distinction you might care about. A tracker that shows them separately is more honest and looks like a bookkeeping error. Worse is the third case: an app that recognises one contract and not the other, prices the recognised one and leaves the other as an unpriced row, and reports a total that is short by exactly the amount of a stablecoin you definitely own. If two apps disagree here, the cause is contract coverage rather than a price source difference.

The habit that fixes it permanently is to verify by contract address on Arbiscan rather than by name, once, for each token you hold more than dust of. A ticker is a string anyone can set. An address is the token.

Am I even looking at the right Arbitrum?

There are two chains, and the address is the same on both.

Arbitrum One, chain ID 42161, is the general-purpose rollup that posts its data to Ethereum and holds effectively all of the value. Arbitrum Nova, chain ID 42170, posts data through a committee instead, which makes fees lower and the security assumption different. Nova was where a set of gaming and social applications ran, and people who used them in 2022 and 2023 hold balances there that they have entirely forgotten about.

A tracker querying Arbitrum One will never see them. Neither will a wallet whose network list contains only One. The holdings are not lost, they are on a chain nobody thought to check, which is the same category of error as an unwatched sub-account on an exchange. Explorer support has shifted too: Nova Arbiscan stopped being supported on 31 January 2026, and Blockscout is now where you look.

The wider version of this problem is worse than two chains. Arbitrum's stack is used to launch application-specific chains, and each one reproduces your address again. Tracking one identity across many chains is the discipline that keeps this manageable: maintain a list of the networks you have actually transacted on, not the ones you meant to.

Two more things that catch people out. Gas is ETH, not ARB, so a wallet full of governance tokens and no ether cannot transact. And a canonical withdrawal to Ethereum sits inside a seven-day challenge window, during which the funds have left Arbitrum and have not arrived on mainnet, and no balance query anywhere will show them. That is the same shape of gap that appears on Base and other optimistic rollups, and it is the most alarming normal thing in rollup usage.

What did the airdrop tell everyone about me?

Arbitrum's privacy story has a specific wrinkle that most chains lack.

The ARB distribution in March 2023 was allocated by on-chain behaviour, and qualifying meant your address had a scored, published history. That produced a large, well-organised body of public analysis about which addresses were active, which were funded from the same source, and which were probably one person running many wallets. Sybil hunting was the explicit point of the exercise, and the clustering work it produced did not evaporate afterwards.

The general truth still applies: an address is public, permanent and readable by anyone, and the wallet privacy trade-off covers the shape of that. The Arbitrum-specific addition is that farming an airdrop across multiple addresses is the fastest way to link them all to each other, because the funding pattern that qualifies you is the same pattern that identifies you. If you ran ten wallets to maximise a claim, assume they are known to be yours.

Spam behaves like Ethereum's here, priced off thin pools and shaped to be swapped. Filter it before you reconcile anything or the token list is unreadable. Spam and dust filtering covers the thresholds.

How do I get to a token list I can trust?

1. List the chains you have used. Arbitrum One, Nova, and any application chain you touched. Query each one.
2. Verify your top holdings by contract address, not by ticker, on Arbiscan or Blockscout. Save the addresses somewhere.
3. Consolidate the duplicates you do not want. Swapping USDC.e for native USDC costs a few cents and removes a permanent source of ambiguity from every future reconciliation.
4. Hide the unrecognised sub-dollar rows before comparing totals, or they will drown the comparison.
5. Account for anything in transit. A seven-day withdrawal is not a discrepancy, and neither is a bridge deposit you submitted an hour ago. Why your portfolio balance is wrong lists the causes that are.

The useful outcome is not a tidier screen. It is that the next time a stablecoin balance looks wrong by a suspiciously round amount, your first thought is which contract rather than which app, and you will be right about it most of the time.