FAQ

What is a Searcher?

A Searcher is responsible for monitoring mempool transactions in the TON blockchain and submitting new transactions based on predefined logic. It allows users to interact with mempool messages and create transaction bundles that can be sent to the Sova engine for processing.

Why Use a Searcher?

A searcher allows users to interact with mempool transactions efficiently, enabling automated strategies for transaction execution and optimization. Here are some variants:

• Monitor Transactions: Subscribe to new transactions in the mempool.

• Priority Transactions: Create and send transactions that will be included in the beginning of the block.

• Real Anti-MEV transactions that can't be sniffed or tracked.

• Automate Responses: Create and send transaction on specific events in blockchain or front-run/back-run messages that meet criteria.

• Arbitrage & MEV: Implement strategies that detect profitable opportunities.

How to Write a Searcher?

You can use one of existent SDKs to implement your searcher:

• Rust SDK

• Golang SDK

• Typescript SDK

Throughput limits?

Each searcher enforces a limit of 5 requests per second. If you need to have higher limit, you can send request at

Bundle Requirements

The bundle must include External Messages. One of resulting Outgoing Messages should sends a non-zero amount of TON to one of the network's tip addresses. This tip is used to reward Validator to include external & internal messages of Bundle in specific order.

Atomicity of Execution

Once validator includes bundle to Block it guarantees that all external & internal messages are following same order for current & following block on same or different shard. More coverage will be achieved by increasing adoption of Sova TON validator client.