🔥Auto Limit Order
Buy low, sell high, automatic take profit or stop loss according to pre-set strategies
Last updated
Buy low, sell high, automatic take profit or stop loss according to pre-set strategies
Last updated
Limit orders are used to buy or sell tokens at a set price within a specified time period
Please go to DBot-Dashboard, and click "Create" on the "Limit Order" page.
All basic settings are required, buy/sell settings are enabled by default, and will not follow the buy or sell if turned off. After saving, the orders will be created with limit buy and limit sell
Token/Pair Address: The contract address of the trade pair for the token you need to buy / sell
Enter the contract address of the trading pair, and the token security will be automatically checked. (honeypot, LP burnt, mintable, freezable, top10 hold, etc.)
My Wallet: Select the wallet used to limit buy / sell
DBot Buy Price: Trigger to buy when the token reaches this price
(Limit order can be created by market cap & price change. After entering CA, you can use the Price Calculator to create the task)
Buy Amount: Amount of ETH/SOL/BNB used to buy the token
Priority Fee: Used to incentivize miners to prioritize your transactions, the higher the priority fee the faster the transaction is processed
Expiry: Effective time for limit buy/sell, overtime unexecuted orders will be invalidated
Auto Buy: Auto buy if the task expires without being triggered
After enabled, if the task is not triggered within the expiry period, it will be executed automatically when the expiry period ends
Auto Sell: Auto sell if the task expires without being triggered
After enabled, if the task is not triggered within the expiry period, it will be executed automatically when the expiry period ends
Turbo Mode: Turbo mode of the highest priority for large-scale concurrency, low latency, fast trading. The priority fee will be auto split into multiple optimal transaction routing channels in turbo mode. In this mode, please be careful to set slippage to avoid excessive fluctuations in transaction expectations.
*Bribery Tip (Jito)Addiotional bribery tip to be set so that the Jito validator can process your transcation as soon as possible.
Anti-MEV: Anti-MEV will initate transactions through privacy nodes, requiring a brebery tip to be paid to speed up (but final sync relies on global node consensus, which cannot be 100% guaranteed)
Priority Fee: Used to incentivize miners to prioritize your transactions, the higher the priority fee the faster the transaction is processed
Slippage Tolerance: The difference between the actual price and the desired price, the difference multiplier = 1/(1-slippage), 50% means a maximum of 2 times the accepted spread, 100% means unlimited spreads
*Your transaction may be frontrun and result in an unfavorable trade
*The max slippage for Pump & Moonshot is 50% by default, which can be lifted in "Settings - General"
Gas Delta (Gwei): The amount of gas you are willing to pay over the blockchain average, assuming 5 is filled in and the current blockchain average gas is 20, the gas for the transaction will be set to 25 Gwei
Max Gas (Gwei): Max gas you are willing to pay, beyond which the transaction will not take place
Slippage Tolerance: The difference between the actual price and the desired price, the difference multiplier = 1/(1-slippage), 50% means a maximum of 2 times the accepted spread, 100% means unlimited spreads
Retry Count: Retry count after task failure, 0 means no retry
Concurrent Node: Nodes to which the task is sent at the same time
Sell Price: Trigger to sell when the token reaches this price
Sell Ratio: Sell ratio of the token, e.g. if choosing 50%, only half of the holdings will be sold
Limit orders are enabled after saving, and can be manually modified to disable
Limit orders have three statuses
In Progress: Orders that have not reached their expiration time and have not yet been executed
Completed: Orders that were successfully bought / sold
Expired: Orders that failed to buy / sell or were not triggered by the expiration time
The limit orfer tasks can be managed by custom groups, and after grouping, it can be filtered and closed/deleted with one click.
