USDC.n is being deprecated and will no longer be the supported on the chains covered by this guide. If you hold USDC.n on those mentioned chains, you should migrate it to USDC.inj, the version that will be supported going forward.
After the migration, you will have USDC.inj on the same chain where you started.For example:dYdX USDC.n → dYdX USDC.injIf you start with USDC.n on dYdX, you finish with USDC.inj on dYdX.Skip:Go handles the intermediate steps automatically. You only need to sign twice during the migration.
Enough gas on the chain where your USDC.n is currently held to cover the first transaction
You only need to prepare gas on your source chain.You do not need to prepare INJ in advance. If your INJ balance is insufficient to cover the second transaction, Skip:Go will automatically recharge the required amount of INJ for you.
Open Skip:Go and connect the wallet holding your USDC.n.Select:
From: The chain where your USDC.n is held / USDC.n
To: The same chain / USDC.inj
For example:From:dYdX / USDC.nTo:dYdX / USDC.injEnter the amount you want to migrate.
Make sure the From and To chains are the same and the destination asset is USDC.inj.
2
Sign the first transaction
Review the migration details and approve the first transaction in your wallet.Signature 1 of 2Gas for this transaction is paid on your source chain.
3
Wait while Skip:Go processes the migration
Skip:Go processes the migration automatically after your first signature.The second signature is typically requested within about 3–5 minutes.No action is needed until Skip:Go prompts you to sign again.
4
Sign the second transaction
When prompted, approve the second transaction in your wallet.Signature 2 of 2You do not need to prepare INJ in advance. If your INJ balance is insufficient to cover the second transaction, Skip:Go will automatically recharge the required amount of INJ for you.
5
Confirm the migration
Once Skip:Go shows the migration as complete, confirm that you received USDC.inj on the same chain where you started.For example:dYdX USDC.n → dYdX USDC.injMigration complete.
Only if you also hold USDC.n directly in your dYdX Chain wallet.Do not use this guide for USDC in a dydx.trade trading subaccount. Follow the official dYdX migration instructions for that balance when they become available.
Why do I need to sign twice if Skip:Go handles the migration automatically?
Signature 1 starts the migration from your source chain.Skip:Go then handles the intermediate steps automatically until USDC.inj arrives on Injective.Signature 2 authorizes the final IBC transfer from Injective back to your original source chain.
I completed Signature 1, but Signature 2 hasn't appeared yet. Is something wrong?
After Signature 1, Skip:Go completes the intermediate migration steps before requesting Signature 2.This usually takes about 3–5 minutes, but timing may vary depending on network conditions. Wait until Skip:Go prompts you to sign again.
I completed Signature 1 but not Signature 2. Where are my funds?
Once the automated steps after Signature 1 are complete, your USDC.inj is on Injective.If you do not complete Signature 2, your USDC.inj remains on Injective instead of being transferred back to your original source chain. Your funds are not lost.To move the funds, transfer your USDC.inj from Injective to the supported chain where you want to receive it.
Signature 2 asks me to sign on Injective, but I don't have any INJ. Can I continue?
Yes.You do not need to prepare INJ in advance. If your INJ balance is insufficient, Skip:Go provides the INJ needed for Signature 2.The only gas token you need to prepare is your source chain’s gas token for Signature 1.
I selected the same chain for From and To. Why do I see Avalanche or another EVM network in the route?
This is expected.On the CCTP route, Skip:Go uses an EVM network as an intermediate step in the background.You do not need to select, fund, or interact with that network, and you do not need to prepare its gas token. Your migration still ends with USDC.inj on your original source chain.
Is USDC.n → USDC.inj a swap?
Not necessarily. Skip:Go automatically determines the best route based on the transfer amount and the source and destination chains.When the source and destination chains are the same, amounts above 250 USDC.n use CCTP as part of the migration route.For other cases — including amounts of 250 USDC.n or less, or transfers between different source and destination chains — Skip:Go automatically selects the best available route for the transfer.Regardless of the route used, you will receive USDC.inj on the destination chain. No additional conversion or migration is required on your end.
My USDC.n is on a chain that isn't supported by this migration. What should I do?
If your USDC.n is on a chain not listed above, check whether Skip:Go provides a route to transfer your USDC.n to one of the supported chains listed above. If a route is available, transfer your USDC.n to that supported chain first, then follow this migration guide.If no supported route is available, contact the team responsible for your chain.For chain teams: A direct IBC path with Injective is required to support your chain as a USDC.inj destination, including IBC light clients, an ICS-20 transfer channel, and at least one reliable relayer.If you need help meeting these requirements and already have a Skip contact, work with them for guidance and assistance.Once the IBC connection and relaying are operational, use your existing contact with Skip or submit a Chain Integration Request to request support for your chain as a USDC.inj destination on Skip:Go.