How to Move Assets to and from WAX With Cross-Chain Bridges

WAX is an EOS-compatible delegated proof-of-stake blockchain, launched in 2017, that uses the WAXP token and is built around e-commerce and NFT collectibles. Because it is a separate chain from Ethereum and most other networks, a token that lives elsewhere cannot be used on WAX until a WAX-side version of it exists.

There are three common routes. A cross-chain bridge locks or burns tokens on the source chain and releases or mints an equivalent on the destination. A centralized exchange can credit WAXP to your WAX account when you withdraw from its platform. A native WAX transfer moves assets that already exist on WAX between accounts.

This guide concentrates on bridges, but it also covers the points where bridges and exchanges meet, because many users combine the two. Before any transfer, settle three questions: which asset you hold, which network it currently sits on, and whether a WAX version of that asset is supported at all. Most failed transfers trace back to one of those answers being wrong.

Before you send anything, confirm three details.

First, confirm the exact token and the chain it lives on. The same ticker can exist on several networks as different tokens, and a bridge may support only one of them.

Second, confirm your WAX account name. WAX uses named accounts rather than long hexadecimal addresses, so a single wrong character can send funds to a place you cannot recover them from. Copy the name from your wallet instead of typing it, and compare the first and last characters before you confirm.

Third, check that your account can perform actions on WAX. Like other EOS-style chains, WAX uses a resource model in which accounts need RAM, CPU and network bandwidth to submit transactions. Many wallets manage this in the background, but if a transaction fails for resource reasons, the WAX documentation explains how to add resources. Keep a small amount of WAXP available so you can pay for network activity once the transfer arrives.

Finally, plan a test. Send a small amount first, wait for it to arrive and confirm it, then move the rest. This costs a little time and some fees, but it limits the damage from a wrong address, a wrong network or an unsupported token.

Each route suits a different starting point. Use this table to compare them before you choose.

Route	Best for	What to check first
Cross-chain bridge	Moving a supported token from another chain into WAX, or back	Supported token list, WAX as a destination, fees and minimum amounts
Exchange withdrawal	Getting WAXP into a WAX account from an exchange account	WAXP listed, correct network selected, memo or tag requirements
Native WAX transfer	Moving assets already on WAX between accounts	Recipient account name, memo field, resources on the sending account

Bridge protocols such as Across and LayerZero V2 are general cross-chain infrastructure. Whether either one offers a route to WAX for a particular token is something to confirm on that bridge's own documentation and in WAX resources, since supported chains and tokens change over time.

No route is automatically better. A bridge may suit a token you hold on another chain, while an exchange may be simpler if you already have WAXP on that platform. Compare the total cost, the number of steps and the expected waiting time for each option before you commit.

Follow these steps when moving a supported token from another chain onto WAX. Labels in bridge interfaces vary, but the sequence is broadly the same.

1. Open the bridge through its official documentation or a bookmark you created yourself, not a link from an advertisement or a message.
2. Connect your source-chain wallet and select the token and the source network.
3. Select WAX as the destination and enter your WAX account name. Read it back once before continuing.
4. Enter the amount. Note any minimum, maximum and estimated fee the interface shows.
5. If the bridge asks for a memo or other field, enter exactly the format it specifies.
6. Review the summary, then approve any token permission at the smallest amount the interface allows, and sign the transaction.
7. Wait for the source-chain confirmation and for the bridge to process the transfer.
8. Check your WAX account balance in your wallet, and confirm the transaction in a WAX block explorer using your account name.

Keep the transaction hash from the source chain. You will need it if the transfer stalls or if you contact support.

Moving assets off WAX follows the same logic in reverse, but there are a few extra checks.

1. Make sure your WAX account holds enough WAXP to pay for the transaction that sends funds out.
2. Open the bridge and select WAX as the source network. Confirm the token you hold on WAX is one the bridge supports for that route.
3. Select the destination chain and enter the address on that chain. Confirm it is the correct format for that network, because a WAX account name will not work as a destination address on other chains.
4. Enter the amount and review the fee estimate, minimums and any delay the bridge states.
5. Sign the transaction from your WAX wallet. Keep the transaction ID.
6. Wait for the bridge to confirm the WAX side, then for the destination chain to release or mint the asset.
7. Check the balance in the destination wallet and confirm the transaction in that chain's explorer.

Some bridges return a wrapped asset on the destination chain that you may need to convert again before you can use it there. Read the summary carefully before you sign, and check which version you will receive.

Some destinations require more than an account name. Exchange deposit addresses are the most common example, and some bridges and payment services also use a memo field. A memo is a short piece of text attached to a transaction. It tells the receiving system where to credit the funds.

If the memo is missing, wrong, or includes extra spaces or characters, the funds may be credited to the wrong account or held until someone resolves them by hand. Recovery can be slow and is not guaranteed.

To avoid this, read the deposit page or bridge form for a memo or tag field before you send. Ask the receiving service what format it expects if the instructions are unclear. Copy the memo exactly, and do not reuse one from a previous transfer unless the instructions say it is permanent.

Treat a memo as mandatory when a page shows one, even if it seems like an extra step. Then run a small test transfer to confirm the full path before you send the amount you intended to move.

Fees and timing depend on the bridge, the source and destination chains, and network congestion at the time you transfer. Because these change often, this guide does not quote figures. Check the interface you use at the time of transfer, and look at the bridge's official documentation for its published fee model.

Bridge interfaces usually show an estimated fee before you sign. Read what it covers. Some fees are charged on the source chain, some are taken from the amount you send, and some are paid in a token you may not hold yet. The WAX side of a transfer may also require a small amount of WAXP for network activity.

To track a transfer, keep three pieces of information: the source transaction hash, the bridge's transfer or order reference if it gives one, and your WAX account name. Use the source chain's block explorer to confirm the first step. Use a WAX block explorer with your account name to check the arrival. Many bridges also provide a status page that shows which stage a transfer is in.

If a transfer takes longer than the bridge says it should, do not send it again. Contact the bridge's support channel with the transaction references and wait for a reply.

Most transfer problems fall into a small set of patterns. Each one has a practical response.

• Wrong network selected: the funds may be sent to a chain where the token is not supported. Check the network in your wallet before you approve anything.
• Unsupported token: the bridge does not offer a WAX route for that asset. Choose a different route or a different token version.
• Missing or incorrect memo: the funds may not be credited. Contact the receiving service with the transaction ID.
• Below minimum amount: the bridge may reject the transfer or hold it. Check the minimum on the interface before you sign.
• Insufficient resources on WAX: the transaction fails on the WAX side. Add resources through the WAX documentation method and retry.
• Transfer stuck in progress: keep the transaction references and contact the bridge's support channel.

In every case, stop before repeating the transfer. A repeated send can duplicate funds on one side or lose them on the other. Record what happened, and use the official support channel of the bridge or service involved.

Bridges and wallets are frequent targets for scams, so apply the same discipline each time.

• Navigate to bridges only through official documentation or bookmarks you saved yourself. Search ads and unsolicited direct messages often lead to copies of real sites.
• Check the token contract or asset identifier against the official source before you approve a permission.
• Limit token approvals to the amount you need, and revoke approvals you no longer use with a reputable wallet tool.
• Never share your seed phrase or private keys with anyone, including someone claiming to be support. Legitimate support will not ask for them.
• Be cautious of pages that ask you to connect a wallet to 'verify' a transfer or claim a refund.
• Store your WAX account recovery details offline, and check that the account name you enter matches the one you control.

If you believe you have signed something malicious, move remaining assets to a new wallet you set up with a freshly generated seed phrase, and report the incident to the affected service.

Once funds arrive on WAX, you may want to use them in a WAX application or move them again. Before doing that, confirm the balance in your wallet and note the transaction ID so you have a record.

If you plan to swap the asset later, check which networks the exchange or decentralized exchange you use supports, and whether the WAX version of the token is listed there. Decentralized exchanges such as Uniswap V3 operate on chains outside WAX, so a WAX-side token may need a different route. Look at each platform's supported-network page before assuming a swap is possible.

If you keep funds on WAX for a long period, review the resource situation of your account, and check the WAX documentation for any changes to how accounts and resources are managed. Because chains and bridge support evolve, revisit the supported-token lists of the bridges you use rather than relying on a list you saved earlier.

Finally, keep the habits from this guide: verify, test with a small amount, copy account names and memos exactly, and keep your transaction references until the transfer is complete.