USDD on BSC: verify chain representation

On BSC, USDD and sUSDD are separate contracts serving different purposes. USDD is the base stablecoin; sUSDD represents a savings position whose underlying USDD value can change. A swap form needs the contract corresponding to the balance you actually hold.

The current USDD contract reference lists BNB Chain USDD at 0x45E51bc23D592EB2DBA86da3985299f7895d66Ba and sUSDD at 0x8bA9dA757d1D66c58b1ae7e2ED6c04087348A82d. It separately lists the peg-stability module and joining contracts, which are not interchangeable with the token address.

A savings balance is measured twice

The USDD Savings guide distinguishes the number of sUSDD units from their corresponding USDD value. Withdrawing burns the savings token and returns underlying USDD. Consequently, 100 sUSDD should not be assumed to mean precisely 100 USDD.

Compare a direct sUSDD sale with the protocol withdrawal result in the same units. Include any subsequent conversion needed to reach the final desired asset. A route that looks shorter can still give a different result because it sells a receipt at a market price rather than redeeming the underlying claim.

Match the current version

USDD's current introduction describes its newer crypto-collateralized system. Historical USDD documentation and old wallet entries can belong to a different contract or mechanism. Use the current network-specific record instead of relying on an old bookmark's ticker.

For a stablecoin swap, identify the output with equal care. Receiving USDD on BSC does not create a TRON balance; receiving another dollar-named token does not prove identical backing. Save the exact contracts and whether the transaction was a market swap or a savings withdrawal, because those actions explain different balance changes.