If you have initiated a deposit or withdrawal from dYdX v4 and your funds haven't arrived within an hour, follow this guide to better understand where your transaction is in the process and how to troubleshoot it.
Important: After submitting a deposit, make sure you do not close the tab or web browser, as leaving the frontend may lead to funds getting delayed en route to your dYdX address.
Withdrawal and Deposit Process
There are currently 2 main withdrawal and deposit flows on the dYdX front end.
We can categorize them in:
CCTP: USDC deposits or withdrawals via Ethereum, Arbitrum, Optimism and Avalanche, Polygon, Base, Solana.
Axelar or non-CCTP: If they do not fall into the CCTP category, they are by default using the Axelar route. This includes USDC transfers on non-CCTP supported chains, and any other assets from other chains.
Troubleshooting CCTP Transactions
CCTP Flow
If your deposit is routed via CCTP, the process is as follows:
Native USDC is burned on the source chain
The same amount of USDC is minted on Noble chain
USDC is routed to dYdX Chain via IBC
Withdrawals follow the opposite flow, with Noble USDC being burned on Noble chain and Native USDC being minted on the destination chain. For more info on this flow, see:
https://dydx.exchange/blog/cctp.
CCTP deposits troubleshooting
Check dYdX frontend status
Refresh your browser and check on the dYdX front end if your deposit has succeeded. If you notice after one hour that your deposit is still on the "bridging tokens" step, continue to step 2.
Check tracker tool
Check whether your USDC has been bridged, by entering the transaction hash on https://usdc.range.org/usdc.
Tip: Be sure to tick the "Show Pending" box.
If the status shows "finalized", USDC should have arrived on Noble, and you can move on to step 3.
If the status shows "Pending" for more than one hour, raise a support ticket to https://dydx.trade > Help > Live Chat and make sure to share:
- Transaction hash
- EVM address
- dYdX address
Note: You can also ask skip for support via their Discord here
Check destination address
Now check whether your funds have arrived on dYdX: https://www.mintscan.io/dydx. You should see a "deposit to subaccount" transaction there.
If not, you can confirm whether USDC has arrived on Noble, by checking https://www.mintscan.io/noble or https://ibc.range.org.
You need to make sure you have the dYdX Front-end opened and wallet connected. The dYdX front end will detect your funds on Noble and auto-sweep it to your dYdX address. For this to happen, you need to actively open the front end and connect your wallet.
Manual process stuck funds
If for some reason, you have done step 3, but you still don't see your funds on dYdX, you can always manually IBC transfer your funds to your dYdX address, by importing your secret phrase into Keplr and performing a manual IBC transaction from Noble to your dYdX address.
Troubleshooting Axelar transactions
Axelar Flow
If your deposit is routed via Axelar, the process is as follows:
Skip routes funds to axlUSDC on EVM using Axelar General Message Passing (GMP)
axlUSDC on EVM gets burned and axlUSDC minted on Axelar
axlUSDC is sent to Osmosis and swapped to Noble USDC
Bridge Noble USDC from Osmosis -> Noble chain -> dYdX Chain
Withdrawals follow the opposite flow.
For more info on this flow, see https://dydx.exchange/blog/1-click-onboarding.
Axelar troubleshooting
Check dYdX Frontend status
Refresh your browser and check on the dYdX front end if your deposit has succeeded. If you notice after one hour that your deposit is still on the "bridging tokens" step, continue to step 2.
Check tracker tool
Check whether your funds have arrived on the destination side, by entering the origin transaction hash and chain_id (see chain_id here) on https://docs.skip.build/go/api-reference/prod/transaction/get-v2txstatus.
For DepositsIf the status shows "axelar_transfer_success", funds should have arrived on dYdX and you can move on to step 3.
If the status shows "axelar_pending_confirmation" or "axelar_transfer_failure", check at which "hop" (or intermediary chain) the funds got stuck.
If the status in a hop shows "axelar_pending_confirmation" or "axelar_transfer_failure" at Osmosis or Noble, you can move on to step 3, to manually move your funds.
If the funds are "axelar_pending_confirmation" for more than 1 Hour or "axelar_transfer_failure" with Axelar, raise a support ticket via: https://dydx.trade > Help > Live Chat and make sure to share:
- Transaction hash
- EVM address
- dYdX address
You can also ask skip for support via their Discord here
For Withdrawals
If the status shows "axelar_transfer_success", funds should have arrived on your destination address and you can move on to step 3.
If the status shows "axelar_pending_confirmation" or "axelar_transfer_failure" for more than one hour, check at which "hop" (or intermediary chain) the funds got stuck.
If the funds are "axelar_pending_confirmation" for more than 1 Hour or "axelar_transfer_failure" on Axelar / Osmosis, raise a support ticket via https://dydx.trade > Help > Live Chat and make sure to share:
- Transaction hash
- EVM address
- dYdX address
You can also ask skip for support via their Discord here
Check destination
Now check whether your funds have arrived at the destination address.
For deposits https://www.mintscan.io/dydx, you should see a "deposit to subaccount" transaction in your transactions list.
If not, you can confirm whether the USDC has arrived on Noble, by checking https://www.mintscan.io/noble.
You need to make sure you have the dYdX front end opened and your wallet connected. The dYdX front end will detect your funds on Noble and auto-sweep it to your dYdX address. For this to happen, you need to actively open the front end and connect your wallet.
Manual process stuck funds
If for some reason, you have done step 3, but you still don't see the funds, you can always manually IBC transfer your funds to your dYdX address, by importing your secret phrase into Keplr and and perform a manual IBC transaction to your dYdX address.
Disclaimer and Terms
This document may provide information with respect to the dYdX Chain software, and/or non-mandatory guidelines and suggestions that may help with using dYdX Chain software. dYdX Operations Services Ltd. does not run dYdX Chain validators nor operate or control the dYdX Chain network. dYdX Operations Services Ltd. is not responsible for any actions taken by other third parties who use dYdX Chain software. dYdX Operations Services Ltd. services and products are not available to persons or entities who reside in, are located in, are incorporated in, or have registered offices in the United States or Canada, or Restricted Persons (as defined in the Terms of Use). The content provided herein does not constitute, and should not be considered, or relied upon as, financial advice, legal advice, tax advice, investment advice or advice of any other nature, and you agree that you are responsible to conduct independent research, perform due diligence and engage a professional advisor prior to taking any financial, tax, legal or investment action related to the foregoing content. An asset's inclusion in a particular liquidity tier is not an endorsement or recommendation of the asset, and trading in any asset supported by dYdX Chain may involve material risks, including the risk of financial losses arising from market volatility or liquidation. The information contained herein, and any use of products or services provided by dYdX Operations Services Ltd., are subject to the Terms of Use.