USDC deposits and withdrawals
Collateral on the chain is USDC. On the testnet you can get test USDC two ways:
- the faucet: $10,000 of test USDC a day, straight to your address (quickstart). It stays: it trades like any USDC but can't leave the chain;
- the bridge: Circle's test USDC from Ethereum Sepolia, Arbitrum Sepolia or Base Sepolia, by the route dYdX's own chain uses since v9.9. It goes back the same way.
Both are the same coin on the chain (the USDC denom below), but only USDC that came in over the bridge can leave: the chain keeps, per address, what it received over IBC less what it sent (how much you can withdraw).
Only USDC moves over the bridge. The chain refuses to send any other token out over channel-0, and any other token sent here from Injective arrives as a voucher that can't go back.
The route
EVM testnet wallet (MetaMask)
│ Circle CCTP V2: burn USDC on Sepolia, Arbitrum Sepolia or Base Sepolia
▼
Injective testnet (injective-888): mint, at your own address
│ IBC transfer (ICS-20) over our channel-0, relayed by a Hermes relayer
▼
firstaccess-testnet-1: your address's wallet
│ MsgDepositToSubaccount
▼
a subaccount, to trade
| USDC denom on this chain | ibc/2547906198C60129474CC58DEA82084E5B6D39E993D29E345D83925C2B988A7F: SHA-256 of transfer/channel-0/erc20:0x0C382e685bbeeFE5d3d9C29e29E341fEE8E84C5d, asset 0 |
| Our channel | transfer/channel-0, the chain's first channel, to injective-888 |
| Injective's channel | Its end of channel-0: channel.counterparty.channel_id in /ibc/core/channel/v1/channels/channel-0/ports/transfer. The trading app pins it in its config.json (bridge.injectiveChannel) and moves nothing if they differ |
| Who may open IBC channels | Only the chain's IBC gate admin (x/ibcgate), so no one else can take or add a channel to an impostor chain |
| What crosses channel-0 | USDC only: any other token's transfer out is refused (x/ibcgate) |
| Relayer | Hermes, run with the testnet |
x/canonicalusdc | Disabled (MODE_DISABLED): plain ICS-20, the voucher is the chain's USDC |
The faucet's USDC and genesis USDC are the same denom as bridged USDC. Read the denom from
/dydxprotocol/assets/asset/0 rather than hard-coding it.
The easy way: the trading app
The trading app's Bridge page (https://app.testnet.firstaccess.exchange/#/bridge) runs
every step with MetaMask and the app's key. You need, in MetaMask: test USDC on the source chain
(Circle's faucet: 20 USDC per request, every 2 hours, per address
and network), that chain's test ETH for gas, and testnet INJ for gas on Injective
(Injective's faucet). The page adds Injective's EVM
testnet (chain 1439) to MetaMask when it needs it.
The page keeps a transfer in progress in the browser, with each transaction's hash from the moment it is sent; after a reload it carries on at the same step and never sends a step twice. Its Recover section picks up a transfer it lost track of (recovery).
Deposit, step by step
Every step is an EVM transaction, signed in MetaMask.
- Burn on the source chain:
approveCircle's TokenMessengerV2 for the amount, thendepositForBurn(amount, 29, mintRecipient, usdc, 0x0, maxFee, finality). Domain 29 is Injective. The mint recipient is your own address, left-padded to 32 bytes: on Injective that address isinj1…, the same 20 bytes. - Wait for Circle's attestation:
GET https://iris-api-sandbox.circle.com/v2/messages/{srcDomain}?transactionHash=0x…untilmessages[0].statusiscomplete. Standard transfers (finality 2000) are free and take about 15 to 19 minutes; fast transfers (finality 1000) take seconds and cost 1 to 1.3 bps (GET /v2/burn/USDC/fees/{src}/29). The app refuses a fast transfer whose fee is above 10 bps, and shows the most Circle may keep before you burn. Before minting, check that the attestedmessageis your burn: its destination domain, mint recipient and amount. - Mint on Injective's EVM (chain 1439):
receiveMessage(message, attestation)on MessageTransmitterV2. Nobody relays CCTP into Injective's testnet, so you mint it yourself and pay INJ for gas. - Send over IBC, still on Injective's EVM: the ICS-20 precompile at
0x0000000000000000000000000000000000000069,transfer(string channel, string receiver, address token, uint256 amount, (uint64,uint64) timeoutHeight, uint64 timeoutTimestamp, string memo), with Injective's channel id, yourdydx1…address, Injective's USDC token and a timeout. No approval is needed. - The relayer carries the packet. The USDC arrives in your wallet (not a subaccount) as the chain's USDC denom, in a few seconds to a minute. Deposit it into a subaccount to trade (accounts).
| Contract (every testnet) | Address |
|---|---|
| TokenMessengerV2 | 0x8FE6B999Dc680CcFDD5Bf7EB0974218be2542DAA |
| MessageTransmitterV2 | 0xE737e5cEBEEBa77EFE34D4aa090756590b1CE275 |
| TokenMinterV2 | 0xb43db544E2c27092c107639Ad201b3dEfAbcF192 |
| Chain | CCTP domain | Test USDC |
|---|---|---|
| Ethereum Sepolia | 0 | 0x1c7D4B196Cb0C7B01d743Fbc6116a902379C7238 |
| Arbitrum Sepolia | 3 | 0x75faf114eafb1BDbe2F0316DF893fd58CE46AA4d |
| Base Sepolia | 6 | 0x036CbD53842c5426634e7929541eC2318f3dCF7e |
| Injective testnet (EVM chain 1439) | 29 | 0x0C382e685bbeeFE5d3d9C29e29E341fEE8E84C5d (bank denom erc20:0x0C382e685bbeeFE5d3d9C29e29E341fEE8E84C5d) |
Sources: Circle's contract addresses,
supported blockchains and
USDC addresses, checked on
chain on 2026-11-16. One depositForBurn moves at most 10,000,000 USDC.
Withdrawal, step by step
-
Withdraw from the subaccount to your wallet (
MsgWithdrawFromSubaccount). Only what your address bridged in can leave, at least $1 a transfer (how much you can withdraw). -
Send from this chain: an IBC transfer (
MsgTransfer) of USDC over channel-0 to theinj1…form of your EVM address, with a timeout (the app uses 10 minutes). The relayer carries it, and Injective releases the USDC from its escrow. With the CLI (its default timeout is 10 minutes), $1:dydxprotocold tx ibc-transfer transfer transfer channel-0 inj1... \ 1000000ibc/2547906198C60129474CC58DEA82084E5B6D39E993D29E345D83925C2B988A7F \ --from KEY --chain-id firstaccess-testnet-1 --node https://rpc.testnet.firstaccess.exchange:443 \ --gas auto --gas-adjustment 1.5 --gas-prices 25000000000adv4tnt -
Burn on Injective's EVM:
approve, thendepositForBurnto the destination's domain, finality 2000. From Injective it is free and attested in about a second. -
Mint on the destination chain:
receiveMessage(message, attestation).
How much you can withdraw
Withdrawals are limited to USDC that arrived at your address over the bridge (x/ibcgate). Per
address, the chain keeps the USDC it received over IBC less what it sent out over IBC: its
allowance.
curl -s https://api.testnet.firstaccess.exchange/dydxprotocol/ibcgate/allowance/dydx1...
# or: dydxprotocold q ibcgate allowance dydx1...- A USDC transfer out above the sender's allowance is refused before anything moves (codespace
ibcgate, code 3), and so is one under $1 (code 4;min_usdc_transfer_quantumsin/dydxprotocol/ibcgate/params). The trading app says "This is more than this address bridged in" and "The smallest withdrawal is $1." - A withdrawal that is refunded (Injective couldn't pay it out, or it timed out) gives the allowance back.
- Faucet and genesis USDC have none: they trade normally but can't leave.
- The allowance belongs to the address the deposit arrived at, not to the coins. Moving USDC between that address and its own subaccounts keeps it. USDC you send to another address can't be withdrawn by that address: the coins go to them, the allowance stays with you, and you can still withdraw that much from any USDC you hold (faucet USDC included).
Limits and failures
- Only bridged-in USDC leaves, at least $1 a transfer (above).
- Only USDC crosses the bridge's channel out. An IBC transfer of any other denom over channel-0 (the native token, any other voucher) is refused with x/ibcgate error 7 ("only USDC may be sent out over the bridge's IBC channel"). Send nothing else in: a token of another denom sent here over channel-0 arrives, but it can't be sent back.
- Withdrawal rate limits (dYdX's
x/ratelimit, on USDC leaving over IBC, across all users): per hour the larger of $10,000 and 1 ppm of all USDC on the chain, per day the larger of $100,000 and 10 ppm: about $1,000,000 an hour and $10,000,000 a day at genesis. A withdrawal over what is left is refused before anything moves; deposits add capacity back. Governance changes them withMsgSetLimitParams. - Refunds: a transfer Injective refuses comes back to your wallet here, usually within a minute; one not delivered before its timeout is refunded to the sender.
- Resets: the testnet may be reset. A reset loses every bridged USDC still on the chain (the old channel's escrow on Injective can't be released). A reset that would strand bridged USDC is announced on the trading app's Bridge page at least 24 hours beforehand, and deposits close there then; withdraw before the date. Closing is the app's: the chain still accepts USDC sent by other means (the precompile directly, a CLI, another wallet), and that too is lost at the reset unless withdrawn.
- Fees: gas on each chain (ETH on the source, INJ on Injective,
adv4tntor USDC here), and Circle's fee on a fast transfer. The bridge itself charges nothing.
Recovering a transfer
Every step is on a public chain, so a transfer can be finished from anywhere:
- USDC at your Injective address (after a mint, before the IBC send; or a deposit that came
back): send it on with the ICS-20 precompile (deposit step 4), or burn it to an Ethereum
testnet (withdrawal step 3). Its balance:
cast call 0x0C382e685bbeeFE5d3d9C29e29E341fEE8E84C5d "balanceOf(address)(uint256)" 0xYOU --rpc-url https://k8s.testnet.json-rpc.injective.network. - A burn not minted yet: fetch its attestation from Circle by the burn's transaction hash
(deposit step 2, with the domain it was burned on: 29 for Injective), then
receiveMessageon the other chain.usedNonces(nonce)on MessageTransmitterV2 is 1 once anyone minted it; the nonce is bytes 12 to 44 of the attested message. - An expired attestation (a fast transfer not minted within about a day:
receiveMessagereverts "Message expired and must be re-signed"):POST https://iris-api-sandbox.circle.com/v2/reattest/{nonce}, then fetch the message again. - A withdrawal that came back: it is in your wallet here again, with its allowance.
- Whether a withdrawal arrived: the chain keeps the relayer's transaction that brought back
Injective's answer. Search it by the packet's sequence (the
send_packetevent of your withdrawal):tx_searchforacknowledge_packet.packet_src_channel='channel-0' AND acknowledge_packet.packet_sequence='N'; itsfungible_token_packetevent hassuccess(paid) orerror(refused, refunded). Atimeout_packetfor the sequence means it timed out (refunded).
The trading app's Bridge page does each of these from its Recover section.
Watching the bridge on chain
# Our channel-0 and Injective's end of it
curl -s https://api.testnet.firstaccess.exchange/ibc/core/channel/v1/channels/channel-0/ports/transfer
# USDC's denom trace
curl -s https://api.testnet.firstaccess.exchange/ibc/apps/transfer/v1/denom_traces/2547906198C60129474CC58DEA82084E5B6D39E993D29E345D83925C2B988A7F
# What an address may still withdraw, and the minimum
curl -s https://api.testnet.firstaccess.exchange/dydxprotocol/ibcgate/allowance/dydx1...
curl -s https://api.testnet.firstaccess.exchange/dydxprotocol/ibcgate/params
# The withdrawal limits and what is left of them
curl -s https://api.testnet.firstaccess.exchange/dydxprotocol/v4/ratelimit/list_limit_params
curl -s 'https://api.testnet.firstaccess.exchange/dydxprotocol/v4/ratelimit/capacity_by_denom?denom=ibc/2547906198C60129474CC58DEA82084E5B6D39E993D29E345D83925C2B988A7F'