Why a swap across two blockchains is harder than a swap on one, how bridges and atomic swaps approach the problem, and how a resolver-based design like STON.fi's Omniston coordinates it.
Picture someone holding USDT in a TON wallet. They want USDC in a wallet on Base, an Ethereum layer-2 network. On a single blockchain, this would be one swap: pick two tokens, confirm, done.
Here it's different. The USDT sits on one network, and the asset they want has to appear on a completely different one. No single swap contract can touch both. Something has to coordinate what happens on each side, and it has to do so without leaving the user stranded halfway.
That coordination problem is what cross-chain swaps exist to solve.
What is a cross-chain swap?
A cross-chain swap lets you exchange an asset on one blockchain for an asset on another through a coordinated transaction flow. You start with one asset on a source chain and end with a different asset on a destination chain.
Four terms keep the picture clear:
Source chain and asset: where your funds start (TON and USDT).
Destination chain and asset: where you want to end up (Base and USDC).
Final settlement: the point at which the destination asset is actually in your destination wallet, not just when your first transaction is confirmed
That last point matters more than it sounds. Confirming a transaction on the source chain tells you only that one half of the journey was submitted.
Why blockchains don't share state
Think of two countries with separate banking systems. Each keeps its own ledgers, applies its own rules, and verifies its own transactions. A payment recorded in Country A doesn't automatically appear in Country B's books. Moving money between them needs agreements, intermediaries or other coordination.
Blockchains work the same way:
Independent ledgers. Each chain keeps its own record of balances and contract data, maintained by its own validators.
Different rules. Chains differ in how they reach agreement, how they run smart contracts, and even how addresses look. TON addresses and Base's EVM-style addresses are different formats.
No automatic updates. A transaction on TON changes TON's state only. Base has no way to know about it unless something carries the information across.
Ethereum's developer documentation describes this as blockchains existing in siloed environments, with no natural way to trade or communicate with each other. That is why cross-chain activity needs extra infrastructure. Something has to connect the isolated ledgers, and that choice shapes the risks you take on.
Same-chain swaps vs. cross-chain swaps
1. Where Assets Exist
Same-Chain: Both assets reside entirely on a single blockchain.
Cross-Chain: The source asset exists on one chain, while the destination asset exists on another.
2. How Execution Happens
Same-Chain: Handled through a single transaction flow run by the native blockchain's smart contracts.
Cross-Chain: Requires coordinated actions across two independent chains, linked by an intermediary mechanism.
3. Infrastructure Required
Same-Chain: Handled directly by a DEX (Decentralized Exchange) contract and its liquidity pools.
Cross-Chain: Requires an additional layer such as bridges, resolver networks, relayers, or cross-chain protocols.
4. User Experience & Wallets
Same-Chain: Seamless — requires only one wallet and one network.
Cross-Chain: More complex — often requires managing two networks and potentially two separate wallets.
5. Costs & Speed
Same-Chain: You pay only one set of network gas fees, with execution tied to a single block confirmation time.
Cross-Chain: Involves transaction fees and confirmation times across multiple chains, varying widely based on the chosen route.
6. Key Risks
Same-Chain: Standard DeFi risks like slippage, smart-contract vulnerabilities, and price impact.
Cross-Chain: All standard DeFi risks, plus bridge exploits, coordination failure, destination liquidity shortages, and network/address mismatch errors.
Practical Example:
Same-Chain: Swapping USDT for GRAM on TON.
Cross-Chain: Sending USDT on TON and receiving USDC on Base.
Every cross-chain connection introduces trade-offs between speed, cost, and counterparty security. Which bridges or cross-chain protocols do you rely on most?
The main approaches
There is no single way to do this. Ethereum.org's bridge documentation groups the common designs into three: lock-and-mint, burn-and-mint, and atomic swaps.
Bridge-based approaches
A bridge moves value between chains. STON.fi's own explainer puts the distinction this way: a bridge is mainly about moving value, while a cross-chain swap is mainly about ending with the asset you want on the destination chain.
Two classic models:
Lock-and-mint. The original asset is locked on the source chain, and a wrapped or mirrored version is created on the destination. The wrapped token is only as good as the locked collateral and the system managing it.
Burn-and-mint. The asset is destroyed on the source chain and an equivalent is created on the destination. This depends on a trusted authority or system being able to mint it.
A third, liquidity-based variety releases funds already waiting on the destination side instead of minting a new token.
Bridges can be trusted, relying on an outside set of verifiers, or trustless, relying on the connected blockchains' own validators. Ethereum.org notes that trusted designs can offer connectivity and speed but add trust assumptions, and that bridges have been the target of some of the largest hacks in DeFi.
Atomic-swap approaches
An atomic swap is built on conditional execution: the exchange either completes on both sides or doesn't happen at all. It is often built with a hash time-locked contract (HTLC). The Bitcoin Wiki describes an HTLC as a payment that uses a hashlock and a timelock, so the receiver must prove receipt before a deadline or lose the ability to claim it, with the funds returning to the payer.
In plain terms:
The hashlock means a secret is needed to unlock the funds.
The timelock means if the secret isn't revealed in time, the funds go back.
When two linked HTLCs use the same secret, revealing it on one chain lets the other side claim as well.
When moving value across blockchains, not every cross-chain swap uses the same underlying mechanism. The two primary models—Bridge-based and Atomic-swap (HTLC)—approach trust, liquidity, and risk in fundamentally different ways.
1. Core Idea
Bridge-based: Move or mirror value between chains.
Atomic-swap (HTLC): Conditional exchange linked by a shared secret.
2. Trust Assumptions
Bridge-based: Varies; relies on trusted verifiers or the chains' own validators.
Atomic-swap (HTLC): Cryptographic conditions and timelocks, plus a counterparty providing destination liquidity.
3. Liquidity
Bridge-based: May rely on locked collateral or pools on both sides.
Atomic-swap (HTLC): Needs a counterparty with assets ready on the destination chain.
4. Failure Scenarios
Bridge-based: Smart contract exploits, wrapped-asset depegs or issues, and stuck transfers.
Atomic-swap (HTLC): No counterparty available, or timeouts leading to delayed refunds.
5. Strengths
Bridge-based: Broad connectivity; can carry arbitrary messages or data across chains.
Atomic-swap (HTLC): Native assets stay native—no synthetic or wrapped tokens are needed.
6. Limitations
Bridge-based: Historically a major attack surface in DeFi.
Atomic-swap (HTLC): Heavily dependent on counterparty availability and immediate liquidity.
Neither approach is universally superior. As Ethereum.org notes, there are no perfect solutions each brings a distinct trade-off between connectivity, security, and capital efficiency. Which model do you prefer when routing cross-chain trades?
Neither is universally safer or better. Ethereum.org puts it well: there are no perfect solutions, only trade-offs made to fulfil a purpose.
Omniston: a resolver-based architecture
With those foundations, here is a practical example. STON.fi is a decentralized exchange on TON, and Omniston is its liquidity protocol. According to STON.fi's documentation, it covers swaps on TON and cross-chain swaps through a single request-for-quote (RFQ) model.
What is a resolver?
A resolver is an independent market maker. Omniston's documentation describes it as a service that provides an exchange rate and settles trades. For cross-chain swaps, STON.fi's blog says resolvers bring their own capital, set their own quotes, and compete on price.
Quoting, execution and settlement are different things
This is the part beginners most often mix up. Four stages are easy to blur:
Routing: finding possible paths for your trade.
Quoting: resolvers respond to your request with prices.
Execution: the chosen resolver and the protocol carry out the trade across chains.
Settlement: the final outcome, either completed delivery or a rollback.
A quote is an offer, not a finished trade. Documentation also notes that quotes have validity limits, and that once you submit, the settlement tracking, not the original quote, is the source of truth for what happened.
How the cross-chain flow is designed
According to Omniston's documentation, the flow works like this:
You send a request for quote, and resolvers respond with competing quotes.
You pick one. You fund the source side, and the selected resolver provides the destination-side liquidity.
Linked HTLCs on the two chains tie both legs together.
STON.fi's materials describe the intended outcome as all-or-nothing: either the destination-side leg completes and you receive the quoted asset, or the flow follows a timed refund path. The documentation calls this an intended safety property of the design. Note the scope: it describes how the HTLC settlement is meant to behave, not a promise that every transaction will be instant, free of fees, or risk-free. Smart-contract bugs, network problems and user mistakes remain possible. If no resolver offers a quote, the swap simply doesn't start, and nothing is locked.
STON.fi's blog also says Omniston is not a wrapped-token bridge: assets stay native on each side, with funds held in escrow that is refundable if the swap doesn't complete.
A hypothetical TON-to-Base journey
This walk-through is illustrative. The numbers and timings are not real.
You start with USDT on TON in a TON wallet, and you have a Base-compatible wallet ready.
You choose the destination. You pick Base as the network and USDC as the asset.
Quotes are gathered. Resolvers respond with prices for your request.
A route is selected, and you review the final details, including rate and fees.
You sign. Your funds go into escrow on the source side, the resolver commits destination-side assets, and the linked contracts coordinate.
Settlement. Either your USDC arrives on Base, or the flow unwinds through the refund path.
The official guide, How to send USDT from TON to Base, walks through this exact route in the app. It covers connecting both a TON wallet and a Base-compatible wallet, choosing the token and destination network, reviewing fees, and confirming in your wallet. It also reminds you that cross-chain transactions can't be reversed, so you should check the destination network, asset, amount and address first, and consider a small test transaction. If you swap from TON, STON.fi's cross-chain guide also says to keep a small GRAM balance (GRAM is TON's native currency, formerly Toncoin) to cover network fees.
Supported pairs change over time, so check the live interface for what's currently available.
Risks and precautions
Cross-chain coordination reduces manual steps. It does not remove risk. The main ones:
Smart-contract and protocol risk. Any contract can have bugs, including audited ones.
Compromised infrastructure. Bridges and relayers have been attack targets. Designs differ in how much they trust.
Slippage and changing quotes. Prices can move, so review the final quote before signing.
Fees and liquidity limits. Fees may apply on more than one network, and some routes may have no available liquidity.
Wrong network or address. Addresses valid on one chain aren't valid on another, and a mistake can't be undone.
Delays and recovery limits. Timed refunds exist in some designs, but nobody can guarantee a recovery process for every failure.
Pre-swap checklist
Confirm the source network, source asset and amount.
Confirm the destination network and destination asset.
Check that your receiving wallet supports that network.
Verify the destination address character by character.
Review the rate, fees and minimum received.
Make sure you hold the asset needed to pay network fees.
For larger transfers, try a small test first.
Track the transaction status until it settles.
FAQ
Is a cross-chain swap the same as a bridge?
Not exactly. A bridge mainly moves value between chains, while a cross-chain swap aims to deliver a chosen asset on the destination chain. Modern products blur the line, so check how a given route works.
Do I need two wallets?
Usually, yes. You need a wallet for the source chain and one for the destination chain, such as a TON wallet and a Base-compatible wallet.
Is an atomic swap risk-free?
No. It can reduce certain risks, but contract bugs, liquidity gaps and user errors still apply.
What if no one offers a quote?
In Omniston's design, the swap doesn't initiate, and your funds aren't committed.
Can I reverse a cross-chain swap?
STON.fi's guide says cross-chain transactions can't be reversed, so verify everything before confirming.
Does the quoted rate always apply?
STON.fi's guide says the rate shown applies to that transaction, and the confirmation screen shows the exact amount you'll receive. Always read it before signing.
The bigger picture
The world isn't going to settle on one blockchain, so moving between them will stay a basic need. Better routing and execution architecture reduce friction by letting competing resolvers price a trade, binding both sides with conditions, and showing users one flow instead of a patchwork of apps.
The takeaway: a cross-chain swap is really two transactions on two ledgers, linked by a mechanism you should understand. Know your source, your destination and your route, and read the details before you sign.
Sources
Ethereum.org: Bridges
Bitcoin Wiki: Hash Time Locked Contracts
STON.fi docs: How Omniston Works
STON.fi blog: Omniston explained
STON.fi blog: Cross-chain swaps and bridging: what's the difference?
STON.fi guide: How to make a cross-chain swap on STON.fi
STON.fi: How to send USDT from TON to Base