SUSHI to BNB: Swap SushiSwap on Ethereum for BNB on BSC, No KYC

SUSHI is the governance token of SushiSwap and an ERC-20 token on Ethereum. BNB is the native coin of BNB Smart Chain. The two chains are separate ledgers, even though their addresses look identical, so this swap is a real change of network as well as a change of asset.

There is no bridge and no wrapped token in the middle. Your SUSHI is deposited on Ethereum, and the BNB you get is ordinary BNB on BNB Smart Chain, the same coin anyone else there uses to pay gas.

One wallet can often do both sides. MetaMask and Rabby hold Ethereum and BNB Smart Chain accounts under the same 0x address, and a Ledger connected to either of them works the same way. You just switch the network between sending and checking the payout.

An ERC-20 transfer costs gas, and on Ethereum gas is paid in ETH. The SUSHI balance cannot pay for its own transfer, so the sending address needs some ETH beside the tokens. Without it, the wallet shows an insufficient-funds warning and nothing is sent.

Ethereum gas moves with demand, and a token transfer costs more than a plain ETH send. Quieter hours are usually cheaper. Let the wallet suggest the fee rather than cutting it down by hand, because a transfer stuck at a very low fee holds up the swap.

The deposit confirms in about 2 to 5 minutes on Ethereum. You can follow it on Etherscan by pasting your transaction hash; the SUSHI amount appears under the token transfers line, while the ETH value of the transaction reads zero.

This is the classic mistake on this pair. A BNB Smart Chain address and an Ethereum address are both 0x followed by 40 hexadecimal characters. If you send SUSHI from Ethereum straight to your own BNB address, the transfer goes through without a warning, but the tokens just land at that address on Ethereum. They never turn into BNB.

The way to get BNB is to send the SUSHI only to the one-time deposit address the box shows, and put your BNB address in the receive field. That field expects an address you control on BNB Smart Chain, from Trust Wallet, MetaMask, Rabby or similar.

Also send from Ethereum mainnet itself. SUSHI sitting on a layer-2 or another network is a different token contract from the one this deposit expects, so move it to mainnet first if that is where your balance is.

Read the gas row twice. Before the swap you need ETH to send. After the swap you hold BNB, which is the gas coin of the receiving chain, so the BNB can be moved, staked or swapped on BNB Smart Chain straight away without any top-up.

Some SUSHI holders simply want out of a DeFi governance token and into the base coin of a busy chain. Others are tired of paying Ethereum gas on every small move: BNB Smart Chain fees are usually lower, so a balance there is cheaper to manage day to day.

BNB also opens the apps and pools on BNB Smart Chain without first getting gas from elsewhere, because the asset you receive is the gas coin itself. That makes it a tidy end point if your next steps happen on BSC.

If you would rather stay on Ethereum, SUSHI to ETH keeps everything on one network, and SUSHI to USDT ERC20 gives you a dollar balance there. To come back to SUSHI later, the BNB to SUSHI page runs the reverse.

Enter a SUSHI amount and the box shows the BNB you will receive after fees, quoted from aggregated liquidity from leading crypto markets, with this pair's minimum and maximum. The rate floats until your Ethereum deposit confirms; most swaps finish within minutes after that.

If a swap cannot be completed, the coins are refunded to the sender address you entered, on Ethereum. Use the address that actually holds your SUSHI, not an exchange deposit address.

Save the swap ID when the status page opens. The SUSHI deposit is visible on Etherscan and the BNB payout on BscScan. If the deposit shows as successful but the status page has not moved for a long while, email support@ghostswap.io with the swap ID and the Ethereum transaction hash, and hold off on sending again.