swapping assets across chains without a bridge

A bridge is a contract that locks tokens on one chain and issues a representation of them on another. The representation is not the original token. If the bridge is exploited, that representation can become worthless. This site does not use bridges. It also does not hold your funds in a shared pool, which is the method most centralised swap services use. Instead, each swap is a sequence of independent trades on the chains involved. You send coins. The exchanger receives them, trades them on the source chain, moves the proceeds to the destination chain, trades again if needed, and sends the result to your wallet. No contract ever locks your tokens. No single account ever custodies both sides of the trade.

That sequence is worth examining in detail, because at each step there is something you can check and something that can go wrong.

What happens inside a cross-chain swap when no bridge is involved is a series of automated trades executed by the exchanger's software. You pick the asset you want to send and the asset you want to receive. The system looks for a route. If a direct trading pair exists on the destination chain, the swap is simple: the exchanger buys the asset you want and sends it. If no direct pair exists, the system finds an intermediate token, trades the source asset for that intermediate, moves it, then trades the intermediate for your target asset. This is exactly what a decentralised exchange aggregator does on a single chain, but here the same logic spans two chains.

The exchanger does not mint or burn tokens. It does not create wrapped versions of anything. It uses the liquidity available on each chain's decentralised exchanges. This means the route can change depending on which pools have depth at the moment you start the swap. The system estimates the route and shows you the expected output before you send. That estimate is not a guarantee; slippage and price movement during the swap can change the final amount.

How to find a swap route when no direct trading pair exists is handled automatically. The system searches for the cheapest path through available liquidity. It might go through a stablecoin, through a widely traded token like Ether or Sol, or through a series of three or four hops. You do not need to specify the intermediate steps. You do need to understand that more hops mean more ethereum-basics/ethereum-transaction-lifecycle/">transaction fees and more exposure to slippage. The estimate you see before confirming accounts for this.

Why the same token lives at a different address on each chain is a consequence of how tokens are deployed. A token contract is deployed on one chain at one address. That contract has no authority on any other chain. If the same project issues a token on Ethereum and on Solana, those are separate smart contracts, each with its own address and its own supply. The token on Ethereum cannot move to Solana. The token on Solana cannot move to Ethereum. A cross-chain swap does not move the token; it sells the token on the source chain and buys the same project's token on the destination chain. The two are economically linked by the market, but technically separate. This is not a flaw. It is the normal architecture of independent blockchains.

How to move a token from Ethereum to Solana without wrapping or bridging is what this service does. You send the Ethereum token to the exchanger's address on Ethereum. The system sells it for a token that exists on both chains - typically a stablecoin like USDC - and then buys the Solana version of your target token on Solana and sends it to your wallet. The USDC on Ethereum is spent. The USDC on Solana is bought. No wrapping, no bridging, no synthetic representation. The only thing that connects the two chains is the exchanger's off-chain coordination, which monitors both chains and executes the trades.

How many block confirmations each chain needs before a swap completes depends on the chain's finality model. Bitcoin-style chains typically require several confirmations because a block can be reorged. Ethereum and its layer-2s finalise faster; one confirmation is usually enough, though the system may wait for more on high-value swaps. Solana finalises in a few hundred milliseconds, but the system still waits for a confirmation from the network. The exact numbers are displayed on the swap form before you send. They are not negotiable. If you send funds and then see the transaction confirmed on your end, the system has not yet received it until the required confirmations pass. Do not assume the swap has started until the confirmation count is met.

What a memo or destination tag does and when a swap requires one is a routing identifier. Some chains - particularly those with exchange-style deposit addresses - require a memo or tag alongside the destination address. The tag tells the exchanger which swap the incoming funds belong to. If you send funds without the required memo, the system cannot match them to your order. The funds will sit in a holding address until you contact support. The swap form tells you whether a memo is needed and provides the exact string. Copy it exactly. A space, a missing digit, or an extra character will cause the same problem.

What happens if you send coins to the right address but on the wrong network is that the funds are lost to you. The exchanger cannot access them. If you send Ethereum-based USDC to an address on the Solana network, the address format is different, and the transaction will likely fail or go to a nonexistent account. If you send to an address that exists on the wrong network - rare, but possible with address formats that share a prefix - the funds arrive at a wallet the exchanger does not control. There is no way to reverse this. The system checks the network you are sending from and the network of the destination address, but it cannot stop you from choosing the wrong chain in your wallet. Verify the network before you confirm any send.

How to tell if a swap service is holding your funds in a shared pool is simple. A shared pool means you send funds to an address that collects deposits from many users. The service then internally credits your account and later sends from a different address. You cannot see your specific funds on chain. On this site, the address you send to is generated per swap and is not reused. The funds are moved immediately. If you check the blockchain explorer for that address, you should see only your transaction and the subsequent trades. If you see many incoming transactions from different senders, that is a pool. This site does not operate that way.

The swap form below shows the route, the estimated output, the fees, and the confirmations required. Read those numbers. If the estimated output changes significantly between when you load the page and when you send, the route may have shifted. You can reload the form to get a fresh estimate. Sending funds is irreversible. The swap will complete or fail based on market conditions and network traffic. If it fails, the system returns your funds minus the network fees already spent. That return can take minutes or hours, depending on the chain's congestion.

No swap is instant. No swap is guaranteed to execute at the exact rate shown. The mechanism is transparent, but it is also mechanical. Check the address. Check the memo. Check the network. Then send.