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. Diagnosing Failed Swap Transactions

BNB <-> ETH

PreviousSolana -> BNB/ETHNextBNB/ETH -> Solana

Last updated 3 years ago

In this example, a user swaps their BUSD from BNB Chain to USDT on Ethereum. Two Wormhole transactions occurred here: first BUSD BNB enters the Wormhole bridge and later Wormhole-wrapped USDT gets redeemed via the bridge into USDT on Ethereum. If you see these transactions where the token is entering the Wormhole bridge but there is no corresponding transaction where it is leaving the bridge, please refer to "" to resolve the problem.

Once the token arrives on the Solana side, it will interact with the pool to arrive at the desired native token for users. If your swap failed and you only see the transaction where your native token is converted to a Wormhole-wrapped token, please refer to “” to resolve the problem.

⚙️
Unconfirmed Wormhole Transactions
Wormhole-wrapped Tokens
bscscan
solscan
etherscan