๐Ž๐ง๐ž ๐’๐ฆ๐š๐ฅ๐ฅ ๐…๐ž๐š๐ญ๐ฎ๐ซ๐ž ๐“๐ก๐š๐ญ ๐Œ๐š๐๐ž ๐’๐“๐Ž๐.๐Ÿ๐ข ๐‚๐ซ๐จ๐ฌ๐ฌ-๐‚๐ก๐š๐ข๐ง ๐’๐ฐ๐š๐ฉ๐ฌ ๐ˆ๐ง๐ญ๐ž๐ซ๐ž๐ฌ๐ญ๐ข๐ง๐ 

I was testing the cross-chain swap interface on @ston_fi with 500 USDT on TON, and one option immediately caught my attention:

โ€œReceive to custom address.โ€

The quote showed roughly 499.506 USDTโ‚€ on the receiving side, with an estimated value of about $499.41.

What stood out is that the destination wallet doesn't necessarily have to be the wallet connected to the swap.

The flow is simple:

โ†’ Start with 500 USDT on TON
โ†’ Select the destination asset/network
โ†’ Enable Receive to custom address
โ†’ Enter the wallet that should receive the funds
โ†’ Confirm the swap

That can be useful for:

โ†’ Sending funds to another wallet you control
โ†’ Receiving assets in a separate wallet
โ†’ Making cross-chain payments
โ†’ Keeping the destination wallet disconnected from the dApp

The interesting part is that the custom destination is built directly into the swap flow rather than requiring a separate transfer afterward.

The interface also shows Omniston handling the cross-chain execution.

For me, this is the kind of DeFi improvement worth noticing.

Not because it's flashy, but because it removes a small piece of unnecessary friction.

500 USDT in.
~499.506 USDTโ‚€ quoted out.
Custom wallet as the destination.

Simple on the surface, with the cross-chain complexity handled underneath.

Of course, I'd still verify the destination address, network and asset before confirming.

Less friction doesn't mean less responsibility.

#STONfi #Omniston #TON #DeFi #CrossChain