Cross-chain swap guides

When a cross-chain swap fails, your coins sit in one of four places: your own wallet, the mempool, the upstream deposit address (refund pending), or the destination chain with display lag. UpSwap never holds funds on its books, so there is no internal balance to freeze.

A hardware wallet guarantees one thing: the bytes you confirm on its screen are the bytes that get signed, and a compromised computer cannot change that display. It does not tell you whether the deposit address you were handed is legitimate. If the website was poisoned, both screens show the attacker's address and they match. A small test transfer and an independent block-explorer check are what cover that gap.

TRC20 for CEX deposits ($0-$1.50, ~57s), ERC20 for DeFi (only chain Aave/Uniswap V3 have real depth), BEP20 inside the Binance/PancakeSwap loop ($0.05-$0.30), SPL on Solana-native rails. Sending TRC20 or BEP20 USDT to a Coinbase address is permanent loss. Fee snapshot dated 2026-06-17.

Whether your USDT is recoverable comes down to three variables: was it sent between EVM chains, did it land at a CEX deposit address, and do you still control the sending wallet's private key. This guide gives you the 30-second decision tree, the three-tier recovery taxonomy (DIY same-key EVM sweep, CEX paid recovery, Tether direct freeze-and-reissue), a 5-exchange policy matrix sampled 2026-06-26, and an honest list of cases that genuinely cannot be recovered.

A cross-chain swap is two transactions on two chains, both already recorded on public ledgers. Paste your source tx hash into the source chain's explorer, confirm the deposit landed, then paste your destination address into the destination chain's explorer to find the payout. Read six fields on any tx: status, confirmations, from/to, native value, token transfers, and fee. The stablecoin trap: USDT shows Value 0 native because it is a Token Transfer, not a native move, and the real amount is one line lower. Verify all of this yourself across Etherscan, TronScan, Solscan and mempool.space before you ever message Telegram @upswapservice, so you arrive with a tx hash and orderId instead of a shrug.

Under $25k on liquid pairs, a non-custodial cross-chain swap usually beats a Binance withdrawal once you price KYC waiting time honestly. Over $50k the CEX wins. The middle is a 5x5 matrix.

There is no single "safer" stablecoin. USDC wins for DeFi, transparency and EU-regulated use; USDT wins for CEX trading and emerging-market cash-out. Both maintain an on-chain freeze function and both have de-pegged (all figures sampled 2026-06-26).

Most stuck swaps fall into four symptom buckets: wallet debited but order pending, source confirmed but destination silent, quote expired before signing, or refund initiated but not arrived. Match your symptom to the right row, check the on-chain wait window for your source chain, and only escalate to <code>@upswapservice</code> after the worry threshold is crossed.

Address poisoning attempts hit 34,000 per hour (Trust Wallet, sampled 2026-06-26; same source for 225M+ cumulative attempts and $500M+ confirmed stolen) and Ethereum daily attempts jumped from 628K in November 2025 to 3.4M by January 2026 after Ethereum's Fusaka upgrade cut gas costs ~6x (BeInCrypto, sampled 2026-06-26). The 5-second rule before any send: check the 6 middle characters of the address, verify on the hardware-wallet screen, and send a $20-50 first-corridor test. Different chains break differently when a character flips — TRC20 and BTC reject silently, Solana does not.

When a cross-chain swap fails, the refund auto-returns to your SOURCE address — the exact address your deposit came from, traced on-chain from the deposit transaction. That mechanism is safe when you sent from a wallet you control, and a quiet trap when you did not: if the source is an address you cannot reach, the refund lands somewhere you cannot reach it. Four source-wallet types break this — a centralized-exchange withdrawal / hot wallet, a single-use exchange deposit address, a Gnosis Safe not deployed on the refund chain, and a counterfactual (undeployed) ERC-4337 smart account. On UpSwap you do NOT set a refund address; it goes to source automatically (model confirmed 2026-06-11). The one rule that prevents almost every lost-refund ticket: never start a swap directly from a CEX withdrawal — withdraw to a self-custody wallet you control first, then swap from there.

Every cross-chain swap quote has five fee layers: source-chain gas, solver spread, destination-chain gas (plus Solana ATA rent), slippage band, and refund-tx fee if anything goes wrong. We name who collects each, when it triggers, and the dollar range on three real routes (Route 1 from project archived sampling; Routes 2-3 from industry-typical bands).

Four mechanisms move value between chains: lock-and-mint (mints a wrapped IOU backed by a locked reserve), burn-and-mint (a canonical issuer like Circle CCTP re-mints the native asset), liquidity networks (native assets swapped from pre-funded LP pools), and intent-based swaps (you sign a desired output amount and competing solvers advance the destination asset). Only lock-and-mint always creates wrapped tokens. The historic bridge hacks — Ronin ~$625M, Wormhole ~$325M, Nomad ~$190M — all hit locked-collateral honeypots, a different attack surface than the intent model's solver non-fill risk; those are 2022-2023 incident snapshots, and several of the named protocols have since revised their security models. Neither approach is zero-risk. UpSwap aggregates the intent and relayer rails (NEAR Intents + Relay), so it inherits the solver-fill surface, not a locked reserve.