Short answer: cross-chain swaps into non-EVM chains fail differently than EVM-to-EVM swaps, and almost none of the failure modes have anything to do with the swap itself. There is no eth_sendTransaction waiting for you at the far end, the explorer won't tell you why a leg is stuck, and your destination wallet needs the right token account before anything can land. Here's what I actually hit routing 0.1 WBTC (Arbitrum) into SOL on Solana.
Why non-EVM destinations are a different problem
An EVM-to-EVM swap is one mental model: same address format, same gas rules, same explorer, same failure messages. A non-EVM destination breaks every one of those assumptions at once:
-
Different address space. Your EVM address is not a Solana address. Wallet, wallet, and wallet.
-
Different gas/fee model. Solana charges for transaction space and prioritization; there is no EIP-1559 gas price to set or bump.
-
No shared RPC error decode. A stuck leg gives you a Solana-side error code, not an EVM revert reason.
-
Token accounts. A Solana wallet may not even have the account for the token you're receiving until something creates it.
The route I actually tested
Asset: 0.1 WBTC on Arbitrum → SOL on Solana. Date: October 12, 2026. Quotes only, no wallet connected, pulled through Rango's route comparison across its connected sources.
-
Best route: Flashnet — 74.259280 SOL, $0.15 fee, ~45 seconds, 1 step.
-
Cheaper-fee route: $0.14 fee, 74.155747 SOL, ~2 minutes. Sorting on fee loses ~0.1 SOL (~$9) of output.
-
Worst route: XO Swap, −2.39% versus best.
-
Wrapped alternative: WBTC → USDC (Circle bridge) → SOL, 2 steps, ~26 minutes.
Every route landed native SOL — no wrapped destination token — so the non-EVM risk surface was the destination chain itself, not an IOU layer on top of it.
What actually goes wrong on a non-EVM leg
1. The quote exists, the execution doesn't. A route can display a healthy number and still be unroutable for your specific wallet state. Quote quality and executability are separate checks.
2. Destination account missing. On Solana, receiving a token requires a token account that may not exist yet. On the EVM side this concept doesn't exist at all — a first-timer will assume the swap is broken when it's the wallet.
3. Time is not free. 45 seconds of execution versus ~26 minutes on the wrapped path: the quote you accepted at the start is priced for the beginning, not the end. Long legs carry rate risk with no gas parameter to speed them up.
4. You cannot fix it with gas. On the EVM you bump and retry. On a non-EVM destination the failure is often structural — wrong account, unsupported route — and more priority fee buys nothing.
The practical route checklist for non-EVM destinations
1. Verify the destination address format first. Before touching liquidity, confirm the receiving wallet can hold what you're sending.
2. Read the destination token on the quote. Native or wrapped is a bigger difference than any fee on the list.
3. Compare final output, then fee, then time. My test's fee ranking and output ranking disagreed by ~$9 on a single 0.1-size trade.
4. Count the hops. 1 step / 45 seconds versus 2 steps / ~26 minutes is the whole risk difference.
5. Check the token account exists on Solana-type destinations before you blame the router.
Non-EVM swaps: the honest summary
Aggregators like Rango make non-EVM destinations routable in one step — my tested route did exactly that, native SOL in ~45 seconds at the best output of every option compared. But the aggregator can only fix the route. The wallet, the account, the address format, and the time risk are still yours to check. Do the five checks above and a non-EVM swap stops being a guessing game: you're just comparing route rows like any other trade.