How to Bridge Tokens Between Two Avalanche Subnets Without Going Back to C-Chain

16 October 2026

You can bridge tokens directly between two Avalanche subnets without routing through the C-Chain, provided both subnets support Avalanche Warp Messaging (AWM). The process uses native inter-subnet transfers rather than a separate bridge contract, so you avoid C-Chain gas fees and extra transaction steps.

When direct bridging is possible

Not every subnet pair supports direct token transfers. The two subnets must both be registered with the Avalanche Platform Chain (P-Chain) and have AWM enabled. Most subnets launched after the Cortina upgrade support this, but older or custom subnets may not. You also need the destination subnet to accept the token you want to send - either as a native gas token or as an ERC-20 that the subnet’s VM recognizes.

If both subnets meet these conditions, you can use a cross-subnet transfer through a wallet or dApp that implements AWM. The transfer happens via the P-Chain as a message relay, not as a token movement through a bridge contract.

Step-by-Step: direct subnet-to-subnet transfer

The exact interface varies by wallet and dApp, but the general steps are the same.

Step 1: Confirm Both Subnet RPCs Are Added to Your Wallet

You need the correct RPC endpoints for both the source and destination subnets loaded in your wallet. If you have not added them already, follow the same process as adding any custom Avalanche subnet RPC to MetaMask or a compatible wallet. Each subnet has its own chain ID and RPC URL - using the wrong one will fail or send tokens to the wrong place.

Step 2: Initiate the Transfer From the Source Subnet

In your wallet, select the source subnet network. Look for a “Send” or “Transfer” option that offers a cross-subnet destination. Some wallets label this “Cross-Subnet Transfer” or “AWM Transfer.” Enter the destination address - which is the same address format as on the C-Chain, because Avalanche subnets share the same address space - and the amount.

The wallet should let you choose the destination subnet from a list of known subnets. If your destination subnet does not appear, you may need to add its RPC manually first.

Step 3: Confirm the Source Subnet Transaction

The wallet will prompt you to approve a transaction on the source subnet. This transaction burns or locks the tokens on the source side and generates a Warp Message. You pay gas in the source subnet’s native gas token. If the source subnet uses a custom gas token (not AVAX), make sure you have enough of that token to cover the fee.

Step 4: Wait for the Warp Message to Be Delivered

The P-Chain validators relay the Warp Message to the destination subnet. This usually takes a few seconds to a couple of minutes, depending on subnet validator responsiveness and network congestion. You do not need to do anything during this wait - the destination subnet will pick up the message automatically if the transfer is set up correctly.

Step 5: Claim the Tokens on the Destination Subnet

Some wallets and dApps require a second transaction on the destination subnet to claim the incoming tokens. This transaction mints or unlocks the tokens on the destination side. It costs gas in the destination subnet’s native token, so you need a small balance of that token before you start.

Other implementations handle the claim automatically - the tokens appear in your wallet without a separate approval. If the tokens do not show up after a few minutes, check whether the destination subnet requires a manual claim step. The wallet or dApp documentation for that specific subnet should state which method it uses.

What can go wrong

The most common failure point is insufficient gas on the destination subnet for the claim transaction. If you do not have any of the destination subnet’s native gas token, you cannot complete the claim. In that case, you need to acquire a small amount of the destination gas token - possibly by bridging a minimal amount from the C-Chain first, then using that to claim the rest.

Another issue is incompatible token types. If the source subnet sends an ERC-20 token and the destination subnet does not recognize that token contract, the transfer may appear to succeed but the tokens will not be usable. Check whether the destination subnet has a bridge or swap for that specific token before transferring.

When you still need the c-chain

Direct subnet-to-subnet bridging does not work if either subnet does not support AWM, or if the destination subnet has no mechanism to accept the token you want to send. In those cases, you must route through the C-Chain: send from the source subnet to the C-Chain, then from the C-Chain to the destination subnet. This adds two C-Chain transactions and their associated gas costs.

Some older subnets also require a manual approval step on the C-Chain to enable the bridge contract, even if the actual transfer uses AWM. Check the documentation for each subnet pair before assuming a direct path exists.

Checking Subnet Compatibility

Before attempting a direct transfer, verify that both subnets are listed as AWM-enabled on the Avalanche network status page or the subnet’s official documentation. If a subnet was launched before the AWM standard was adopted and has not upgraded, direct bridging is not available. In that case, the C-Chain route is your only option.

Back to avalanche