> For the complete documentation index, see [llms.txt](https://aboutcryptotalks.gitbook.io/aboutcrypto/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aboutcryptotalks.gitbook.io/aboutcrypto/wormhole-bridge-for-exchange-users-moving-to-wallets.md). # Wormhole Bridge for Exchange Users Moving to Wallets Wormhole bridge moves tokens and messages between connected blockchains. It lets you send an asset from your own wallet on one chain and receive a corresponding asset on another, without depositing it at a centralised exchange. ### What Is the Wormhole bridge? It is a cross-chain protocol whose messaging layer lets applications coordinate actions across separate blockchains. Token transfer routes use those messages to account for assets on each chain. You authorise the transfer from your wallet rather than moving funds into an exchange account. A message is signed data, not a coin. An application can use one to trigger an action on another chain, but moving a token requires a transfer route built on the messaging layer. What you receive depends on that route. ### How Does a Token Transfer Work? A transfer locks or burns tokens on the source chain, then releases or creates their counterpart on the destination chain. Say you move 100 units of an Ethereum-issued token to Solana: before, your Ethereum wallet holds 100 units; afterward, your Solana wallet holds the corresponding token, and the original 100 cannot also be spent on Ethereum. The source-chain contract records the transfer and emits a message. The Guardian Network observes it, and a quorum of 13 of 19 Guardians signs a proof called a VAA. The destination contract verifies that proof before redemption. In a wrapped-token transfer, the original is locked and a Wormhole-wrapped token is minted elsewhere; sending it back burns the wrapped token and unlocks the original. The source transaction can succeed while redemption is still pending. An automatic route pays a relayer to submit the proof on the receiving chain; a manual route requires you to redeem it yourself. The destination transaction completes the transfer. ### Which Chains and Assets Can You Use? The Wormhole crypto bridge connects Solana and Ethereum with other chains, including Arbitrum, but a connected chain does not mean every token can use every route. Check these details for the transfer you intend to make: * Source chain: the network that holds the token in your wallet. * Destination chain: the network where you need to use it. * Asset identity: the token’s contract or mint address, rather than its ticker alone. * Received form: a wrapped representation or a native version, as the route specifies. Two tokens can display the same ticker yet have different addresses and different acceptance by apps. If the destination app requires a particular version, the received form decides whether the transfer meets your goal. A token may also need registration on the destination chain before its first wrapped transfer. ### How Do You Move Tokens From Your Own Wallet? Start with a wallet holding the token on the source chain and an address you control on the destination chain. For a transfer between connected chains, wormholebridge.org is an option for moving the token through Wormhole. Keep some of the source chain’s native token for gas, and establish how destination gas or relaying will be covered. Confirm the token address, amount, recipient address and expected received token before authorising the transfer. For this move, the Wormhole cross-chain bridge starts with the wallet that holds your token. [Wormhole bridge](https://wormholebridge.org) lets you send it to your chosen address on a connected destination chain once the route matches what you intend to receive. Keep the source transaction ID and follow the transfer through destination redemption. If an automatic transfer stalls, its signed proof may still need submission on the destination chain. Check the received token’s balance and contract or mint address before using it. ### What Will It Cost and How Long Will It Take? Expect source-chain gas plus either destination-chain gas for manual redemption or a relayer charge for automatic completion. A first token transfer on Ethereum may require a separate approval transaction, adding another gas payment. Costs depend on the chains, congestion and route, so review the quoted total and received amount before signing. Source-chain finality sets much of the wait. Full Ethereum finality is often around 15–20 minutes, while Solana typically finalises in seconds; Guardian signing and destination execution add time. Ask yourself: will the exact token version arriving on the destination chain work where you need it, and can you cover the steps required to finish the transfer? --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://aboutcryptotalks.gitbook.io/aboutcrypto/wormhole-bridge-for-exchange-users-moving-to-wallets.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.