Sui to Polygon: object and account boundary
A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. Sui and Polygon use different network identities, gas assets, wallet support, confirmation behavior, and destination conventions. Validate each side independently in the current route.
Sui coin-object and SUI gas requirements
SUI is the native gas asset for Sui. Sui hexadecimal account address with an object-based asset model Coin objects and Move types are not EVM token contracts.
USDT input versus POL output representation
The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
Converting stablecoin USDT into POL
USDT is issued through ERC-20, TRC-20, SPL, and other network-specific contracts. The ticker does not determine the token standard, contract, issuer controls, or destination address model. The source is a stablecoin contract or recorded native representation, while POL is classified as token. Check the quoted output rather than assuming a one-dollar source unit fixes the destination amount.
Mistakes specific to USDT Sui to POL Polygon
Route-specific mistakes include sending on a network other than Sui; using a destination that is not valid for Polygon; running out of SUI before the source transaction is submitted; assuming other and evm addresses are interchangeable; selecting a stablecoin by ticker without checking its network contract. A Sui source consumes or mutates Move coin objects, uses a Sui address, and spends SUI for gas and storage-related execution. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior. A Polygon PoS receipt follows Polygon token contracts and checkpointed execution; later movement uses POL gas rather than Ethereum L1 gas. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.
USDT input identity and handling
Tether is classified as a stablecoin for this route. USDT uses a network-specific contract asset on Sui. The recorded Sui representation uses 6 decimal places. The input must match the selected ERC-20, TRC-20, SPL, or other USDT representation; each standard has different address, approval, and fee behavior.
POL output identity and receiving
POL (ex-MATIC) is classified as a governance or utility token for this route. POL uses a native asset on Polygon. The recorded Polygon representation uses 18 decimal places. On Polygon PoS, native POL can support later gas; a POL contract on another network does not inherit that native function.