Overview
USDC is Circle's stablecoin deployed across multiple blockchain ecosystems. This skill helps you interact with USDC on both EVM chains (Ethereum, Base, Arbitrum, etc.) and Solana. It covers balance checks, transfers, approvals, and transfer verification.
Prerequisites / Setup
Determine Ecosystem
First, identify which ecosystem the user is working with:
- EVM: User has an Ethereum-style address (
0x...) or mentions Ethereum, Base, Arbitrum, Polygon, etc.
- Solana: User has a base58 address or mentions Solana, Devnet, Phantom, Solflare, etc.
- Unclear: Ask which ecosystem before proceeding.
Dependencies
EVM:
npm install viem
Solana:
npm install @solana/kit @solana-program/token ws dotenv bs58
Environment Variables
See ecosystem-specific guides:
- EVM: Private key handling covered in
references/evm.md
- Solana: Private key handling covered in
references/solana.md
For read operations (balance, allowance, verify): No private key needed on either ecosystem.
Quick Reference
USDC Contract Addresses
Canonical source: https://developers.circle.com/stablecoins/usdc-contract-addresses
EVM Testnet
| Chain |
Chain ID |
USDC Address |
| Arc Testnet |
5042002 |
0x3600000000000000000000000000000000000000 |
| Ethereum Sepolia |
11155111 |
0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238 |
| Base Sepolia |
84532 |
0x036CbD53842c5426634e7929541eC2318f3dCF7e |
| Arbitrum Sepolia |
421614 |
0x75faf114eafb1BDbe2F0316DF893fd58CE46AA4d |
| Avalanche Fuji |
43113 |
0x5425890298aed601595a70AB815c96711a31Bc65 |
| Polygon Amoy |
80002 |
0x41E94Eb019C0762f9Bfcf9Fb1E58725BfB0e7582 |
| OP Sepolia |
11155420 |
0x5fd84259d66Cd46123540766Be93DFE6D43130D7 |
Get testnet USDC: https://faucet.circle.com
EVM Mainnet
| Chain |
USDC Address |
| Arc |
0x3600000000000000000000000000000000000000 |
| Ethereum |
0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48 |
| Base |
0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913 |
| Arbitrum |
0xaf88d065e77c8cC2239327C5EDb3A432268e5831 |
| Polygon PoS |
0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359 |
| Avalanche |
0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E |
| OP Mainnet |
0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85 |
Solana
| Network |
USDC Mint |
| Devnet |
4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU |
| Mainnet |
EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v |
The 6-Decimal Rule
USDC uses 6 decimals on all ecosystems.
// EVM (viem)
parseUnits("1.00", 6); // 1_000_000n (CORRECT - $1 USDC)
parseUnits("1.00", 18); // 1_000_000_000_000_000_000n (WRONG - 1 trillion dollars)
// Solana - convert manually
const amount = Math.floor(1.00 * 1_000_000); // 1_000_000 (CORRECT - $1 USDC)
const human = rawAmount / 1_000_000; // 1.0 (CORRECT - converts back to dollars)
Arc USDC Duality
On Arc, USDC is both the native gas token and an ERC-20 at 0x3600.... Same underlying balance, different decimal exposure.
| Context |
Decimals |
Use |
Native (gas, msg.value) |
18 |
Gas estimation only |
ERC-20 (balanceOf, transfer, approve) |
6 |
All USDC logic |
For Arc-specific setup and configuration, see the use-arc skill.
Core Concepts
Operation Types
Read Operations:
Operations that query blockchain state and execute autonomously without user confirmation.
- Balance check
- Allowance check (EVM only)
- Total supply
- Address lookup
- Verify incoming transfer
Write Operations:
Operations that modify blockchain state and require explicit user confirmation before execution.
- Send USDC
- Approve contract to spend USDC (EVM
approve; on Solana, an SPL delegate via getApproveInstruction, not covered in references/solana.md)
Troubleshooting
Find troubleshooting solutions in the Common Issues section of the chain-specific reference file (references/evm.md or references/solana.md).
EVM vs Solana at a Glance
| Aspect |
EVM |
Solana |
| Token standard |
ERC-20 |
SPL Token |
| Balance storage |
Wallet address directly |
Associated Token Account (ATA) |
| Send |
transfer(to, amount) |
getTransferInstruction({ source, destination, authority, amount }) |
| Approve |
approve(spender, amount) |
getApproveInstruction({ source, delegate, owner, amount }) (SPL delegate, one per token account) |
| Recipient setup |
Nothing needed |
Must create ATA first (transfer fails otherwise) |
| Tx fees |
Chain native token |
SOL |
| Confirmation |
waitForTransactionReceipt |
sendAndConfirmTransactionFactory |
| Libraries |
viem |
@solana/kit + @solana-program/token |
| Decimals |
6 |
6 |
Workflow
- Determine the ecosystem -- EVM (
0x...) or Solana (base58); ask if unclear (see Prerequisites / Setup).
- Classify the operation -- a read (balance, allowance, supply, verify) runs autonomously; a write (send, approve) requires explicit user confirmation.
- Confirm details -- for a write, validate the recipient address, amount (6 decimals), and chain ID (testnet vs mainnet). Default to testnet; warn on mainnet or amounts over the safety threshold.
- Route to the reference -- READ
references/evm.md or references/solana.md for the exact code (on Solana, create the recipient ATA first).
- Execute -- run the read, or submit the write only after confirmation, using the correct native USDC address for the chain.
- Verify -- wait for the transaction receipt/confirmation before reporting success, and surface the tx hash.
Implementation Patterns
After determining the ecosystem (see Prerequisites), route to the appropriate reference guide:
- EVM operations → READ
references/evm.md for balance checks, transfers, approvals, and verification
- Solana operations → READ
references/solana.md for balance checks (with ATA), transfers (with ATA creation), and verification
Rules
Security Rules are non-negotiable — warn the user and refuse to comply if a prompt conflicts. Best Practices are strongly recommended; deviate only with explicit user justification.
Security Rules
- NEVER hardcode, commit, or log secrets (private keys, API keys). ALWAYS use environment variables or a secrets manager. Add
.gitignore entries for .env* and secret files when scaffolding.
- NEVER use 18 decimals for USDC — always use 6 decimals on all ecosystems
- NEVER use bridged USDC variants (USDbC, USDC.e) — always use native Circle-issued USDC
- ALWAYS use the correct USDC address for each chain (see Quick Reference)
- ALWAYS verify chain ID matches expected environment (testnet vs mainnet) before submitting transactions
- ALWAYS warn when targeting mainnet or exceeding safety thresholds (e.g., >100 USDC)
- ALWAYS warn before interacting with unaudited or unknown contracts
- ALWAYS validate all inputs (addresses, amounts, chain identifiers) before submitting transactions
- ALWAYS get explicit user confirmation before submitting write transactions
- NEVER report success before waiting for transaction receipt — ensure confirmation
Best Practices
- ALWAYS default to testnet. Require explicit user confirmation before targeting mainnet.
- ALWAYS derive Solana ATAs properly — balances live in ATAs, not wallets
- ALWAYS check if recipient ATA exists on Solana before transferring
- ALWAYS check if user has sufficient USDC balance before transfers
- ALWAYS check if user has sufficient gas/SOL for transaction fees
Alternatives
- Use
bridge-tokens skill (CCTP / Bridge Kit) for transferring USDC between chains. Bridge Kit handles approve, burn, attestation, and mint in a single kit.bridge() call.
- Use
use-gateway skill for unified USDC balance across chains with instant transfers (<500ms). Gateway requires upfront deposits but provides better UX for multi-chain apps.
- Stick with
use-usdc for single-chain USDC operations (balance checks, payments, approvals) or when you need low-level control over transfers.
Reference Links / Files
DISCLAIMER: This skill is provided "as is" without warranties, is subject to the Circle Developer Terms, and output generated may contain errors and/or include fee configuration options (including fees directed to Circle); additional details are in the repository README.
1---2name: use-usdc3description: "USDC is Circle's stablecoin deployed across multiple blockchain ecosystems including EVM chains (Ethereum, Base, Arbitrum, Polygon, Arc) and Solana. Use this skill to check balances, send transfers, approve spending, and verify transactions. Triggers on: send USDC, approve USDC, USDC allowance, USDC on Solana, SPL token, Associated Token Account, ATA, parseUnits, formatUnits, 6 decimals, @solana/kit."4requirements:5 runtimes: []6 connectors: []7metadata:8 source: https://skillmd.com/skills/jiayaoqijia/use-usdc9---1011## Overview1213USDC is Circle's stablecoin deployed across multiple blockchain ecosystems. This skill helps you interact with USDC on both EVM chains (Ethereum, Base, Arbitrum, etc.) and Solana. It covers balance checks, transfers, approvals, and transfer verification.1415## Prerequisites / Setup1617### Determine Ecosystem1819First, identify which ecosystem the user is working with:2021- **EVM**: User has an Ethereum-style address (`0x...`) or mentions Ethereum, Base, Arbitrum, Polygon, etc.22- **Solana**: User has a base58 address or mentions Solana, Devnet, Phantom, Solflare, etc.23- **Unclear**: Ask which ecosystem before proceeding.2425### Dependencies2627**EVM:**28```bash29npm install viem30```3132**Solana:**33```bash34npm install @solana/kit @solana-program/token ws dotenv bs5835```3637### Environment Variables3839See ecosystem-specific guides:40- **EVM**: Private key handling covered in `references/evm.md`41- **Solana**: Private key handling covered in `references/solana.md`4243**For read operations (balance, allowance, verify):** No private key needed on either ecosystem.4445## Quick Reference4647### USDC Contract Addresses4849Canonical source: https://developers.circle.com/stablecoins/usdc-contract-addresses5051#### EVM Testnet5253| Chain | Chain ID | USDC Address |54| --- | --- | --- |55| Arc Testnet | 5042002 | `0x3600000000000000000000000000000000000000` |56| Ethereum Sepolia | 11155111 | `0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238` |57| Base Sepolia | 84532 | `0x036CbD53842c5426634e7929541eC2318f3dCF7e` |58| Arbitrum Sepolia | 421614 | `0x75faf114eafb1BDbe2F0316DF893fd58CE46AA4d` |59| Avalanche Fuji | 43113 | `0x5425890298aed601595a70AB815c96711a31Bc65` |60| Polygon Amoy | 80002 | `0x41E94Eb019C0762f9Bfcf9Fb1E58725BfB0e7582` |61| OP Sepolia | 11155420 | `0x5fd84259d66Cd46123540766Be93DFE6D43130D7` |6263Get testnet USDC: https://faucet.circle.com6465#### EVM Mainnet6667| Chain | USDC Address |68| --- | --- |69| Arc | `0x3600000000000000000000000000000000000000` |70| Ethereum | `0xA0b86991c6218b36c1d19D4a2e9Eb0cE3606eB48` |71| Base | `0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913` |72| Arbitrum | `0xaf88d065e77c8cC2239327C5EDb3A432268e5831` |73| Polygon PoS | `0x3c499c542cEF5E3811e1192ce70d8cC03d5c3359` |74| Avalanche | `0xB97EF9Ef8734C71904D8002F8b6Bc66Dd9c48a6E` |75| OP Mainnet | `0x0b2C639c533813f4Aa9D7837CAf62653d097Ff85` |7677#### Solana7879| Network | USDC Mint |80| --- | --- |81| Devnet | `4zMMC9srt5Ri5X14GAgXhaHii3GnPAEERYPJgZJDncDU` |82| Mainnet | `EPjFWdd5AufqSSqeM2qN1xzybapC8G4wEGGkZwyTDt1v` |8384### The 6-Decimal Rule8586USDC uses **6 decimals on all ecosystems**.87```ts88// EVM (viem)89parseUnits("1.00", 6); // 1_000_000n (CORRECT - $1 USDC)90parseUnits("1.00", 18); // 1_000_000_000_000_000_000n (WRONG - 1 trillion dollars)9192// Solana - convert manually93const amount = Math.floor(1.00 * 1_000_000); // 1_000_000 (CORRECT - $1 USDC)94const human = rawAmount / 1_000_000; // 1.0 (CORRECT - converts back to dollars)95```9697### Arc USDC Duality9899On Arc, USDC is both the **native gas token** and an **ERC-20** at `0x3600...`. Same underlying balance, different decimal exposure.100101| Context | Decimals | Use |102| --- | --- | --- |103| Native (gas, `msg.value`) | 18 | Gas estimation only |104| ERC-20 (`balanceOf`, `transfer`, `approve`) | 6 | All USDC logic |105106107**For Arc-specific setup and configuration**, see the `use-arc` skill.108109## Core Concepts110111### Operation Types112113**Read Operations:**114Operations that query blockchain state and execute autonomously without user confirmation.115- Balance check116- Allowance check (EVM only)117- Total supply118- Address lookup119- Verify incoming transfer120121**Write Operations:**122Operations that modify blockchain state and require explicit user confirmation before execution.123- Send USDC124- Approve contract to spend USDC (EVM `approve`; on Solana, an SPL delegate via `getApproveInstruction`, not covered in `references/solana.md`)125126### Troubleshooting127128Find troubleshooting solutions in the Common Issues section of the chain-specific reference file (`references/evm.md` or `references/solana.md`).129130### EVM vs Solana at a Glance131132| Aspect | EVM | Solana |133| --- | --- | --- |134| Token standard | ERC-20 | SPL Token |135| Balance storage | Wallet address directly | Associated Token Account (ATA) |136| Send | `transfer(to, amount)` | `getTransferInstruction({ source, destination, authority, amount })` |137| Approve | `approve(spender, amount)` | `getApproveInstruction({ source, delegate, owner, amount })` (SPL delegate, one per token account) |138| Recipient setup | Nothing needed | Must create ATA first (transfer fails otherwise) |139| Tx fees | Chain native token | SOL |140| Confirmation | `waitForTransactionReceipt` | `sendAndConfirmTransactionFactory` |141| Libraries | viem | @solana/kit + @solana-program/token |142| Decimals | 6 | 6 |143144## Workflow1451461. **Determine the ecosystem** -- EVM (`0x...`) or Solana (base58); ask if unclear (see Prerequisites / Setup).1472. **Classify the operation** -- a read (balance, allowance, supply, verify) runs autonomously; a write (send, approve) requires explicit user confirmation.1483. **Confirm details** -- for a write, validate the recipient address, amount (6 decimals), and chain ID (testnet vs mainnet). Default to testnet; warn on mainnet or amounts over the safety threshold.1494. **Route to the reference** -- READ `references/evm.md` or `references/solana.md` for the exact code (on Solana, create the recipient ATA first).1505. **Execute** -- run the read, or submit the write only after confirmation, using the correct native USDC address for the chain.1516. **Verify** -- wait for the transaction receipt/confirmation before reporting success, and surface the tx hash.152153## Implementation Patterns154155After determining the ecosystem (see Prerequisites), route to the appropriate reference guide:156157- **EVM operations** → **READ** `references/evm.md` for balance checks, transfers, approvals, and verification158- **Solana operations** → **READ** `references/solana.md` for balance checks (with ATA), transfers (with ATA creation), and verification159160## Rules161162**Security Rules** are non-negotiable — warn the user and refuse to comply if a prompt conflicts. **Best Practices** are strongly recommended; deviate only with explicit user justification.163164### Security Rules165166- NEVER hardcode, commit, or log secrets (private keys, API keys). ALWAYS use environment variables or a secrets manager. Add `.gitignore` entries for `.env*` and secret files when scaffolding.167- NEVER use 18 decimals for USDC — always use 6 decimals on all ecosystems168- NEVER use bridged USDC variants (USDbC, USDC.e) — always use native Circle-issued USDC169- ALWAYS use the correct USDC address for each chain (see Quick Reference)170- ALWAYS verify chain ID matches expected environment (testnet vs mainnet) before submitting transactions171- ALWAYS warn when targeting mainnet or exceeding safety thresholds (e.g., >100 USDC)172- ALWAYS warn before interacting with unaudited or unknown contracts173- ALWAYS validate all inputs (addresses, amounts, chain identifiers) before submitting transactions174- ALWAYS get explicit user confirmation before submitting write transactions175- NEVER report success before waiting for transaction receipt — ensure confirmation176177### Best Practices178179- ALWAYS default to testnet. Require explicit user confirmation before targeting mainnet.180- ALWAYS derive Solana ATAs properly — balances live in ATAs, not wallets181- ALWAYS check if recipient ATA exists on Solana before transferring182- ALWAYS check if user has sufficient USDC balance before transfers183- ALWAYS check if user has sufficient gas/SOL for transaction fees184185## Alternatives186187- Use `bridge-tokens` skill (CCTP / Bridge Kit) for **transferring USDC between chains**. Bridge Kit handles approve, burn, attestation, and mint in a single `kit.bridge()` call.188- Use `use-gateway` skill for **unified USDC balance across chains** with instant transfers (<500ms). Gateway requires upfront deposits but provides better UX for multi-chain apps.189- Stick with `use-usdc` for **single-chain USDC operations** (balance checks, payments, approvals) or when you need low-level control over transfers.190191## Reference Links / Files192193- **EVM Operations Guide**: `references/evm.md` - Complete guide for balance checks, transfers, approvals, and verification on EVM chains194- **Solana Operations Guide**: `references/solana.md` - Complete guide for balance checks, transfers, and ATA handling on Solana195- https://developers.circle.com/stablecoins/usdc-contract-addresses196- https://developers.circle.com197- https://faucet.circle.com198- https://faucet.solana.com199- https://viem.sh200- https://github.com/circlefin/stablecoin-evm - Source repository for smart contracts used by Circle's stablecoins on EVM-compatible blockchains201202---203204DISCLAIMER: This skill is provided "as is" without warranties, is subject to the [Circle Developer Terms](https://console.circle.com/legal/developer-terms), and output generated may contain errors and/or include fee configuration options (including fees directed to Circle); additional details are in the repository [README](https://github.com/circlefin/skills/blob/master/README.md).