Why STON.fi Pauses Swaps When TON Goes Offline
STON.fi can pause swaps in its official interface during a TON outage because the frontend is a service, not the chain. The team can stop new swap requests when TON is delayed or not producing blocks, without reversing blockchain history or controlling tokens in self-custodial wallets.
🔥 What the pause does and does not do
- It stops the official app from preparing new swap actions.
- It does not switch TON validators off.
- It does not automatically cancel a transaction already signed and broadcast.
🚀 Why leaving swaps open becomes dangerous
Under normal conditions, a quote and execution stay reasonably close. An outage breaks that.
- Market state can change before the swap lands.
- Delayed refunds still need TON messages.
- Status screens can look wrong while infrastructure is unstable.
🧠 The August 2024 example
DOGS claim traffic filled queues and TON later stopped producing blocks. After processing resumed, congestion returned. STON.fi then disabled swaps on the official app for roughly 18 hours. Liquidity tools stayed online. The pause was an operational safety step around the interface.
⚡ Extra protections after recovery
Already sent swaps can still execute, fail a price check, or refund later. STON.fi DEX V2 adds min_out and a deadline so a late fill can be rejected instead of accepted at a worse rate.
My take: the pause is useful because it keeps extra users from joining an unstable queue. It is not proof that the DEX owns TON.
Would a frontend pause make you check TON status first, or try another route anyway? 👇
Share how you handled a delayed STON.fi swap during congestion.
Not investment advice - research on your own! 🚀
$GRAM @STONfi DEX
STON.fi can pause swaps in its official interface during a TON outage because the frontend is a service, not the chain. The team can stop new swap requests when TON is delayed or not producing blocks, without reversing blockchain history or controlling tokens in self-custodial wallets.
🔥 What the pause does and does not do
- It stops the official app from preparing new swap actions.
- It does not switch TON validators off.
- It does not automatically cancel a transaction already signed and broadcast.
🚀 Why leaving swaps open becomes dangerous
Under normal conditions, a quote and execution stay reasonably close. An outage breaks that.
- Market state can change before the swap lands.
- Delayed refunds still need TON messages.
- Status screens can look wrong while infrastructure is unstable.
🧠 The August 2024 example
DOGS claim traffic filled queues and TON later stopped producing blocks. After processing resumed, congestion returned. STON.fi then disabled swaps on the official app for roughly 18 hours. Liquidity tools stayed online. The pause was an operational safety step around the interface.
⚡ Extra protections after recovery
Already sent swaps can still execute, fail a price check, or refund later. STON.fi DEX V2 adds min_out and a deadline so a late fill can be rejected instead of accepted at a worse rate.
My take: the pause is useful because it keeps extra users from joining an unstable queue. It is not proof that the DEX owns TON.
Would a frontend pause make you check TON status first, or try another route anyway? 👇
Share how you handled a delayed STON.fi swap during congestion.
Not investment advice - research on your own! 🚀
$GRAM @STONfi DEX
