Đang kiểm tra khả năng đọc thành tiếng của trình duyệt…
Bài đọc này hiện có bằng tiếng Anh. Giao diện sử dụng ngôn ngữ bạn đã chọn.
Đọc bản gốc tiếng Anh →Native and bridged USDC have different identities
Distinguish token origins before selecting a pool.
A stablecoin label can hide a different contract and a different route into the network.
- Native USDC contract
- Bridged USDC.e contract
- Destination supports a specific identity
Compare the contracts
Arbitrum documents native USDC and bridged USDC.e as separate tokens with different contracts. Read the current official addresses. A shortened label in a wallet or pool selector can obscure that distinction.
Check the receiving application's support
Confirm which exact token the destination, pool or service accepts. A quote for one representation does not establish support for the other. Bridging and swapping are different operations; check the intended route before authorizing either.
Compare official identities
Read the documentation; do not connect a wallet.
- Find the two contracts in the guide.
- Write native and bridged on separate cards.
- Explain what a recipient must specify.
Use the contract and origin, not a generic stablecoin name.
Choose the token representation the destination actually supports.
Tiến độ được lưu trên thiết bị này.