SOL transaction failed
Why did the Solana transaction fail?
There are several reasons why the transaction is not on the chain:
Failure of transactions that have been put on the chain: This type of transaction has been put on the chain, but problems occurred during the execution process and caused the failure:
Why is the Solana network congested?
On-chain transactions require a βmajorityβ of nodes to reach consensus to complete state synchronization.
DBot will reply with a failure message when the sale fails. If it fails continuously, you can try to switch to the plug-in wallet to sell manually.
At the same time, we are also preparing to open more solana private staking nodes in more global regions for users to choose.
If the node status of a certain area is blocked, users can automatically/manually switch to nodes in other continents to try.
What makes DBot SOL so fast? Why is there a chance to buy in the same block or first?
DBot's DEX automated trading system uses professional financial-grade technical solutions. Unlike robots on the market, our trading system is embedded in private nodes, which means that we have modified the node code.
A node is a node, but it is also an automated trading system. We do not have the traditional network interaction delay. All data delays occur in the memory and cache inside the computer system, thereby achieving the lowest delay and the fastest speed. Our engineers have been continuously optimizing the code integration of nodes and automated systems, optimizing data structures and CPU cache design to achieve the fastest trading speed.
However, there are many global chain nodes, and the synchronization is very complicated. Occasionally, unexpected events such as short-term forks may occur. At the same time, the final chain is closely related to the current transaction concurrency and congestion level on the chain. However, in general, our current speed is ahead of the market, and we are continuously optimizing each version in this regard, constantly strengthening node firepower coverage and routing algorithm acceleration.
How to set up DBot SOL copy trading to be the fastest?
Due to the complexity of the on-chain situation, please set it according to personal needs, the style of smart wallet (the popularity of sniping tokens) and other factors.
The priority fee may vary depending on the congestion on the chain and the popularity of the token. The DBot automatic priority fee is currently a relatively gas-saving solution. It is recommended to use a custom priority fee setting during congestion. In the default mode of turbo mode, the priority fee will be auto split into multiple optimal transaction routing channels. (Customized priority fee and bribery tip for Solana's transactions supported)
Slippage determines the deviation between the purchase price and the price of the smart wallet. The slippage price is calculated as 1/(1-slippage). If it is set to 20%, it means that a maximum price deviation of 25% is accepted. It is not recommended to set too high slippage for large-amount purchases. It is recommended that the slippage be set within a reasonable range. 50% slippage means that you can accept a 2x price purchase, and 100% means that you can accept any price purchase. The slippage tolerance price is calculated as 1/(1-slippage). This depends on your copy trading needs and risk preferences.
Generally speaking, for the same gas, Turbo Mode will be faster and Anti-MEV mode will be safer. The speed and success rate of Turbo Mode are generally higher than Anti-MEV mode.
If you pursue high-frequency quantification and chain speed, and the single transaction amount is not large and the slippage is not high, you can use Turbo Mode, which is faster and has a higher success rate. If it is a large amount and high slippage transaction, it is recommended to use Anti-MEV mode.
At the same time, DBot provides professional advanced filtering functions in SOL copy buying, which can be set according to your needs to assist your transactions to the greatest extent.
SOL chain copy buy filter settings
Last updated