A private USDC cross-chain route considers source-to-destination wallet linkage while preserving the need to verify both network representations and all public endpoint records.
Two USDC identities
Source and destination chains use different contracts or asset identifiers. The route must name exactly what is deposited and delivered.
Bridge or liquidity mechanics
A route can burn and mint, lock and release, or use liquidity to deliver value. Those choices affect public messages and contract events.
CCTP as a concrete example
Circle’s CCTP burns USDC on the source domain, emits a message, obtains an off-chain attestation, and submits that message so USDC can be minted on the destination. The source burn, message fields, recipient, amount, and destination mint create inspectable evidence even though the asset remains native USDC.
Not every USDC route is CCTP
An aggregator may choose a liquidity bridge, wrapper, or provider-mediated path instead. Verify the quoted provider and delivered contract rather than assuming one mechanism from the USDC symbol. The privacy analysis changes when delivery comes from inventory instead of a directly corresponding mint.
What observers can compare
Addresses, amounts, timing, route infrastructure, and later wallet behavior can create associations. Stable units can make amount comparison intuitive after fees.
What to check in Sasquatch
Confirm the current provider, output, fees, address, representations, and Private Route status. Static pages do not guarantee live availability.
How to read the evidence
USDC is represented by network-specific contracts or identifiers, so analysis must follow the exact source and destination records. Base uses EVM transactions and logs; Solana uses signatures and token accounts. Cross-chain mechanisms can add messages, burns, mints, or liquidity delivery. Similar output values help research but do not prove a match without supporting route evidence.