About Copy Trading/Sniping
Last updated
Last updated
Please log in DBot-Dashboard or DBot TG bot and set it up for Copy Trading.
DBot-Dashboard:
DBot Telegram Personal Bots
Currently, the TG side has not pushed the failed copying buy order. Please check whether there is a copying record in Copy-Record of DBot-Dashboard.
If the copy order fails, the specific reason will be displayed.
If other reasons are displayed, please click the question mark, and the prompt after the error is the specific reason. Generally, it is due to slippage or insufficient priority fee.
If it shows that the transaction on the chain failed, please go to the corresponding blockchain browser to check the specific reason.
If there is a copy order record, please adjust your copy order strategy settings according to the failure feedback;
If there is no copy order record, please first check whether the wallet address is filled in correctly and check the status of the target transaction. Currently, cross-pool transactions, multiple swaps of the same transaction, bundled transactions, and unsupported transaction pairs (such as USDC) will not trigger copy orders for the time being.
DBot supports automatic take-profit and stop-loss at the token level (only once, segmented, and proportional selling), and also supports TP and SL at the wallet level of copy trading. There are three copy-order selling modes to choose from:
Sell Mode:
Mixed: Enable both copy sell and take profit/stop loss
Only Copy: Copy sell only, without enabling take profit/stop loss
Only TP/SL: Only enable take profit/stop loss, without copying sell
Auto TP / SL Mode:
Only Once: Take profit / stop loss executed only once, Sell 100%
Segmented: Take profit / stop loss executed multiple times with customized sell price and sell ratio
For sure, you can create and edit limit orders, auto sniper and copy trading at Telegram Bot. Also, Token multisender and token collection for TG Bot
We now have a large number of users who use it, the current feedback of copy trading are very good. Our average speed has been greatly optimized and improved. According to our observations, sometimes the speed can even exceed the order copying target.
We build our own nodes, so there will be no situation where they are occupied by external services. We can ensure that service resources are exclusively for our member users during the peak period of the market. At the same time, we have pledged nodes and have done a lot of intelligent routing broadcast optimization, striving to queue up and go on the chain as quickly as possible.
But at the same time, there are many global chain nodes, and the synchronization situation is also very complicated. Occasionally, there will be unexpected things such as short-term forks, but at the same time, the final result is closely related to the current transaction concurrency and congestion level on the chain. But in general, our current speed is leading the market, and we are continuously optimizing in every upgrading, constantly strengthening node firepower coverage and routing algorithm acceleration.
The success of following orders is affected by many factors, such as priority fees and slippage settings. It is recommended to set priority fees and slippage reasonably. The transaction speed of DEX trading bots depends more on the congestion on the chain. We will give users prompts for reasonable settings based on the congestion level on the chain to maximize the success rate.
In the default mode of turbo mode, it will automatically allocate the priority fee to gas and jito. (Customized priority fee and bribery tip for Solana's transactions supported) If your gas is sufficient, the success rate of the turbo mode will be higher. In the turbo mode, the priority fee will be automatically split into multiple optimal transaction routing channels. The turbo mode gives the highest priority to ultra-large-scale concurrency, extremely low latency, and extremely fast chain upload. In this mode, please set the slippage carefully to avoid excessive fluctuations in transaction expectations.The anti-mev mode will initiate transactions through privacy nodes, and you need to pay a bribe to speed up the chain upload (but the final synchronization depends on the global node consensus, which can not be 100% guaranteed)
If you are looking for high-frequency quantification and chain speed, and the single transaction amount is not large, it is recommended to use the turbo mode. The more nodes there are, the faster the chain speed is, and the greater the probability. The anti mev mode only uses global privacy nodes, so the speed will theoretically be slower than the turbo mode.
Retry sell works actually. The retry will be performed according to your original settings, and the failure will be pushed after all retries are completed. When you see the failure message, the retry has ended. If the price has exceeded the slippage, the retry will also fail.
DBot uses self-built private nodes, which guarantees speed, but there are many factors affecting sniping, which requires comprehensive judgment. If it is a pump dev, you can also follow his address to snipe. PumpDev's MINT and Buy are usually in the same transaction, and the time difference is not big. It is mainly because the price of Token fluctuates greatly in the early stage of sniping, the competition is fierce, and there may be tax factors, so the requirements for slippage and gas are relatively high.
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. The Turbo mode currently automatically allocates the priority fee to gas and jito.
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.
DBot uses private nodes to ensure privacy and security in the transaction mempool, but the transactions of DEX contracts are still open and can be monitored. In the block time interval of EVM, huge slippage will still give mev bots enough benefits to execute sniping. Unless it is a popular coin or a very optimistic coin, we do not recommend setting huge slippage. We will remind you of this part when setting it to enhance the risk.
Sol is different from Evm. Sol does not have a unified mempool, so Sol will not have a mev problem fundamentally, but Sol is publicly linked like all other chains. Now Jito covers nearly 80% of the nodes. Like our monitoring, the market will also have other large orders to monitor. In a very short period of time, if the order is large and profitable, there is a probability that it will be preempted by other monitors at a very high Jito price.
If you have a large order requirement, you can turn on the anti-pinch mode and set a Sol Jito fee. It is recommended that the amount be appropriately increased based on your own experienceγ
This refers to the number of nodes. If you select multiple concurrent nodes, multiple nodes will help you request at the same time, increasing the success rate of the transaction. It is possible to pay more gas for multi-node concurrency. SOL generally does not, but EVM may. It is recommended to only use it in necessary sniping scenarios.
You can click the question mark in the copy order record in the dashboard to view the specific reasons and make adjustments.
The success rate of copy order sales is affected by many factors, such as gas and slippage settings.
It is recommended to set them according to the smart wallet style.
At the same time, the congestion on the chain will also affect the success rate of copy order sales.
If there is an on-chain process, it will be deducted, which is charged by the chain. If there is no chain process, it will not be deducted.
This is the mechanism of EVM. In order to avoid gas loss, the nodes on the chain will simply simulate the execution of the transaction. If the simulation result is unsuccessful, the actual execution result must fail. Returning errors in advance can reduce the gas loss caused by some transaction failures. This error is generally caused by insufficient slippage or problematic tokens.
It is a slippage problem. The core reason is that the pump can only copy trade according to quantity of token. Therefore, if the slippage is completely released, users may spend far more Sol than expected. In order to avoid extreme situations and protect the rights and money of users, the DBot backend currently limits the slippage of the Pump.
If your question is still not answered in the FAQ above:
Please refer the steps in
Please refer the steps in
Telegram offical group:
DBot DiscordοΌ
