Skip to main content
Use this guide to migrate USDC.n to USDC.inj with Skip:Go.

​
Why this migration is needed

USDC.n is being deprecated in favor of USDC.inj
USDC.n is being deprecated and will no longer be the supported version of USDC on the chains covered by this guide. If you hold USDC.n, you should migrate it to USDC.inj, the version that will be supported going forward.

​
What are the differences between USDC.n and USDC.inj?

Both are USDC, but they originate from different chains and are treated as separate assets on Cosmos chains.
  • USDC.n: USDC originating from Noble
  • USDC.inj: USDC originating from Injective

​
What happens when you migrate

Two-stage overview of the USDC.n to USDC.inj migration
After the migration, you will have USDC.inj on the same chain where you started. For example: dYdX USDC.n → dYdX USDC.inj Skip:Go routes the migration through Injective. You do not need to send your funds to Injective manually.

​
Who this guide applies to

This guide applies to USDC.n held on:
  • dYdX, Cosmos Hub, Osmosis, Terra, Neutron, ZIGChain
If your USDC.n is on a chain not listed above, check whether Skip:Go provides a route to transfer it to one of the supported chains listed above. If a route is available, transfer your USDC.n to that chain first, then follow this migration guide. If no supported route is available, contact the team responsible for your chain. For chain teams: See What if my USDC.n is on a chain not listed above? in the FAQ below for the requirements and process to add support.
dYdX usersThis guide applies only to USDC.n held in your dYdX Chain wallet.It does not apply to USDC in a dydx.trade trading subaccount. Follow the official dYdX migration instructions for that balance when they become available.

​
What to do

Manual migration will be available starting August 28, 2026. A simpler one-step migration is planned for Mid-September, 2026.
The signature counts above only cover the migration itself and exclude any transactions needed to obtain fee tokens.

​
Before you start

The manual migration has two stages: Stage 1: USDC.n on your source chain → USDC on an EVM network Stage 2: EVM USDC → Injective → USDC.inj on the chain where you started This guide uses dYdX as the source chain and Avalanche as the EVM network. If your USDC.n is on another supported source chain, select that chain instead. The overall migration flow is the same.
Stay safeUse only the official Skip:Go site at go.skip.build. Never share your seed or recovery phrase.

​
1. Prepare gas

Preparing gas on the source chain, EVM network, and Injective
The manual migration requires transaction fees on three networks:
  1. Your source chain
  2. Your selected EVM network
  3. Injective
Make sure you have the required fee tokens on all three networks before starting.

​
Source chain

Keep approximately $0.10 worth of a supported fee token on the chain where your USDC.n is held.

​
EVM network

You also need gas on the EVM network used for the migration. You can use another supported EVM network if you prefer or already have gas there.

​
Injective

You need INJ to pay the Injective transaction fee in Stage 2.
Fees are estimates and may vary with network conditions. Recommended balances include extra buffer.

​
2. Check your wallets and addresses

Before starting, make sure you can access:
  • The wallet holding your USDC.n
  • A wallet on your selected EVM network
  • An Injective address with INJ for gas
  • An address on your original source chain to receive USDC.inj
Your source and destination addresses may be in the same wallet, and the same wallet may support more than one of these networks. This guide uses Keplr for dYdX and Injective. For the EVM network, use a wallet supported by Skip:Go.
Select each address from a wallet that supports that network. Do not manually convert one address format into another.

​
Stage 1: Move USDC.n to an EVM network

dYdX USDC.n → Avalanche USDC
  • Wallet signatures: 1
  • Estimated time: Up to 6 minutes
1

Select USDC.n and enter the amount

Selecting USDC.n as the source asset and entering the migration amount
Open Skip:Go and connect the wallet holding your USDC.n.Select:
  • From: dYdX / USDC.n
  • To: Avalanche / USDC
Enter the amount you want to migrate.Select Swap to continue.
Skip:Go uses its standard Swap interface here, even though this step is part of the USDC.n migration.
2

Set the destination address

Select Set destination address.
3

Connect the destination wallet

Select the wallet that controls your Avalanche address.Confirm the destination address before continuing.
4

Review and sign

Reviewing the Stage 1 transaction before signing
Check:
  • From: dYdX / USDC.n
  • To: Avalanche / USDC
  • Amount
  • Destination address
Approve the transaction in your source wallet.Signature 1 of 3
5

Wait for the transfer

Skip:Go will track the transfer automatically.Keep this page open while the transfer is in progress.
6

Complete Stage 1

When Skip:Go displays Go again, Stage 1 is complete.Your USDC is now on Avalanche.Continue to Stage 2 to migrate it to USDC.inj on your original source chain.

​
Stage 2: Move EVM USDC to USDC.inj on your source chain

Avalanche USDC → Injective → dYdX USDC.inj
  • Wallet signatures: 2
1

Select USDC and USDC.inj

Selecting Avalanche USDC as the source and dYdX USDC.inj as the destination
In Skip:Go, select:
  • From: Avalanche / USDC
  • To: dYdX / USDC.inj
Enter the amount you want to migrate.If your migration started on another supported source chain, select that same chain as the destination.
Make sure the destination asset is USDC.inj, not USDC.n.
2

Review and confirm

Check:
  • From: Avalanche / USDC
  • To: dYdX / USDC.inj
  • Amount
  • Destination address
Select Confirm.
3

Continue to signing

Skip:Go will display 2 signatures required.Select Continue and keep the window open until both signatures are complete.
4

Complete both signatures

Approving both required signatures to complete Stage 2
Approve both transactions when prompted:
  1. Injective transaction → uses INJ for the transaction fee
  2. Avalanche transaction → uses AVAX for the transaction fee
Review each transaction before approving it.
5

Wait for the migration

After both transactions are approved, Skip:Go will process the migration.Keep this page open while the migration is in progress.
6

Confirm completion

When Skip:Go displays Go again, the migration is complete.Confirm that USDC.inj is available on dYdX.Migration complete:dYdX USDC.n → dYdX USDC.inj

​
FAQ

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.
You can resume the migration later.
  • After Stage 1: Your USDC remains on the EVM network you selected. You can start Stage 2 later using that USDC.
  • During Stage 2 signing: Both signatures are required before Stage 2 proceeds. If you stop before completing both signatures, your USDC remains on the EVM network. You can start Stage 2 again when you are ready.
For example, if you use Avalanche, your USDC remains on Avalanche until Stage 2 proceeds.
This guide is specifically for migrating your balance from USDC.n to USDC.inj.Skip:Go may display Swap in parts of the interface because the same interface is also used for swaps and cross-chain transfers.Swapping USDC.n for another token, such as DYDX, AVAX, or INJ, is a separate transaction and is not part of this migration.
No. Mid-September is the planned launch date for the one-step migration, not a migration deadline.Manual migration will be available starting August 28, 2026. You can use the manual flow or wait for the one-step migration planned for mid-September.
No.This guide uses Avalanche as an example; you can use any supported EVM network.If you choose another network, make sure you have the required gas token before you start.
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.

​
Official references