# Twitter Preset
{% hint style="info" %}
Twitter Presets allow you to set the default configurations used when running a Twitter task.
***
The guide below refers to BSC. The same logic applies to all supported blockchains, although buttons and available features may vary.
{% endhint %}
{% stepper %}
{% step %}
Select the desired blockchain
{% endstep %}
{% step %}
Tap 🔧 Presets
{% endstep %}
{% step %}
Tap 🐤 Twitter Presets
| Button | Action |
| ------------------ | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Max Buy Count | Specify how many of the target account’s posted contracts you want the bot to purchase.
Eg.
• If you enter 1, Bloom will only buy the first contract posted.
• If you enter 2, Bloom will buy both the first and the second contracts posted.
If you change target account, the parameter won't reset.
|
| Buy | Choose the BNB amount to buy. |
| Gas | Set the transaction gas (Max Priority Fee) for buying.
Max Fee is automatically calculated using the formula: Base Fee + (Priority Fee × 2).
|
| Slippage | Set the buy slippage percentage. |
| Buy Tip | Set the tip to increase transaction priority and help your trade execute faster.
Ethereum: We suggest to set a minimum of 0.001 ETH.
|
| Mev Protect | When MEV Protect is enabled, your transactions will be processed through BloXroute to prevent getting MEVed. If disabled, transactions will be routed through a custom public node: slightly faster, fully visible.
Warning: Do not disable MEV Protect without a specific reason. The speed gain rarely compensates for the slippage loss on a sandwiched trade.
|
| Twitter Tweet | 🟢: When enabled, Bloom automatically buys posted contracts according to your settings. *(Including quoted retweets where the contract is taken from the quoted text).* |
| Twitter Reply | 🟢: When enabled, Bloom automatically buys contracts posted in a post reply according to your settings. |
| Twitter Bio Update | 🟢: When enabled, Bloom automatically buys contracts posted in bio the moment the bio changes according to your settings. |
| Twitter RT | 🟢: When enabled, Bloom automatically buys contracts posted in the original retweeted post, following your settings. |
| Twitter OCR | 🟢: When enabled, Bloom uses OCR to automatically buy contracts from images. |
| Min Market Cap | Set the minimum market cap at which you’re willing to buy. When the post appears, the bot checks the cap: if the market cap is below your threshold, the buy won’t execute; if it’s above that value, the buy will trigger. |
| Max Market Cap | Set the maximum market cap at which you’re willing to buy. The bot checks the cap when the post appears: if the market cap exceeds your threshold, the buy won’t trigger; if it’s lower, the buy will execute. |
| Min Token Age | • Set the minimum amount of time passed since the token was created.
• For migrated coins, the time is calculated from the moment they were listed on a DEX.
|
| Max Token Age | • Set the maximum amount of time passed since the token was created.
• For migrated coins, the time is calculated from the moment they were listed on a DEX.
|
| Limit Orders | Refer to the dedicated guide. |
| {% endstep %} | |
| {% endstepper %} | |
***
### Auto Orders
{% hint style="info" %}
Auto orders are limit orders automatically created after you buy a coin. They trigger based on your settings and don’t require you to start them manually once created.
After creation, the task will automatically start post-buy. Make sure to delete it if you don't want it to run.
{% endhint %}
{% stepper %}
{% step %}
Click 📈 Limit Orders
{% endstep %}
{% step %}
Tap 🆕 Create Limit Order
| Button | Action |
| ---------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Dev Sell | Choose whether to automatically sell the specified amount if the Dev sells any of their tokens. If enabled, the bot will ignore the set profit/loss percentage and only trigger a sale when the Dev sells. |
| Sell Amount | Set the % you would like to sell. |
| Profit/Loss | Set take profit or stop loss.
• 📈 Take Profit: Use positive values (e.g., +100% for 2x)
• 📉 Stop Loss: Use negative values (e.g., -50% for half)
|
| Sell Gas | Set the transaction gas (Max Priority Fee) for selling.
Max Fee is automatically calculated using the formula: Base Fee + (Priority Fee × 2).
|
| Slippage | Set the buy slippage percentage. |
| Back | Return to the previous menu without creating the order. |
| Create Order | Tap to create the order. |
| Delete Order | Deletes the target order.
|
| {% endstep %} | |
| {% endstepper %} | |
---
# Agent Instructions: Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter:
```
GET https://docs.bloombot.app/evm/evm-bot/settings/presets/twitter-preset.md?ask=
```
The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.
