Moving USDC from Solana to Base means crossing from an SVM chain to an EVM chain, so the route has to handle two address formats, two fee tokens and two settlement models. The practical options are Circle's Cross-Chain Transfer Protocol (CCTP), which burns USDC on Solana and mints native USDC on Base; a solver-filled intent route, where a third party delivers USDC on Base and is repaid on Solana; and an exchange deposit followed by a Base withdrawal. Circle lists Solana as CCTP domain 5 and Base as domain 6, and both support Fast Transfer as a source (Circle CCTP supported blockchains).
​

Last reviewed: Nov 2026. Every time and fee statement below links to the page it came from. For chain background, see USDC on Solana and USDC on Solana vs Ethereum.
​

Each route is held to the same four tests: whether native USDC arrives on Base, how long the provider says the settlement step takes, how the route charges, and which party must act for funds to land. Cross-VM transfers add a fifth practical check, which is whether the tool accepts a Solana sender and an EVM recipient in one flow.

Three route types cover most Solana to Base USDC transfers. CCTP is Circle's own burn-and-mint path between the two domains. Intent routes let a solver pay out on Base first and settle later. Exchanges move the balance through their own custody. Each can deliver native USDC; they differ on time, cost model and custody in transit.
​

Best for: treasury and application flows that want the issuer path end to end.
​

Pros: Circle's published averages for Solana as a source are about 0.4 to 0.6 seconds for a Fast Transfer attestation after 2 to 3 confirmations, and about 17 seconds for a Standard Transfer after 32 confirmations (Circle finality and block confirmations). Standard Transfers of USDC carry no protocol fee (Circle CCTP fees).
​

Cons: Fast Transfers carry a route-specific fee and sit under a global allowance. The Base mint still needs an EVM transaction, so the receiving side needs ETH for gas unless a relayer submits it. Circle's supported-chains table also marks its Forwarding Service as available for both Solana and Base (Circle supported chains).
​

Best for: wallets and apps that want one integration for Solana and EVM chain pairs.
​

Pros: the Routes API describes chains with a type field that includes svm for Solana alongside evm, and its reference integration covers a Solana source chain (Eco Routes API agent integration). A solver supplies the destination assets, and the source-side reward is released only after the configured prover confirms fulfillment (Eco Routes overview).
​

Cons: pricing is set at quote time rather than in a published schedule, and a fill depends on solver participation for that pair and size.
​

Best for: individuals moving a one-off balance through an account they already use.
​

Pros: the exchange abstracts both address formats.
​

Cons: custody in transit, venue-specific withdrawal fees and minimums, and the need to confirm the Base contract matches Circle's listed native USDC address (Circle USDC contract addresses).
​

The table lines the routes up on the same criteria. Times are the provider's own published averages. Where no time or fee schedule is published, the cell says so instead of estimating one.
​

Because Solana's Standard attestation is already short, the Fast versus Standard trade-off matters less here than on routes that start on Ethereum or an optimistic rollup. The bigger decision is whether the transfer is part of a product, where one cross-VM integration saves work, or a one-off move.
​

Liquidity on each side is deep. DefiLlama's data showed about $7.11 billion of USDC on Solana and about $4.43 billion on Base on November 11, 2026 (DefiLlama stablecoins API). For the Base-side landscape, see Base stablecoin aggregators.
​

Most failed Solana to EVM transfers come from recipient formatting, missing destination gas, or sending a token that is not the native USDC mint. None of these are route failures; they are input errors the route cannot correct after the burn or deposit is confirmed.
​

Solana addresses are base58 strings and Base addresses are hex strings, so the sending tool must accept an EVM recipient from a Solana signer. CCTP identifies each chain by a numeric domain rather than a chain ID, with Solana at 5 and Base at 6 (Circle supported chains). Checking the destination contract against Circle's list before sending avoids receiving a bridged representation (Circle addresses).
​

This page uses published documentation, not live quotes. Averages move with network conditions, intent route prices exist only at quote time, and exchange terms differ by venue and jurisdiction. It also does not cover USDT, which does not use CCTP.

These answers cover the questions teams ask most when they first connect Solana USDC to Base. Each one links to the primary page behind it.
​

Only if you submit the Base mint yourself. Relayers can submit it instead, and Circle's supported-chains table marks its Forwarding Service as available for Solana and Base (Circle supported chains).
​

Both are Circle-issued when you use the addresses in Circle's contract list; CCTP burns on one chain and mints on the other (Circle addresses).
​

Yes. Base supports Fast Transfer as a source with an average attestation of about 8 seconds (Circle finality).
​

All facts come from primary documentation fetched on November 11, 2026. No transfers were run; every time is the provider's own published figure. Supply figures come from DefiLlama's public stablecoin API on the same date.