Case Explanation
Last updated
Last updated
Problem Description: A DBot user's copy trading task is started normally, but there is no copy trading record. Provide the copy trading wallet address for checking.
DBot Feedback: The user wrote the wrong copy address. The transaction signer should be written. The user wrote an internal transaction address. The transaction initiator and the account to which the actual token belongs are not the same account; and the smart wallet is a special wallet that completes both buying and selling transactions in the same block, generally an arbitrage wallet, and copying is generally not recommended.
Problem Description: A DBot user reported that this order did not trigger copy trading, and there was no copy trading record. The copy trading wallet purchase transaction was provided for checking.
DBot Feedback: DBot engineers checked the etherscan transaction details logs and found that the transaction contained two swaps, so it did not trigger copy trading. Currently, cross-pool transactions, multiple swaps in the same transaction, bundled transactions, and unsupported trading pairs (such as USDC) will not trigger copy trading for the time being.
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.
The transaction type as below is a bundled transaction, which will not trigger copy trading for now.
The transaction type as below is multiple swaps transaction, which will not trigger copy trading for now.
Problem Description: After a DBot user used the TG bot to fast buy and sell three tokens, a fee was suddenly deducted. Provide the wallet address for checking.
DBot Feedback: After checking on the chain, it was found that the fee was the DBot fee. The DBot fee is charged by time period, summarizing all transactions within the time period. Therefore, the fee transfer that the user sees is not for a single transaction, but a summary within a time period. DBot only charges fees for successful transactions, and the specific details can be checked on the bill page.
Problem Description: A DBot user reported that the Pump copy order was not triggered, and there was no copy order record (it was verified that it was not a multi-signature wallet or other situations). This situation occurred many times after the internal market copy order was successful. After the liquidity was transferred to RAY after it was full, the copy trading was not sold again when the market fulled. Provide transaction details for checking.
DBot Feedback: When setting the copy trading task, the user only checked the copy trading Pump, so after the liquidity is full, the follow trading will not be carried out. Please note that in the DEX column, select DEX to check according to your personal trading needs.
DEX: Checking All means copying all DEXs, including those we will add later. If you do not want to copy a certain DEX, just uncheck it.
Problem Description: A DBot user reported that he set up the stop-profit and stop-loss tasks, but there was no response.
DBot Feedback: The take-profit and stop-loss tasks do not respond. Please check the specific situation in the TP/SL tasks:
Completed: means that the take-profit/stop-loss has been triggered and the transaction is successful;
Expired: means that the take-profit/stop-loss has been triggered but the transaction failed, and the reason for the failure can be viewed in the specific transaction;
In Progress: means that the take-profit/stop-loss conditions you set have not been triggered yet.
The TP/SL tasks will only be triggered when the set price is reached. All TP/SL transaction failures will be prompted with reasons, and configuration adjustments can be made based on the reasons. If all existing TP/SL tasks are triggered and expired, there will be no TP/SL tasks at this time, and you needs to reset the tasks.
How to view and manage the TP/SL tasks?
TG Bot enters the /tpslorders command to view and manage the TP/SL tasks
TG Bot clicks /start, clicks TP/SL tasks on the homepage, or you can Fast Buy/Sell & Copy Trading, and clicks on "TP/SL" to manage
Go to the DBot dashboard - Fast Buy/Sell & Copy Trading - "TP/SL" view and manage the TP/SL tasks, and support one-click cancellation
If you click on Fast Buy/Sell and Copy Trading in TG and set the TP/SL tasks, it will only take effect on the current task. If you want to save the settings for all tasks, please save them in the template: /settings
Problem Description: A DBot user received an error message when trading: You have unpaid fees on solana chain
DBot Feedback: This is an unpaid transcaction fee, which means that the wallet balance is not enough to pay the handling fee. You can check and pay it in the Dashboard-Billing-Transaction Fees. If the account is created directly by TG, please select TG login when logging in to the webpage.
How to pay : please log in to the official website with your mobile phone or computer, and pay the fees on the bill page on the left side of the Dashboard.
Also, you can set Default Trading Fee Wallet Trading fees for each chain. It will be deducted from the wallet set up for that chain, or the highest balance wallet if it is not set up or has an insufficient balance.
Problem Description: A DBot user reported that the transaction list always shows "PENDING" and set a 0.01 sol priority fee and 20% slippage.
DBot Feedback: The display "Pending" means that it is waiting for the transaction result feedback on the chain. Please refresh it later to check. Please refresh it later.
This is caused by congestion and lag on the chain. DBot will show "Pending" when waiting for the final feedback of the chain result. If you are in a hurry to trade, you can go to the blockchain browser to check the result feedback and then buy or sell manually. It is also recommended to increase the priority fee and slippage to increase the success rate.
Problem Description: A user uses DBot Anti-MEV mode, with a priority fee of 0.05sol and a slippage of 17.8%. It frequently reports an error message when copy trading: Insufficient priority fee. Please provide transaction details for checking.
DBot Feedback: The tokens purchased by this user's copy address are all PVPs that are fully loaded on the external market within a short time interval. This situation has a very high requirement for slippage. In the DBot Anti-MEV mode, Jito's feedback of failure results occasionally reports insufficient slippage and errors as insufficient priority fees. It is recommended to increase the slippage appropriately to improve the success rate.
For more details, please refer to
