Start typing to search this publication.
MEVBOT.TOP
Open menu

Subscribe to MEVBOT.TOP

Get new posts delivered straight to your inbox.

TON Blockchain MEV & Shard Latency: Sniping Liquidity Pools on DeDust and STON.fi

Understanding asynchronous actor-model execution, FunC contract patterns, and DEX arbitrage on TON.

0xB283148a1981fb052572df0510a1C782f6334e66
1 min read
Cover image for TON Blockchain MEV & Shard Latency: Sniping Liquidity Pools on DeDust and STON.fi

TON Blockchain MEV & Shard Latency: Sniping Liquidity Pools on DeDust and STON.fi

The Open Network (TON) has experienced unprecedented user onboarding fueled by Telegram's native Web3 integration and Mini Apps. With millions of active wallets interacting with decentralized tokens, trading volume on primary DEXes like DeDust and STON.fi has reached multi-million daily records.

However, the architecture of TON differs fundamentally from EVM and Solana. Searching for MEV and executing arbitrage on TON requires unlearning synchronous execution and mastering asynchronous message passing.


1. The Actor Model: Why Synchronous Swaps Don't Exist on TON

In Ethereum and Solana, a smart contract can call another contract synchronously in the same transaction trace. On TON, contracts communicate strictly via asynchronous internal messages:

[User Wallet] 
     │ (Message 1)
     ▼
[Jetton Wallet] 
     │ (Message 2)
     ▼
[DEX Vault / Pool]
     │ (Message 3)
     ▼
[Recipient / Result]

Each message hop crosses shard boundaries and takes 1 to 2 block ticks (approximately 3–5 seconds total per full settlement cycle).


2. Arbitrage Mechanics Across DeDust and STON.fi

Because message routing takes multiple seconds, classic atomic sandwich attacks do not function identically on TON. Instead, the dominant profitable strategies are:

  1. Cross-DEX Asynchronous Arbitrage: Exploiting wide spreads between STON.fi (v1/v2) and DeDust pools that emerge after major Telegram meme coin launches.

  2. Liquidity Pool Sniping: Monitoring the TON masterchain for new jetton root deployments and pool factory registrations, submitting high-gas Jetton transfer messages immediately upon pool opening.

  3. Shard-Optimized Node Colocation: Running Lite Servers directly peering with TON masterchain and basechain validators to reduce network hop latency.


3. Handling Message Reverts & Forward Toncoins

A critical hazard on TON is stranded assets:

  • If a swap fails due to slippage on the destination DEX, the Jetton transfer must specify a return address and adequate forward_ton_amount to cover return gas.

  • Unprepared bots burn network fees without handling bounce messages properly.


4. Deploying Dedicated TON Automation

For developers seeking production-ready TON trading engines with native TonLib, LiteClient integrations, and DeDust/STON.fi routing algorithms, see the TON MEV Bot on MEVBOT.TOP.

Subscribe to MEVBOT.TOP