What is BEP-20?
BEP-20 is the standard interface for fungible tokens on BNB Smart Chain (BSC). It defines common functions that allow wallets, exchanges, and decentralised applications to interact with those tokens.
“Fungible” means that units of the same token are interchangeable. A BEP-20 token can serve as a governance token, a utility token, or a stablecoin representation. The standard describes technical behaviour; it does not establish a token’s value or guarantee its backing.
What network is BEP-20?
The phrase BEP-20 network usually refers to BNB Smart Chain, formerly called Binance Smart Chain. Strictly speaking, BEP-20 is the token standard, and BSC is the blockchain.
BSC supports the Ethereum Virtual Machine (EVM), allowing developers to use familiar Ethereum tools and smart contract code. Its native cryptocurrency, BNB, pays network gas fees. BNB is distinct from BEP-20 tokens deployed through smart contracts.
On withdrawal screens, “BNB Smart Chain (BEP-20)” identifies the destination network. The receiving platform must support both that network and the specific token; matching the ticker alone is insufficient.
What is the BEP-20 token standard?
The BEP-20 token standard gives token contracts a common interface, derived from ERC-20. Its core functions include:
- totalSupply: Reports the token supply.
- balanceOf: Returns the balance associated with an address.
- transfer: Moves tokens from the caller to another address.
- approve: Sets how many tokens another address may spend.
- allowance: Reports the remaining spending permission.
- transferFrom: Moves tokens using an authorised allowance.
The specification also defines transfer and approval events, which applications can monitor. Token symbols and decimal precision help wallets display balances consistently. These shared rules reduce the need for separate integrations for every token.
Key characteristics
BEP-20 tokens share an interface, while their purposes and contract rules can differ:
- Fungibility: Units within one token contract are interchangeable.
- Application compatibility: Supporting wallets and decentralised exchanges can use the shared interface to read balances and process transfers.
- Contract-based identity: The contract address identifies the token on BSC. Names and tickers alone are not unique identifiers.
- Customisable supply rules: Developers may add minting, burning, or administrative controls. These features depend on the individual contract.
- BNB-based gas: Standard transactions consume network resources paid for in BNB, even when the transferred token is a different asset.
BEP-20 compliance does not mean that a contract has been audited or that its issuer is trustworthy. Minting permissions and upgrade controls can affect how a token operates.
How do BEP-20 transactions work?
A standard wallet-to-wallet transfer follows these steps:
- Select BNB Smart Chain and the token. Confirm that the recipient supports this combination.
- Enter the recipient’s address and amount. The wallet prepares a call to the token contract.
- Review and sign. Check the transaction details and estimated gas fee.
- Submit the transaction. BSC processes the contract call and includes the transaction in a block.
- Check the result. A successful transfer updates token balances and emits a transfer event. The transaction hash allows its status to be checked in an explorer such as BscScan.
A direct transfer generally does not require a separate token approval. A decentralised exchange may request approval before its contract can spend tokens on the user’s behalf.
Users ordinarily need BNB for gas. Some supported wallets or applications offer sponsored transactions, where another party covers the network cost.
BEP-20 vs ERC-20: what’s the difference?
BEP-20 and ERC-20 provide closely related interfaces for fungible tokens. Their practical differences depend partly on the blockchain where the token is deployed.
| Feature | BEP-20 on BNB Smart Chain | ERC-20 on Ethereum mainnet |
|---|---|---|
| Network | BNB Smart Chain | Ethereum |
| Native gas currency | BNB | ETH |
| Contract environment | EVM-compatible | EVM |
| Core functions | Balances, transfers and allowances | Balances, transfers and allowances |
| Symbol and decimals | Required by the BEP-20 specification | Optional in the original ERC-20 specification |
ERC-20 is also used on other EVM-compatible networks. Fees and confirmation times are properties of the underlying blockchain and transaction, rather than guarantees provided by either token standard.
Sending tokens to an identical address on another network does not bridge them. Moving value between BSC and Ethereum requires a supported bridge or a service offering deposits and withdrawals on both networks.
Summary
BEP-20 defines how fungible tokens operate on BNB Smart Chain. For transfers and crypto payments, the relevant details are the token contract, receiving network, wallet support, and gas arrangements.
FAQ
A BEP-20 address usually means a BNB Smart Chain receiving address. It starts with 0x, followed by 40 hexadecimal characters. Ethereum uses the same address format, so appearance alone cannot identify the network. A token’s contract address identifies the asset and should not be confused with the recipient’s wallet address.
Yes. USDT is available on BSC through BEP-20 representations, including Binance-Peg USDT. This is a pegged-token arrangement, distinct from direct issuance by Tether. Verify the exact token contract and supported deposit network. Tether’s protocol list identifies its directly supported deployments.
