šŖšµš šš®š» š® ššæš¼šš-ššµš®š¶š» š¦šš®š½ š§š®šøš² šš¼š»š“š²šæ?
A regular TON swap happens on one blockchain.
A cross-chain swap has to coordinate execution across two different networks.
For example:
š„š²š“šš¹š®šæ š§š¢š” ššš®š½
TON ā TON
One network ā one settlement process.
ššæš¼šš-š°šµš®š¶š»
TON ā Ethereum/Base/etc.
Quote ā source transaction ā resolver fill ā destination settlement.
With STON.fi and Omniston, the process involves an RFQ where resolvers compete to provide a quote. After a quote is selected, the source and destination sides are coordinated through linked HTLCs.
That means there can be several things to wait for:
ā The quote to be matched
ā The source-chain transaction to confirm
ā The resolver to fill the order
ā The destination-chain transaction to settle
Network conditions matter too.
TON may confirm quickly, while the destination EVM chain can take longer depending on its own block production and network conditions.
š¦š¼ ššµš²š» š¶š š® š±š²š¹š®š š»š¼šæšŗš®š¹?
If the transaction is still progressing through the expected stages, a short wait doesn't necessarily mean something is wrong.
If it stays pending unusually long, the useful next step is to check the transaction hash and trade status rather than submitting the swap again.
STON.fi's Omniston documentation provides trade tracking using the quote ID, wallet address and outgoing transaction hash.
This is also why cross-chain swaps shouldn't be judged by the same timing expectations as a normal TON swap.
You're not waiting for one chain alone.
You're waiting for two chains to coordinate one settlement.
And with Omniston's HTLC design, the intended outcome is atomic: either the quoted assets settle, or the timelock mechanism provides a refund path.
A regular TON swap happens on one blockchain.
A cross-chain swap has to coordinate execution across two different networks.
For example:
š„š²š“šš¹š®šæ š§š¢š” ššš®š½
TON ā TON
One network ā one settlement process.
ššæš¼šš-š°šµš®š¶š»
TON ā Ethereum/Base/etc.
Quote ā source transaction ā resolver fill ā destination settlement.
With STON.fi and Omniston, the process involves an RFQ where resolvers compete to provide a quote. After a quote is selected, the source and destination sides are coordinated through linked HTLCs.
That means there can be several things to wait for:
ā The quote to be matched
ā The source-chain transaction to confirm
ā The resolver to fill the order
ā The destination-chain transaction to settle
Network conditions matter too.
TON may confirm quickly, while the destination EVM chain can take longer depending on its own block production and network conditions.
š¦š¼ ššµš²š» š¶š š® š±š²š¹š®š š»š¼šæšŗš®š¹?
If the transaction is still progressing through the expected stages, a short wait doesn't necessarily mean something is wrong.
If it stays pending unusually long, the useful next step is to check the transaction hash and trade status rather than submitting the swap again.
STON.fi's Omniston documentation provides trade tracking using the quote ID, wallet address and outgoing transaction hash.
This is also why cross-chain swaps shouldn't be judged by the same timing expectations as a normal TON swap.
You're not waiting for one chain alone.
You're waiting for two chains to coordinate one settlement.
And with Omniston's HTLC design, the intended outcome is atomic: either the quoted assets settle, or the timelock mechanism provides a refund path.
