The commonly referenced USDT contract on BNB Smart Chain represents Binance-Peg USDT. BEP-20 describes its token interface; it does not establish direct issuance by Tether.
This distinction affects how to read backing claims, token metadata and compatibility. The network's low-cost reputation cannot substitute for identifying the actual asset.
The commonly referenced BSC-USD contract
The BSC contract 0x55d398326f99059fF775485246999027B3197955 is identified as Binance-Peg USDT in BNB Chain's token definitions. It uses 18 decimals. The contract identifies the token, not a user's receiving account.
The same contract may appear with BSC-USD or USDT labels in different interfaces. Names and logos are display metadata. The full network and contract identity provide the stronger match.
Decimal precision controls how integer balances are displayed. It does not set the token's dollar value or prove its backing. Copying another chain's decimal setting can produce a misleading displayed amount even when the contract identity is otherwise correct.
Primary evidence: BNB Chain's token definitions. Compare the asset-specific entries in Tether's issuer directory; the presence of a BNB section does not make every stablecoin on BSC direct Tether issuance.
A pegged representation has an additional dependency
The underlying reference asset and the representation on BSC are distinct layers. An issuer's reserve report about USDT does not by itself establish the supply or collateral handling of a third party's pegged token.
Useful questions include who operates the representation, where its backing is held, which obligations apply and how the mechanism is documented. A token price close to one dollar does not answer those questions.
Self-custody means controlling the keys that authorize activity from your account. It does not remove the representation's external dependencies. Custody of the wallet and custody of the backing are separate subjects.
Collateral disclosures need an observation date, entity and scope. This guide does not assert a current collateral ratio. For general mechanism risks, read Ethereum's bridge models and the USDT identity guide.
BEP-20, BSC and the 0x address overlap
BNB Smart Chain is the blockchain; BEP-20 is a token interface used there. Native BNB is the ordinary fee asset. A wallet may use BEP20 as a network label, but that shorthand should not blur the distinction between the chain and token.
BSC mainnet uses chain ID 56. Ethereum and Arbitrum use similar 0x address syntax while maintaining separate network state. An address that passes format validation has not thereby selected the intended chain.
A token-contract address is also shaped like a 0x address. That does not make it interchangeable with a personal account. The address's role and the token identity both matter.
Changing the selected chain only changes the context queried by the wallet. It does not move a balance across chains. Source: official BSC network identifiers.
Gas in BNB, with explicit units
Ordinary BEP-20 execution uses BNB for gas. A USDT balance and a native BNB balance are different entries. A large token holding does not establish that an account can cover ordinary execution costs.
Gas consumed depends on the operation and contract state, while effective gas price determines the cost per unit. Provider charges can be additional. A permanent cents-per-operation claim hides these variables.
For illustration only, 0.0001 BNB at a hypothetical BNB price of $600 equals $0.06. This is a unit conversion, not a current network estimate. A different native amount or price assumption changes the dollar result.
Use a current estimate for the actual operation and keep the network charge separate from any provider quote. Sponsored-fee features are product-specific; BEP-20 itself does not promise that USDT pays its own gas. See the BNB guide for native-asset mechanics.
BEP-2 is a retired-chain question
BEP-2 belonged to BNB Beacon Chain, which is retired. It is not an alternative current BSC route. The official sunset plan's November 19, 2024 fork schedule and the explorer's December 3 recorded shutdown describe different historical events.
A legacy balance cannot be relocated by renaming its network in a wallet. Advice to perform an ordinary swap or exchange round trip is not a verified recovery method for a retired-chain asset.
Official recovery eligibility is conditional, including cross-chain binding or mirroring. The hosted recovery tool was discontinued effective July 1, 2026 according to the phase 3 notice. Current documentation describes the self-service approach; this article does not reproduce signing or setup instructions.
Read the current phase 3 notice and eligibility documentation. No general page can guarantee recovery of every old asset.
Investigating an unexpected balance or status
First distinguish a display issue from chain execution. A wallet can hide a token or query a different network. The public contract and account records provide evidence without requiring a private key.
A transaction receipt can show successful or failed execution. Token event details identify the asset involved. A same-symbol token from another contract is a different finding from an authentic token omitted by the wallet display.
Successful chain execution does not certify a third party's internal account recognition or recovery policy. Preserve the public transaction reference, network and contract identity when clarifying an issue.
Be cautious about new signing or approval requests presented as a way to view a balance. An explorer only needs public information. Compare the Ethereum asset guide and network comparison for the broader EVM and representation distinctions.
Frequently Asked Questions
Is the common BSC-USD contract direct Tether issuance?
It is identified as Binance-Peg USDT. The pegged representation must be distinguished from the underlying issuer's direct issuance.
How many decimals does that contract use?
The commonly referenced 0x55d398326f99059fF775485246999027B3197955 contract uses 18 decimals. Precision affects display, not the dollar value or backing.
Does a 0x address identify BSC?
No. Several EVM chains use that syntax. BSC mainnet has chain ID 56; network context and exact token identity still need to match.
Can the USDT balance alone cover ordinary BSC gas?
Ordinary execution uses BNB. Product-specific sponsorship must be documented separately.
Is BEP-2 still an ordinary alternative network?
No. Beacon Chain is retired. Any eligible legacy recovery is a separate conditional process under current official documentation.
Is the fee always a fraction of a cent?
No. Native gas amount, effective price, operation and market conversion affect the cost. A current estimate is needed.