Check this page before making a cross-chain transfer
A cross-chain transfer isn’t an ordinary transfer. Your coins first leave the source chain, then appear on the destination chain. During the time in between, you may temporarily be unable to see them on either chain. 【Conclusion】 Use only the official bridge listed in the project documentation. Make sure the source chain, destination chain, token contract, and estimated arrival time all match the documentation, then start with a small amount. Don’t use bridges sent to you in private messages. 【Analysis】 Official bridges and fake pages can look almost identical; the difference is the URL. Clicking through from the official website and clicking through from a chat history are not the same path. If you select the wrong source chain or destination chain, your assets will remain on the chain you didn’t open. Arrival times can range from a few minutes to tens of minutes. Wait as instructed in the documentation, and don’t use another bridge to transfer the same funds while you’re waiting.
Authorizations are scattered across every website you’ve used. Checking them once a week is faster than looking for them after something goes wrong.
【Conclusion】 For BSC, use Token Approvals on BscScan. For Solana, check the authorizations on your address page in Solscan. You can also use revoke.cash for both chains, but make sure to select the right chain first. Revoke any allowances you don’t recognize.
【Analysis】 The authorization list shows who can still move your tokens and how much allowance remains. Revoking an authorization doesn’t erase the history; it sends a new transaction setting the allowance to 0, so you’ll need to pay a fee and sign again. If you revoke on the wrong chain, nothing changes. If you revoke an official router you’re currently using, you’ll need to approve it again the next time you make a swap. Your tokens themselves won’t be lost.
【Step by step】 1. Open the relevant explorer and go to your address. 2. Find Approvals or Authorizations. Button names may vary by page. 3. Review each contract. Revoke any that don’t match the official documentation. 4. Refresh the list after revoking and confirm the allowance is now 0.
【What can go wrong】 Revoking on the Ethereum page and assuming the allowance on BSC is gone too. Check each chain separately.
Your Binance account and Web3 Wallet don’t share the same balance
The numbers shown in the Binance App aren’t necessarily on-chain. Coins in an on-chain wallet also won’t automatically appear in your Spot account. 【Conclusion】 Exchange balances are held in your Binance account. Web3 Wallet balances are recorded on-chain. When you connect to a DApp, you use your on-chain wallet; it won’t directly use coins in your Spot or Funding account. 【Analysis】 To exchange, authorize, or add liquidity with coins held on the exchange, you first need to withdraw them to your wallet and select the correct network. The reverse process is depositing coins from your wallet back to Binance. Customer support cannot reset a recovery phrase that you imported yourself. If Binance App’s built-in Web3 Wallet offers account recovery, follow the backup instructions in the app. Don’t treat it as the same process as an imported recovery phrase.
The quote looks fine, but the trade confirmation is right at the worst price you set. First, check how much slippage you allowed.
【Conclusion】 Slippage is the limit you publicly tell the market you’re willing to accept. The wider you set that limit, the more room there is for the execution price to move against you. The shallower the pool, the more noticeable the price difference.
【Analysis】 Before a transaction is included in a block, others can see its contents. The more deviation you’re willing to accept, the more room there is for the price to be pushed to the edge of that range before your trade executes. Setting slippage to 0 won’t prevent this; setting it too low can cause the transaction to fail while still costing you gas. A practical approach is to set slippage just high enough for the trade to go through, reduce the amount per trade, or switch to a deeper pool.
【What to do】 1. Review the slippage and price impact for this trade. 2. Set slippage back to a baseline for your next trade: 0.1% for stablecoin pairs, 0.5% for major coins. 3. Cut the amount in half and see whether the price impact drops. 4. If the impact is still high, slippage isn’t the problem—switch pools or split the trade into smaller batches.
【Pitfall】 After a bad execution, keep increasing slippage in the hope that the next trade will “definitely go through.” You’re just widening the limit.
Authorization, swaps, and adding liquidity: What are the three signatures for?
Three wallet pop-ups appear in a row on one page, each for a different action. 【Conclusion】 The first is usually authorization, where you set an allowance. The second is the swap, executed according to the quoted price and minimum amount received. Adding liquidity deposits both tokens into the pool at the same time. Check the amount separately each time. 【Analysis】 Authorization succeeds: the coins are still in your wallet; the contract has only been granted permission to transfer them. The swap succeeds: one token decreases and the other increases. Adding liquidity succeeds: both tokens decrease, and you receive pool shares. To keep the process flowing smoothly, the website will show three pop-ups in sequence. If you click through the first one too quickly, you may not read the next one carefully.
Keep your mnemonic phrase somewhere you’ll remember, but where others can’t figure it out from the paper.
【Conclusion】 If you can’t find your backup, it’s as good as having no backup. Choose a place you’ll remember, and don’t write it down on paper.
【Follow these steps】 1. Choose a fixed place 2. Don’t write the location on the same piece of paper 3. Check every few months to make sure it’s still there