BSC Mainnet
Real fundsFor live transactions, dApps, and staking.
- Network name
- BSC Mainnet
- Chain ID
- 56
- RPC URL
- https://bsc-dataseed.bnbchain.org
- Symbol
- BNB
Clear, step-by-step answers for the seven problems BNB Chain users run into most — networks and RPCs, bridge errors, faucet claims, staking, migrations, swaps and reverted transactions.
Seven common problems, each with the usual causes and the official links you need to verify them.
Use these values in MetaMask, Trust Wallet, or any EVM wallet. Mainnet uses real BNB; testnet tBNB has no value.
For live transactions, dApps, and staking.
For development and testing with free tBNB.
Public RPC endpoints can rate-limit under heavy use. If one is slow or returns errors, switch to another official endpoint from the BNB Chain docs — never one sent to you in a DM.
No legitimate support agent from BNB Chain, a wallet, a bridge, or a DEX will ever ask for your seed phrase, private key, wallet password, or a remote screen session. This site never connects to your wallet and never asks you to sign anything. If someone does, it’s a scam — stop the conversation.
The two most common reasons behind each issue — check these first before opening a ticket.
Wrong chain selected in the wallet, or the chosen RPC endpoint is rate-limited or offline.
The source transaction is still pending, or the bridge relayer simply has a backlog.
The address holds less than 0.002 BNB on mainnet, or the 24-hour claim window has not reset.
Below the 1 BNB minimum, or the validator is inactive, jailed, or already at its delegation cap.
The migration contract is not verified on BscScan, or an unlimited approval goes to an unknown spender.
Slippage is set too tight, or the trade is large enough to push price impact past the liquidity.
A missing token allowance, or a gas limit too low for the route the contract needs to execute.
Open the failed transaction on BscScan — the revert reason usually names the exact problem.
Short answers to the things that are usually not obvious the first time.
Never. A seed phrase or private key gives full control of your wallet. Any person or website requesting one is attempting to steal your funds — there are no exceptions, including “wallet validation”, “sync”, or “rectification” procedures.
Gas pays validators for the computation they performed. A transaction that reverts still consumed computation, so the gas fee is charged even though the token transfer did not happen. This is how EVM chains work — it is not a support issue and cannot be refunded by the network.
Usually between 5 and 30 minutes, depending on the bridge, the source chain’s finality time, and relayer load. Transfers can occasionally take longer during congestion. Always check the bridge’s own status tracker with the source transaction hash before resending.
Start with the official endpoint (mainnet https://bsc-dataseed.bnbchain.org). If it is slow, switch to another endpoint from the official BNB Chain documentation, or use a reputable RPC provider. Never use an endpoint you received from a stranger.
No. Once a transaction is confirmed on-chain it cannot be undone. What you can do is revoke token approvals you no longer need, using the token approval checker on BscScan or a reputable revocation tool. If a transaction is still pending, you may be able to replace it with the same nonce and a higher gas fee.
Use the official faucet at bnbchain.org/en/testnet-faucet. The requesting address generally needs at least 0.002 BNB on BSC Mainnet, and claims are limited to once every 24 hours (currently 0.3 tBNB). tBNB has no financial value.
Most issues can be answered from the transaction hash alone. Include it and we can skip the back-and-forth.
Never include your seed phrase or private key — not in this form, not in email, not in any chat. No real support process needs them.