Swap troubleshooting: 'insufficient BNB', unknown errors, slippage and routing

Table of contents

• Common swap error messages (and what people search)
• Quick pre-flight checks (step-by-step)
• Fix: "insufficient BNB" and gas-fee problems
• Fix: generic "unknown error" or "swap failed" messages
• Slippage, routing and why a swap times out
• Special case: "swap to smart chain disappeared" (wrong network or token standard)
• Preventive steps and safety checklist
• Quick troubleshooting table
• FAQ
• Conclusion and next steps

---

Common swap error messages (and what people search)

Users often land here after Google queries like "insufficient bnb balance for gas fee trust wallet", "trust wallet swap unknown error", "trust wallet swap not working" or "swap failed trust wallet". Those phrases usually describe three distinct problems:

• You don't have enough native token for gas (often BNB on Binance Smart Chain).
• A generic or "unknown" error that hides a routing, liquidity, or RPC issue. (Yes, vague errors are the worst.)
• Slippage or routing that causes the transaction to revert.

What I’ve found working with in-wallet swaps is that the simplest fix is often a simple balance check. But some failures need a longer checklist.

![screenshot-placeholder]

(Placeholder: screenshot showing a typical "insufficient BNB" error.)

Quick pre-flight checks (step-by-step)

Before retrying a swap, run this short checklist. It saves time.

1. Confirm you have native chain gas funds. For BSC swaps that means BNB (not BEP2 wrapped tokens).
2. Verify the network selected matches the token standard (mainnet vs Smart Chain, etc.).
3. Check token balance and pending approvals (an approval can block a follow-up swap).
4. Try a tiny test swap (like $1–$5) to reproduce the error safely.
5. Capture the transaction hash and any on-screen error; keep it for support.

If you want detailed setup steps for the in-app swap UI, see the in-wallet-swap guide.

Fix: "insufficient BNB" and gas-fee problems

Error message: "insufficient BNB" or search: "you don't have enough to cover network fees trust wallet".

Why this happens: the swap needs the chain's native token to pay gas. Wrapped tokens or LP tokens do not cover gas. Short one-liners: check the native balance.

Step-by-step fix:

1. Open your wallet and view the native token balance (BNB on BSC, ETH on Ethereum).
2. If balance is low, top up: transfer from an exchange or wallet, or buy via the app (if supported).
3. If the in-app buy fails (many users search "not able to buy bnb on trust wallet"), send a small amount from an exchange; that’s more reliable.
4. Once you have a small buffer (I keep ~0.005–0.01 BNB for routine swaps), retry.

And if you accidentally sent the wrong token type (for example BEP2 vs BEP20), see the section below on tokens that appear to have disappeared.

Fix: generic "unknown error" or "swap failed" messages

Generic errors can come from several sources. They might mean the DEX reverted the trade, the aggregator hit a bad route, your RPC node timed out, or the gas estimate is wrong.

Steps to diagnose and fix:

• Increase slippage slightly (0.5% → 1% or 1% → 3%) for low-liquidity tokens.
• Use a different connection method: try the in-app DApp browser, or connect the same account via WalletConnect to a desktop DEX. (But watch for phishing—always double-check the URL.)
• Clear any pending approvals or stuck transactions (link: revoke-token-approvals).
• Switch RPC/node if your wallet allows a custom node—some public nodes throttle requests under load.
• If the transaction reverted on-chain, look up the transaction hash on a block explorer; the revert reason sometimes helps.

But don’t just pump up gas fees blindly. Overpaying doesn't help if the swap reverts for other reasons.

Slippage, routing and why a swap times out

Slippage is the difference between quoted and executed price. If price impact or slippage limits are too tight, the DEX reverts the trade to protect you.

How to adjust slippage (general steps):

1. Tap the gear or settings in the swap UI.
2. Increase the slippage tolerance in small increments.
3. For illiquid tokens you may need higher tolerance (3–12%), but that increases front-running and sandwich risk.

Routing: aggregators try multi-hop paths to find the best price. More hops can mean more gas and more points of failure. If the wallet shows route details, prefer shorter routes when possible. If it doesn't, try a different aggregator via WalletConnect.

Special case: "swap to smart chain disappeared" (wrong network or token standard)

Many users see tokens "vanish" after a swap or transfer because the token exists on multiple standards (BEP2, BEP20, ERC20, etc.) and was sent to the wrong network address. That often shows up as "trust wallet swap to smart chain disappeared" in searches.

What to do:

• Double-check the token standard and the destination address.
• Use add-custom-token to manually add the token contract/asset if the UI hides it.
• If you really sent to the wrong chain, recovery may require a bridge or help from the receiving wallet's custodial service (if applicable). See bridging-cross-chain and troubleshooting-token-not-showing.

Preventive steps and safety checklist

• Revoke large/unlimited token allowances regularly. See revoke-token-approvals.
• Use a small test swap before committing large amounts.
• Keep a gas buffer (native token) in every account you actively use.
• Store your seed phrase offline and read backup-recovery.
• Run transaction simulations where available (see transaction-simulation-safety).

But remember: a hot wallet trades convenience for some security risk. If you're moving large sums, consider combining with a hardware wallet (see ledger-hardware for ideas).

Quick troubleshooting table

Symptom	Likely cause	Quick fix
"Insufficient BNB"	Native gas token too low	Transfer or buy small amount (see buy-crypto)
"Unknown error" / "Swap failed"	Routing or RPC issue	Increase slippage slightly, switch RPC or try WalletConnect
Token disappeared after transfer	Wrong network/token standard	Add custom token or use recovery steps (see above)
Pending or stuck tx	Low gas or nonce issue	Resend with higher gas or cancel if supported

FAQ

Q: Is it safe to keep crypto in a hot wallet?
A: Hot wallets are convenient for active DeFi use, but they carry higher risk than cold storage. I use a hot wallet for daily swaps and a hardware wallet for larger holdings. See security-features for defensive options.

Q: How do I revoke token approvals?
A: Use the wallet's approvals tool or a trusted revoke service (link: revoke-token-approvals). Revoke the ones you don’t actively use.

Q: What happens if I lose my phone?
A: You can restore with your seed phrase or follow steps at lost-phone-recovery. Keep your seed phrase offline and never share it.

Conclusion and next steps

Swap failures are frustrating, but most are fixable by checking gas balances, adjusting slippage, and confirming network/standards. When a swap reports "insufficient BNB balance for gas fee trust wallet" or a vague "trust wallet swap unknown error", follow the pre-flight checklist above before retrying.

If you want a step-by-step walkthrough of in-app swaps or how to top up BNB, see the in-wallet-swap and buy-crypto guides. If approvals are part of the problem, head to revoke-token-approvals.

Need more help? Check the troubleshooting hub for deeper recovery guides and examples of common mistakes (I’ve made some myself — learned the hard way). And if you try a fix, keep the tx hash and screenshots handy; they speed support responses.