How to use Uniswap on BSC? (BNB Chain Setup)

Connecting MetaMask to BSC

1. Open MetaMask and click the network dropdown in the top-right corner.

2. Select “Custom RPC” and enter the BSC Mainnet details: Network Name: BSC Mainnet, New RPC URL: https://bsc-dataseed.binance.org/, Chain ID: 56, Symbol: BNB, Block Explorer URL: https://bscscan.com.

3. Confirm the settings and save. The wallet will switch to BSC, displaying BNB balance if funds are present.

4. Ensure sufficient BNB remains for gas fees—transactions on BSC require BNB, not ETH.

5. Verify connection by checking transaction history on BscScan using your wallet address.

Accessing Uniswap Interface on BSC

1. Navigate to https://app.uniswap.org in a desktop browser with MetaMask installed.

2. Click the wallet icon in the top-right corner and select MetaMask to connect.

3. Approve the connection request in MetaMask. The interface will display your BSC wallet address.

4. Confirm that the network indicator shows “BSC Mainnet” or “BNB Smart Chain”—not Ethereum or another chain.

5. If the interface defaults to Ethereum, manually change the network via the chain selector near the wallet button.

Swapping Tokens Using Uniswap on BSC

1. Click the “Swap” tab and input the token you wish to trade in the “From” field.

2. Click the token symbol next to “To”, search for the target token, and select it from the list.

3. Enter the amount and review the price impact, slippage tolerance, and estimated gas fee shown below.

4. Adjust slippage tolerance if needed—common values range from 0.5% to 2% depending on token liquidity.

5. Click “Swap”, confirm the transaction in MetaMask, and wait for block confirmation on BscScan.

Adding Liquidity to BSC Pools

1. Go to the “Pool” tab and click “Add Liquidity”.

2. Select two tokens compatible with BSC—both must be deployed on the BNB Smart Chain.

3. Input amounts for both tokens; the interface auto-calculates the ratio and displays pool share percentage.

4. Review the deposit preview including fees, impermanent loss warning, and pool token receipt.

5. Confirm the transaction in MetaMask and wait for confirmation—liquidity tokens will appear in your wallet.

Troubleshooting Common Issues

1. If Uniswap fails to load token balances, refresh the page and reauthorize token permissions in MetaMask.

2. When swaps revert, check if the token contract is verified on BscScan and whether it implements standard ERC-20 functions.

3. Slippage errors often occur with low-liquidity tokens—reduce swap size or increase slippage tolerance up to 5%.

4. Failed add-liquidity transactions may stem from outdated token decimals or incorrect allowance—revoke and reset approvals via MetaMask’s asset settings.

Frequently Asked Questions

Q: Can I use the official Uniswap V3 contracts directly on BSC?A: No. Uniswap Labs does not deploy official V3 contracts on BSC. Third-party forks like PancakeSwap or Biswap operate there instead. The Uniswap interface on BSC connects to community-deployed forks—not audited or maintained by Uniswap Labs.

Q: Why does Uniswap show “Insufficient liquidity” for a token listed on BscScan?A: Token listing on BscScan only confirms contract deployment—not liquidity provision. Liquidity must be added to a compatible AMM pool separately. Absence of trading pairs or reserves triggers this message.

Q: Do I need to approve every token before swapping on BSC via Uniswap?A: Yes. Each new token used in a swap requires a one-time approval transaction. This grants the router contract permission to transfer your tokens, and consumes BNB for gas.

Q: Is my private key exposed when connecting MetaMask to Uniswap on BSC?A: No. MetaMask signs messages and transactions locally. Uniswap never receives or stores private keys. Connection only shares your public address and network state.