How Jetton Transfers Work in a STON.fi Swap: Full On-Chain Sequence
A STON.fi Jetton swap is never just one action. On TON it runs as a sequence of smart-contract messages where Jetton wallets move tokens, the Router reads the swap intent, the Pool prices the trade, and a final Jetton transfer delivers the result.
🔥 Why Jetton Movement Matters
- Jettons use separate wallet contracts for each owner instead of one universal balance map.
- Token movement and DEX logic stay separate throughout the process.
- The forward_payload inside the transfer carries the exact swap instructions STON.fi needs.
🚀 Step-by-Step Swap Start
1. Your TON wallet authorizes the transfer request to your Token A Jetton wallet.
2. Your Jetton wallet sends the tokens to the Router-controlled Token A Jetton wallet.
3. That wallet emits a transfer_notification to the STON.fi Router with the DEX payload.
4. The Router forwards the swap request to the matching Pool.
⚡ Pool Calculation and Payout
The Pool never simply receives your Jettons. It uses the incoming amount and payload data to calculate output according to current reserves and fees. If the result meets min_out and the deadline is valid, it replies with a pay_to message. The Router then triggers the Token B Jetton transfer to your receiving wallet.
💬 The Trace Reality
Because TON messages are asynchronous, one STON.fi swap creates multiple linked transactions. Seeing the first confirmation only proves the process started. Full settlement requires the complete path from offer Jetton through Router and Pool to the final output Jetton wallet.
The useful part is simple: once you follow the message chain, pending swaps, refunds, and balance updates become far easier to understand.
Have you ever opened a TON explorer to follow a full STON.fi Jetton swap trace? 👇
Drop the stage that surprised you most in the comments.
Not investment advice - research on your own! 🚀
$GRAM @STONfi DEX
A STON.fi Jetton swap is never just one action. On TON it runs as a sequence of smart-contract messages where Jetton wallets move tokens, the Router reads the swap intent, the Pool prices the trade, and a final Jetton transfer delivers the result.
🔥 Why Jetton Movement Matters
- Jettons use separate wallet contracts for each owner instead of one universal balance map.
- Token movement and DEX logic stay separate throughout the process.
- The forward_payload inside the transfer carries the exact swap instructions STON.fi needs.
🚀 Step-by-Step Swap Start
1. Your TON wallet authorizes the transfer request to your Token A Jetton wallet.
2. Your Jetton wallet sends the tokens to the Router-controlled Token A Jetton wallet.
3. That wallet emits a transfer_notification to the STON.fi Router with the DEX payload.
4. The Router forwards the swap request to the matching Pool.
⚡ Pool Calculation and Payout
The Pool never simply receives your Jettons. It uses the incoming amount and payload data to calculate output according to current reserves and fees. If the result meets min_out and the deadline is valid, it replies with a pay_to message. The Router then triggers the Token B Jetton transfer to your receiving wallet.
💬 The Trace Reality
Because TON messages are asynchronous, one STON.fi swap creates multiple linked transactions. Seeing the first confirmation only proves the process started. Full settlement requires the complete path from offer Jetton through Router and Pool to the final output Jetton wallet.
The useful part is simple: once you follow the message chain, pending swaps, refunds, and balance updates become far easier to understand.
Have you ever opened a TON explorer to follow a full STON.fi Jetton swap trace? 👇
Drop the stage that surprised you most in the comments.
Not investment advice - research on your own! 🚀
$GRAM @STONfi DEX