Reviewed Xuanxi default
Native USDC on Base
The inspected implementation maps USDCBASE to 0x833589...A02913 by default, matching Circle's official Base contract.
USDC on Base
USDC on Base: know native from bridged before you route
The reviewed Xuanxi implementation maps USDCBASE by default to 0x833589...A02913, the native Base USDC contract on Circle's official list. The public catalog confirms the route but does not expose a production contract override.
Start with the contract, not the USDC ticker
Xuanxi verifies a Base route in its catalog, but the snapshot does not expose a contract address. That missing field matters because Base has native and bridged USDC.
Bridged USDC
A different token contract
A bridged representation is not automatically interchangeable with native USDC, even when both display the same ticker.
What is verified for USDCBASE, and what remains live
The catalog entry, reviewed default mapping, Circle contract identity, and Base ledger are separate findings. A production override and commercial terms still require the live route.
| Fact | Current read | Applies to | Finding | Reference |
|---|---|---|---|---|
| Xuanxi route | USDCBASEThe catalog confirms a Base route in both directions; it does not identify the accepted token contract. | Xuanxi catalogDirectly observed | Verified | Source: Public enabled-route catalog |
| Reviewed route default | 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913Xuanxi revision 1e2d7e0 maps USDCBASE to this contract by default. A production environment value can override the default. | Reviewed Xuanxi implementationDirectly observed | Verified | Source: First-party route implementation reviewed at revision 1e2d7e0 |
| Ledger visibility | Fully publicBase is an Ethereum L2; transfers are visible on BaseScan. | Network-wideOn-chain / public ledger | Verified | Source: Base public block explorer |
| Network fee | Paid on BaseThe L2 network fee does not identify which USDC contract the route accepts. | Network-wideOn-chain / public ledger | Verified | Source: Base public block explorer |
| Public token identity | Native Base USDCCircle's official contract list identifies 0x833589...A02913 as USDC on Base. | Contract-specificPrimary document | Verified | Source: Official USDC contract addresses by blockchain |
| Circle authority | Blocked addressesCircle's USDC Terms reserve blocking and freezing powers for specified addresses. | Issuer-widePrimary document | Verified | Source: USDC Terms: blocked addresses and frozen funds |
| Bridged USDC | Different contractBridged USDC is a separate token contract; confirm which one your route expects. | Per routeReasoned from public facts | Partially verified | Not available |
| Live contract override | Not exposed by catalogThe reviewed default is native USDC, but the public route response does not expose the active production override. | Per routeNo evidence | Not published | Not available |
Base changes cost and routing, not Circle's authority
What the L2 changes
BaseScan exposes L2 transfers and bridge activity. Lower network cost changes the economics, not the visibility of those records.
What the L2 leaves intact
Native Base USDC is Circle-issued and subject to Circle's blacklist, exactly like Ethereum USDC. Being on an L2 does not weaken issuer authority.
Before using a Base destination
A destination that accepts Ethereum USDC may still reject Base deposits. Confirm both Base support and the accepted USDC contract.
- Native vs bridged USDC is the key gotcha on Base.
- An L2 lowers fees, not issuer control or ledger visibility.
Base USDC questions about contracts
What is the difference between native and bridged USDC on Base?
Native USDC is issued directly by Circle on Base. Bridged USDC came from another chain through a bridge and is a different token contract. They are not always interchangeable and destinations may accept only one.
Which Base USDC contract did the Xuanxi review find?
The reviewed implementation default is 0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913, which Circle lists as native USDC on Base. The implementation allows an environment override, so confirm the live route before sending.
Does Circle control USDC on Base?
For native Base USDC, yes. The same blacklist authority applies, and moving to an L2 does not remove it.
Carry the contract decision to the destination
The reviewed default is native Base USDC. Xuanxi opens immediately, so confirm that its live route still presents Base and the expected contract before sending.