Moving an asset between blockchains requires a crosschain mechanism. A normal Solana transfer changes Solana state; it does not create an Ethereum or Base receipt. Before using a bridge, identify the source asset, destination asset and mechanism that connects the two records.
Determine what the destination token represents
One bridge design locks an asset on the source and issues a representation on the destination. The resulting token depends on that bridge's backing, verification and redemption rules. Its ticker can resemble the original asset while its mint and claim differ.
For native USDC routes, Circle's CCTP uses burn-and-mint: USDC leaves circulation on the source and the protocol authorizes native USDC issuance on the destination. This avoids creating a separate wrapped-USDC claim for that route. The bridge interface can still add routing, swaps, service fees and execution dependencies.
Check the complete asset identity at both ends. Native USDC, a wrapped representation and a token with a copied symbol are not interchangeable for an exchange deposit or a merchant invoice. Consult the issuer's current contract and mint references.
Verify the exact route before funding it
CCTP identifies networks with its own domain identifiers. Those identifiers differ from ordinary EVM chain IDs. Developers should use Circle's supported-domain and deployment references, including the selected environment and protocol generation.
For a user, the practical equivalent is to check source network, destination network, token, recipient and received amount in the actual quote. Also identify who submits the destination transaction. Some services arrange forwarding; others require a claim action and native gas on the receiving network.
A bridge request can include a swap before or after the crosschain stage. If you start with SOL and want a different token on another network, the operation includes more than a native-USDC burn. Record the additional conversion and its execution limit.
Follow burn, attestation and mint separately
First obtain the source transaction signature or hash and inspect its accepted result. A successful source burn establishes the first stage. It does not establish that the destination token account has been credited.
Next track the protocol message and its attestation status. Circle provides signed attestations after the route's required observation policy. Fast and Standard modes differ in that policy, applicable fees and availability. The service's timing estimate includes work outside Solana consensus.
Finally locate the destination transaction and verify its execution, recipient, token and amount. Save both transaction identifiers and the crosschain message identifier. That record is more useful for troubleshooting than one generic “bridge pending” label.
Compare delivered USDC and separate gas costs
Compare delivered value rather than the headline fee
Use a teaching quote, not a live offer: input 100 USDC, interface charge 0.20 and protocol charge 0.10 leave 99.70 USDC before any additional destination swap. Source and destination gas can be separate costs in different native assets.
A second route advertising zero transfer fee could still deliver less after its swap spread or gas funding. Compare the same input, output, networks and completion requirement. A gas-sponsored destination claim and a self-submitted claim are different service packages.
Do not treat the network's finality target as a bridge delivery guarantee. Even when the source chain has accepted the burn, attestation, forwarding, destination execution or a later application call can remain unfinished.
Resume an incomplete transfer using its existing evidence
If the burn failed, inspect the source error. If it succeeded but attestation is pending, track that original message through the official protocol or the interface's supported recovery flow. If the attestation exists but destination execution failed, investigate its destination accounts, gas and error.
Starting a second burn does not finish the first transfer. It creates another transfer to reconcile. Use the original identifiers when contacting the service, and keep recovery phrases and private keys out of the support conversation.
A final check should reconcile the source debit, destination credit and all stated charges. An accepted token mint can still leave a later exchange credit or application deposit pending. Follow the route until the asset reaches the destination state you originally intended.
Sources and documentation
- Circle: CCTP overview
- Circle: supported CCTP blockchains and domains
- Circle: attestation finality requirements
- Circle: official Solana CCTP programs
- Circle: USDC contract addresses
Found an error or an outdated detail? Send a correction.