Confirm chain ID 42161, distinguish Circle-listed native USDC from bridged USDC.e, reserve ETH on Arbitrum, and verify the payout token.
The source and fresh payout wallet both use Arbitrum One and the live order accepts the exact USDC variant held.
The token is on Ethereum, Base, Solana, or an unsupported bridged form. A bridge should solve a real destination need, not compensate for an unchecked token.
USDC mixer guide covers mixing mechanics, timing, and retention criteria without repeating them here.
Native USDC and bridged USDC.e can coexist in wallets and interfaces. The safe route verifies the full contract, chain ID 42161, ETH on Arbitrum for gas, and the exact asset accepted by the current order.
Circle lists 0xaf88d065e77c8cC2239327C5EDb3A432268e5831 for native USDC on Arbitrum.
The older bridged form has a different contract and history. Confirm what the live route accepts.
The source wallet needs ETH on Arbitrum for gas, not only an ETH balance on mainnet.
The destination wallet must support the selected Arbitrum token and network.
Confirm Arbitrum One at the source.
Distinguish native USDC from USDC.e in the wallet and current order.
Keep enough ETH on the L2 to submit the deposit.
Use a fresh Arbitrum wallet and verify the expected token before sending.
Arbitrum can lower transaction cost, but only a contract-level token check confirms that the route accepts what the wallet actually holds.
Official sources support network and token facts. The partner interface supports only what was visible during the dated review. Provider retention statements remain claims, not proof of backend deletion, liquidity, or a final privacy outcome.
No. They use different contracts and represent different issuance or bridge histories. Match the exact contract accepted by the live route.
Match the contract, chain ID 42161, Arbitrum ETH balance, and payout token before reviewing the current order.