Same-name native assets and wrapped assets—why can’t they be used interchangeably? Because they may represent different underlying objects and redemption paths. Native assets are recorded by their own chain or issuance system; wrapped assets usually correspond to underlying assets via custody, locking, or smart contracts. A similar display name doesn’t mean the counterparty will recognize them, nor does it mean they can be redeemed under the same rules.

For example, even if you transfer a native asset from one chain to an account that only supports the wrapped version—making sure the address and network are correct—you may still find it doesn’t get credited. Seeing the balance in your wallet doesn’t guarantee it will work at the next step. Even if a page says 1:1, you still need to confirm who is responsible for the exchange.

Before you operate, check item by item: “asset full name, the chain it belongs to, the contract address (if any), and the version supported by the recipient.” If the receiving page only lists an abbreviation, or doesn’t clearly specify the version, stop at the confirmation page. This judgment doesn’t apply only when both parties’ official pages explicitly support the same version and clearly state the relationship between them.