Post
Share your knowledge.
Transferred USDC to wrong network; can I recover it?
I mistakenly transferred USDC to a Sui wallet instead of Aptos. I realized the Aptos network was wrongly selected as the SUI network. Is there a way to recover my USDC since the wallet address is the same on both networks?
- Security Protocols
Answers
10your fund is gone. the only way you have any chance of recovery is if you sent it to a centralized exchange.you dig.
Wrong-network USDC transfers are usually unrecoverable; contact bridge support.
Unfortunately there is no way you can recover your usdc when you transfer from Sui to Aptos wallet. Remember to transfer assets in the same network
If you transferred USDC to the wrong network, recovery depends on how the token transfer was made and whether there’s cross-chain support:
When you send USDC from one blockchain (say Solana, Ethereum, or Aptos) to another without going through an official bridge, the funds don’t automatically “show up” on the other chain, even if the wallet address is identical. Sui and Aptos both use Move-based wallets where the addresses may look the same, but they’re separate blockchains with separate ledgers. That means the USDC you sent is sitting on the wrong chain’s contract address and isn’t automatically recoverable by you.
In most cases, tokens sent to the wrong network can only be recovered if:
- The receiving chain has a bridge or custodian that holds the funds and can manually help.
- The wallet provider (like your Sui or Aptos wallet team) offers manual recovery and you submit a support ticket.
- You had control of the private keys on both networks and the token contract matches (which usually isn’t the case with USDC).
For USDC specifically, Circle issues tokens separately on each chain, so the Aptos version and Sui version aren’t interchangeable. If you mistakenly sent Aptos-USDC to a Sui address, it will not appear in your Sui wallet because Sui doesn’t recognize Aptos-native USDC.
Next Steps for You:
- Confirm on a block explorer (Aptos Explorer if you meant Aptos, Sui Explorer if you meant Sui) where the transaction landed.
- If the USDC is on Aptos but you were aiming for Sui, your funds are safe on Aptos — just access them with an Aptos-compatible wallet using the same private key.
- If the tokens are stuck in a contract (for example, sent directly to a smart contract address not meant to receive tokens), they may be irretrievable.
- Contact your wallet provider (Phantom, Suiet, etc.) or the bridge you used, explain the mistaken network selection, and ask if they can manually help.
Recovery is not possible if you sent USDC to a Sui wallet address from another chain (e.g., Aptos), even if the address format appears similar. Sui and Aptos use distinct cryptographic protocols (Ed25519 vs. Secp256k1), meaning the same string of characters represents different underlying keys on each network. The funds are likely irretrievable unless the receiving Sui wallet explicitly supports multichain USDC recovery—which is rare. Always verify the network and address format before transferring, and use bridge interfaces (e.g., Wormhole) for cross-chain moves to avoid this issue.
No, you cannot recover USDC sent to the wrong network.
Why?
- Sui and Aptos are separate blockchains—same address format doesn’t matter.
- The funds are on Sui, but your Aptos wallet can’t access them.
What to Do:
- Import your wallet into a Sui-compatible app (e.g., Sui Wallet) using the same private key.
- Your USDC should be there, but it’s on Sui, not Aptos.
To Use It on Aptos:
- You’ll need to bridge it from Sui to Aptos (e.g., using Wormhole).
Prevention: Always double-check the network before sending.
(Crypto transfers are irreversible—always verify the network!)
Unfortunately, if you sent USDC on the Aptos network to a Sui wallet address, the funds are likely unrecoverable. Even if the address string looks the same, Aptos and Sui are completely separate networks—they can't read each other's transactions.
Your USDC is now essentially stuck on the Aptos blockchain at that address. Since you probably don't control the Aptos version of that Sui address, you can't access it. It's a tough and expensive mistake.
Your only real hope is to contact the support team of the exchange or wallet you sent from. Sometimes, if the funds are still on an exchange-controlled wallet, they might be able to help—but it's not guaranteed. For future transfers, always double-check the network. I think we've all learned this the hard way once.
Unfortunately, there's no way to reverse a transaction in the network once it's done. The USDC is basically irretrievable. Even if it went to the same address on Sui, it may not belong to anyone currently.
If you sent USDC to a Sui wallet instead of Aptos, you can’t directly recover it because the two networks are separate even though they both use Move-based cryptography. The wallet address may look identical, but tokens do not move across chains without a bridge. This means your USDC is now stuck on Sui, where Circle does not issue official USDC. If the receiving wallet was your own Phantom wallet, those funds have no usable value on Aptos. The only exception is if you sent to an exchange wallet that controls accounts on both chains, in which case you should immediately contact their support to request a recovery. You can also reach out to the bridge provider or Circle support, but in most cases, recovery is unlikely unless a centralized custodian is involved. To avoid this in the future, always double-check the selected network, run a small test transfer first, and keep enough SUI or APT for gas fees before moving larger amounts. You can read more here: USDC recovery and supported blockchains.
Transaction block Input → You selected SUI instead of Aptos while sending USDC. Process → The tokens were recorded on the Sui blockchain, not Aptos, since blockchains do not communicate natively. Result → USDC is stuck on Sui, unrecoverable unless sent to a custodian that supports both networks.
Do you know the answer?
Please log in and share it.
Sui is a Layer 1 protocol blockchain designed as the first internet-scale programmable blockchain platform.

- ... SUIMatthardy+2095
- ... SUIacher+1666
- ... SUIjakodelarin+1092
- ... SUIChubbycheeks +1081
- ... SUITucker+1047
- ... SUIKurosakisui+1034
- ... SUIzerus+890
- Why does BCS require exact field order for deserialization when Move structs have named fields?65
- Multiple Source Verification Errors" in Sui Move Module Publications - Automated Error Resolution55
- How to Maximize Profit Holding SUI: Sui Staking vs Liquid Staking414
- Sui Transaction Failing: Objects Reserved for Another Transaction49
- Sui Move Error - Unable to process transaction No valid gas coins found for the transaction316