Swim Docs
  • Introduction
  • 📖Tutorial
    • Swap
      • Solana <> Solana
      • Solana -> BNB/ETH
      • BNB/ETH -> Solana
      • BNB/ETH <-> BNB/ETH
    • Add/Remove Liquidity
    • FAQ
    • Metapool
    • Polkadot and Kusama Ecosystem
      • Karura Guide
      • Acala Guide
  • ⚙️Troubleshoot
    • Diagnosing Failed Swap Transactions
      • Solana -> BNB/ETH
      • BNB <-> ETH
      • BNB/ETH -> Solana
      • Metapool Transactions
    • Wormhole
      • Wormhole-wrapped Tokens
      • Unconfirmed Wormhole Transactions
    • Common error messages
  • Swim Protocol
    • Roadmap
    • Swim Team
    • Audits
    • Contracts
    • Investors
  • Tokenomics
    • SWIM Token
  • Links
    • Community & Contacts
    • Whitepaper
Powered by GitBook
On this page
  1. Troubleshoot
  2. Wormhole

Wormhole-wrapped Tokens

What to do with Wormhole-wrapped tokens?

PreviousWormholeNextUnconfirmed Wormhole Transactions

Last updated 3 years ago

In rare situations, you might receive a Wormhole-wrapped token in your wallet. This is because somewhere along the interaction, there was a failure and the Wormhole-wrapped token has not entered the Wormhole bridge yet.

If this occurs, try the steps outlined in which involves retrying or resuming the swap interaction. If you have attempted this without success, visit the site to transfer the token into it's native form on the destination chain.

In the following example, the user received Wormhole-wrapped-bnb-chain BUSD in their Phantom wallet but wanted to convert it into native BUSD on BNB Chain. See below the form from Wormhole to fill out. Be sure to select the correct target chain. If you select Ethereum as the target chain in this example, your Wormhole-wrapped-bnb-chain BUSD will arrive as a Wormhole-wrapped tokens on Ethereum.

⚙️
Diagnosing Failed Swap Transactions
Wormhole-Transfer