BNB Chain
BEP-20 USDT, BNB for network fees, and a transfer record on BscScan.
USDT on BNB Chain
USDT on BEP-20: verify the Binance-Peg contract, not just the ticker
USDTBSC is verified in Xuanxi's catalog, and the reviewed implementation maps it by default to 0x55d398...7955. BscScan identifies that contract as Binance-Peg BSC-USD, so the ticker should not be treated as proof of a native Tether contract.
A valid 0x address can still be on the wrong chain
Ethereum and BNB Chain share an address format. The network name and gas currency tell you more than the prefix.
Ethereum
ERC-20 USDT, ETH for network fees, and a different ledger despite the same 0x address shape.
The familiar ticker hides a different control stack
The reviewed route default is Binance-Peg BSC-USD. That wrapper model deserves its own reading instead of inheriting conclusions from ERC-20 or TRC-20 USDT.
BscScan records BEP-20 transfers, and a bridge adds its own public transactions. The route may complicate linkage without removing either record.
The reviewed default is a Binance-Peg token. BscScan describes this token model as backed by assets held in Binance public addresses, which adds a wrapper and custody layer that the Tether Token Terms alone do not describe.
What to verify at quote time
The catalog says USDTBSC can be sent and received. It does not reveal the active contract override, pool depth, service fee, minimum amount, or settlement time.
The BEP-20 evidence ledger
Chain-wide facts and a catalog observation are shown together, but their scope stays separate.
| Fact | Current read | Applies to | Finding | Reference |
|---|---|---|---|---|
| Xuanxi route | USDTBSCThe public catalog listed the BNB Chain rail with both directions enabled. | Xuanxi catalogDirectly observed | Verified | Source: Public enabled-route catalog |
| Reviewed route default | 0x55d398326f99059fF775485246999027B3197955Xuanxi revision 1e2d7e0 maps USDTBSC to this contract by default. A production environment value can override the default. | Reviewed Xuanxi implementationDirectly observed | Verified | Source: First-party route implementation reviewed at revision 1e2d7e0 |
| Public token identity | Binance-Peg BSC-USDBscScan identifies the reviewed default contract as a Binance-Peg token and describes Binance-Peg tokens as backed by tokens held in Binance public addresses. | Contract-specificOn-chain / public ledger | Verified | Source: Binance-Peg BSC-USD token contract |
| Ledger visibility | Fully publicEvery BEP-20 USDT transfer is visible on BscScan. | Network-wideOn-chain / public ledger | Verified | Source: BNB Smart Chain public block explorer |
| Fee currency | Paid in BNBBEP-20 transfers cost a small amount of BNB, not USDT. | Network-wideOn-chain / public ledger | Verified | Source: BNB Smart Chain public block explorer |
| Address format | 0x addressEthereum uses the same visible prefix, so the selected chain must be checked separately. | Network-wideOn-chain / public ledger | Verified | Source: BNB Smart Chain public block explorer |
| Live override and quote | Not exposed by catalogThe public response does not expose the production contract override, pool depth, fee, minimum, or settlement time. | Per routeNo evidence | Not published | Not available |
Destination support is its own test
A destination must explicitly accept BEP-20 USDT. An Ethereum deposit address with the same 0x characters is not evidence of BNB Chain support.
- BNB Chain and Ethereum addresses can look identical. Verify the chain as well as the 0x prefix.
- The reviewed implementation default is not proof that a production environment override has never changed.
BEP-20 questions that prevent a chain mismatch
Is USDTBSC Tether's native BNB Chain contract?
Not in the reviewed Xuanxi default. It maps to 0x55d398326f99059fF775485246999027B3197955, which BscScan labels Binance-Peg BSC-USD. Confirm the live contract because the implementation allows an environment override.
Why does the address look like an Ethereum address?
BNB Chain uses the same 0x address format. The chain id differs, so sending to the wrong chain can lose funds even though the address looks valid.
Does a Binance-Peg wrapper make the transfer private?
No. The wrapper changes the token's control and backing model. BEP-20 transfers still appear on BscScan.
Keep BNB Chain explicit at the destination
Xuanxi opens immediately. Do not let a familiar 0x address substitute for an explicit BEP-20 network label there.