A stablecoin name is incomplete information for a BSC trade. Record the chain, contract and party responsible for that representation before comparing reserve claims or choosing a destination. This prevents facts about an original asset from being silently transferred to every token using its ticker.
A compact asset record
| Field | Question it answers |
|---|---|
| Network and chain ID | Where does this balance exist? |
| Contract address | Which precise token does the quote deliver? |
| Issuer or representation operator | Who creates this version? |
| Backing relationship | Is the claim direct or dependent on another token? |
| Exit and destination support | How can this exact version be used or exchanged later? |
| Source and check date | How recent is the evidence? |
These fields answer different questions. A token list can help identify a deployment; it cannot alone establish current collateral or redemption eligibility. Binance's pegged-token collateral page explicitly separates that subject from the exchange's own proof of reserves.
Read network lists at the asset level
A publisher may support a network for one product but not another. At the check date, Tether's detailed BSC section lists XAUt, while Circle's native-USDC list does not include BSC. A broad corporate network relationship therefore cannot substitute for a matching token contract.
For an intended stablecoin conversion, fill this record for both sides. Then ask what exposure changes. If both representations depend on the same wrapper operator, changing the original issuer's name may leave that shared operational dependency intact.
Keep uncertainty visible. “Contract identified; current collateral not checked” is more useful than marking an asset simply “verified.” It tells a later reviewer what was established and which question still needs an authoritative source.
Sources & verification (3)
Source-check date is recorded in the article details. URLs are provided for manual verification. Use Copy to keep this page open.
- Proof of Collateral
Scope is Binance Bridge pegged tokens, separate from exchange proof of reserves; current reserve rows were not retrievable.
https://www.binance.com/en/proof-of-collateral - Supported Protocols and Integration Guidelines
The current BSC section lists XAUt; a BSC network mention alone does not establish a native USDt deployment.
https://tether.to/en/supported-protocols/ - USDC
Current native issuance list does not include BSC; direct Circle Mint availability is limited to qualifying institutions.
https://www.circle.com/usdc