Non-EVM Networks Guide: TRON, Solana, TON, Sui & More

Most popular chains — Ethereum, Arbitrum, Base, Polygon — run the Ethereum Virtual Machine, which means they share address formats, tooling and token standards. AEXI calls these "destination-plus" networks: you can swap both from and to them.

Non-EVM chains run different machinery entirely: Solana's parallel execution, TRON's own VM, TON's sharded architecture. Address formats and token standards differ, and standard EVM bridges cannot reach them at all.

AEXI can deliver tokens to TRON (T... addresses), Solana (base58), Aptos (0x...), TON (0:... / U... / E...), Sui (0x...), Stellar (G...) and Starknet.

These chains are destination-only: you provide a recipient wallet on the target network, and AEXI routes the output there via NEAR Intents.

TRON carries a huge share of the world's USDT volume because transfers cost fractions of a cent and confirm in seconds.

USDT to a TRON recipient is one of the most common AEXI flows — converting Ethereum USDT into TRC-20 USDT on TRON for a P2P or OTC counterparty, for instance.

Solana offers near-zero fees and sub-second finality — ideal for high-frequency stablecoin movement. TON is tightly integrated with Telegram and increasingly used for payments.

Sui, Aptos, Stellar and Starknet each serve their own ecosystems. As long as the token is supported, AEXI's intent engine can route a payout to a native wallet on any of them.

Because formats differ per chain, AEXI validates the recipient input before anything moves. The placeholder changes with the network — "TON recipient address (0:... / U... / E...)" for example — and invalid formats are flagged before you confirm.

Always double-check the prefix and length of a non-EVM address. A misdirected payout cannot be reversed.