Trading Bot
Last updated
Last updated
Auto Snipe is a key feature for the Trading Bot. When the liquidity pool of a token pair is activated, faster transaction inclusion than competitors means users can purchase the target token at a lower price—speed is the core competitive advantage of Auto Snipe. For more details, please refer to Analysis of Swap Transaction Elements.
How to make Snipe transactions be included faster? Two elements need to be considered: fast real-time monitoring and fast RPC.
Fast real-time monitoring refers to capturing signal of the activation event of the target token pair faster than competitors.
One way to achieve this is by setting up a full node yourself. This involves synchronizing mempool transactions(EVM chain), from which events are parsed, based on the P2P network. However, there are many issues with this approach:
Communication Latency: If the self-built full node is located at the edge of the blockchain network, the latency in monitoring events will be relatively higher.
Performance Bottleneck: If the self-built full node runs on server that has insufficient performance, it may encounter performance bottlenecks during periods of high network congestion, failing to monitor events in a timely manner.
Single Point of Failure: A self-built full node deployed as a single point is susceptible to failure. When the server goes down, monitoring of events will also come to a halt.
In scenario of real-time monitoring, it is recommended that the Trading Bot use BlockRazor's high-performance network to subscribe transactions to capture event of activation of target token pair at the earliest opportunity.
BlockRazor's high-performance network is composed of backbone nodes distributed globally, and it provides data stream to speed-sensitive projects based on and deeply optimized algorithm and architecture.
Benchmark shows that compared to the industry-leading high-performance network provider bloXroute, BlockRazor can receive the latest transactions with lower latency. For more details, see the benchmark.
Once the activation event of the target token pair is detected, Trading Bot should immediately construct and send the snipe transaction. For the Trading Bot, it seems that directly connecting to the Builders not only improves the transaction inclusion rate but also get transactions protected through private channel, killing two birds with one stone. However, there are issues:
Rate Limit: The Builder's transaction API have rate limits. Sniping transactions can cause instantaneous high concurrency traffic, which is very likely to trigger rate limit.
Latency: If the Trading Bot's server is geographically distant from the Builder, or even across continents and oceans, the latency for the Builder to receive the snipe transaction will increase.
To get transactions included faster, it is recommended to use BlockRazor's Scutum RPC. Based on a globally distributed network, Scutum can receive transactions from TG Bot with extremely low latency and then forward these transactions to geographically nearby Builders, which achieves end-to-end low-latency forwarding at the network level and improves the transaction inclusion rate.
The chart data shows that transactions submitted to Scutum have a probability of being included in the next block as high as 95%, and 100% probability being included in the next 2 blocks, which significantly surpasses that of competitors.
In addition, Scutum RPC provides sendBundle API, which supports Trading Bot to submit bundles with snipe transactions right after the transaction of activation of target token pair, and then forward to mainstream builders to get transactions included in the very next block, implementing the feature of Block-0 Snipes.
Register for BlockRazor
Log in to BlockRazor, subscribe to the Tier2 or Tier1 plan, and go to the account module to obtain the auth token
Integrate the Subscribe NewTxs method of the high-performance network to subscribe to the latest transactions with low latency
Register for BlockRazor
Log in to BlockRazor
Go to the RPC module to view your dedicated RPC (currently supporting Ethereum and BSC). You can visualize and configure RPC parameters with one click, and then copy the RPC URL.
Go to the project of Trading Bot, locate the chain's RPC configuration file, and replace the default endpoint with the Scutum dedicated RPC URL.
When the target event of liquidity pool activation is captured from Subscribe NewTxs, automatically construct sniper transactions based on user settings.
Submit the snipe transactions to Scutum RPC.
Note: Scutum RPC is free for project builders to integrate without rate limiting. Additionally, BlockRazor provides customized transaction services for Trading Bots. Join Discord to contact.
Currently, on which chains does Scutum provide services?
Currently, Scutum supports Ethereum and BSC.
