How to Send USDC on the Base Network

What a USDC send actually is

USDC on Base is an ERC-20 token. Your balance is an entry in the token contract's storage, not something held in your account directly. Sending USDC means submitting a transaction to the USDC contract that calls transfer(recipient, amount). The contract debits you, credits the recipient, and emits a Transfer event.

Two consequences follow. First, the transaction is paid for in ETH, Base's gas asset, because you are the one submitting it. Second, the token you are moving is defined by its contract address. Circle's native USDC on Base is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913. An older bridged token, USDbC, has a different contract, and anyone can deploy a token called USDC.

Sending from a wallet

1. Select Base. In the wallet's network menu, choose Base mainnet (chain ID 8453). Many wallets include it by default; if not, add it from Base's official documentation.
2. Pick the right USDC. Open the token and check its contract address matches the one above. If the wallet shows two USDC-like balances, one may be USDbC.
3. Check gas. Hold a small amount of ETH on Base. Without it the send fails before broadcasting, unless your wallet sponsors gas or lets you pay fees in USDC.
4. Paste the recipient. Copy the address from the source of truth (the recipient's own wallet, an exchange's Base deposit screen), not from your transaction history. Compare the full string.
5. Send a test amount first to any new address, especially an exchange. Confirm it arrives, then send the rest.
6. Confirm and record the transaction hash.

If the recipient is an exchange, confirm it lists Base as a supported deposit network for USDC. Sending on Base to an exchange that only watches Ethereum for that address can mean a slow support recovery or none.

Sending programmatically

In code, the same transfer is one contract call. This example uses viem; ethers and other libraries are equivalent.

import { createWalletClient, createPublicClient, http, parseUnits, erc20Abi } from "viem";
import { base } from "viem/chains";
import { privateKeyToAccount } from "viem/accounts";

const USDC = "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913"; // native USDC on Base
const account = privateKeyToAccount(process.env.SENDER_KEY as `0x${string}`);
const wallet = createWalletClient({ account, chain: base, transport: http() });
const reader = createPublicClient({ chain: base, transport: http() });

const hash = await wallet.writeContract({
  address: USDC,
  abi: erc20Abi,
  functionName: "transfer",
  args: [recipient, parseUnits("5", 6)], // 5 USDC, 6 decimals
});
const receipt = await reader.waitForTransactionReceipt({ hash });
if (receipt.status !== "success") throw new Error("transfer reverted");

Points that matter more than the syntax:

Decimals. USDC has 6 decimals. parseUnits("5", 6) is five dollars. Using 18 decimals, as for ETH, asks for a trillion times more and reverts on balance. The reverse mistake, passing an unscaled 5, sends five millionths of a dollar and succeeds silently.

Receipt status. A transaction hash means submitted, not succeeded. Wait for the receipt and check status. For accounting, also decode the Transfer event to confirm amount and recipient.

Nonces and retries. If you retry after a timeout, check whether the first transaction landed before sending again, or you will pay twice. Track sends by an idempotency key in your own system.

Keys. The example reads a private key from the environment because it is a script. Do not run an agent this way.

Mistakes that strand or lose funds

Wrong network. The recipient address is identical on every EVM chain, so a send on Ethereum or another network succeeds and lands there instead. Recoverability depends on who controls that address on that chain.

Sending to the token contract. Pasting the USDC contract address as the recipient usually locks the funds permanently.

USDbC instead of USDC. Some recipients only credit native USDC. Swap first if needed.

Poisoned addresses. Lookalike addresses planted in history match the first and last characters. Copy from the recipient, not from history.

No ETH for gas. The send cannot be submitted. Fund ETH on Base or use a wallet that sponsors gas.

Agent with a raw key. An agent sending USDC should use a session key scoped by cap, asset, recipients, and expiry, so a manipulated agent cannot send everything to anyone. CryptoCadet's rail works this way: a non-custodial, session-key-bounded USDC float on Base, with the key held in the OS keychain.