### π’ | π΄ **Anti-Rug**
***Exclusive to Ethereum and BSC***
This feature attempts to frontrun liquidity rugs, blacklisting functions, trade disables, tax hikes, unnatural mints, and practically anything that would βrugβ you. **The bot will detect when a malicious transaction is sent to mempool and will try to sell your holdings before the malicious transaction goes through, thus saving your investment.** **If enabled** οΏ½οΏ½**, then the feature will be activated automatically for every trade you perform on the bot.** While the feature works most of the time, it is not guaranteed due to a multitude of different variables, so please be careful with your investments. For example, if the rug transaction was sent privately (not through mempool), then the bot won't be able to detect it until it's mined and anti-rug measures won't be possible in this case. Also, keep in mind that the bot will automatically adjust your transaction *Gas Price/Delta* to *max {Rug Transaction's Gas Price/Gas Delta +5,* [*Global Sell Gas Price/Delta*](/global-settings/sell-settings.md#gas-price-delta)*}* to maximize frontrunning chances, so make sure you have enough funds in your wallet.
For example, suppose that a rug transaction is detected on **BSC** with a gas price of 2 gwei, and that you have configured the *Gas Price* in your [Global Sell Settings](/global-settings/sell-settings.md) to 6 gwei. In this case, the bot will attempt to sell your holdings using *Gas Price* = *max {2+5, 6}* = 7 gwei. If the *Gas Price* in your Global Sell Settings was instead 8 gwei, the bot would attempt to sell using a *Gas Price* of 8 gwei.
***Anti-Rug*** is only available on **BSC** and **Ethereum**. **Arbitrum** has no public mempool support and relies on a First-Come-First-Serve transaction ordering policy, so implemeting anti-rug measures on the chain is impossible. Similarly, **Base**, **Avalanche**, **Solana**, **Sonic**, **TRON** and **TON** have no public mempools that would allow us to implement anti-rug measures.
### π’ | π΄ **Anti-MEV**
***Exclusive to Ethereum and Solana***
* **Ethereum**: For **Ethereum**, Anti-MEV is force-enabled and **cannot be disabled**. In this case, the bot will route your transactions through a private relay, and your transactions will not be broadcast on mempool. This technique will guard against MEV/sandwich bots and avoid pesky copytraders.
* **Solana**: If enabled, the bot will route your transaction through private relays (Jito, Temporal or NextBlock). This technique will guard against MEV/sandwich bots.
### π’ | π΄ Degen Mode π
The bot normally blocks automated buys (auto-buys) of a token if it detects honeypots, blacklist risks, or unhealthy liquidity. However, some users have requested the removal of these βtraining wheelsβ to allow them to go *full degen*. This is what *Degen Mode* aims to accomplish. When enabled π’, the bot will still notify you if the aforementioned risks are detected, but it will **NO LONGER** block auto-buy in those events. Only enable this if you absolutely know what youβre doing and are willing to handle the risks involved.
### **Max Gas Price**
*Exclusive to ETH, BSC, Base, Avalanche, Sonic and Arbitrum*
Choose the maximum gas price youβre willing to pay for an *Anti-Rug* or copytrade transaction. It compares against the gas price needed to frontrun rugs and scams through *Anti-Rug*, and the gas price needed to frontrun/match copytrades. If any of these scenarios require a higher gas price than the *Max Gas Price* you set, the bot will block the transaction.\
\
Please note that the *Max Gas Price* will not interfere with manual transactions, Signals auto-buys, or snipes.
### Max Gas Limit
*Exclusive to ETH, BSC, Base, Avalanche, Sonic and Arbitrum*
Choose the max gas limit you allow the bot to use. You can leave it on *Auto* as the bot already selects an optimal gas limit for the contracts youβre interacting with, or you can set a specific amount to block tokens with high gas usage. If a transaction requires more gas than the set max gas limit, the transaction will be immediately rejected. **This setting impacts both manual and automated transactions.**
Similarly, for **TRON**, there's *Max Energy Limit* which sets the maximum Energy a manual or automated transaction can use.
### Token Report View
This setting is customizable per chain and it sets the default view for the [Token Report](/pasted-contracts.md). A Token Report is a summary of the most important token info and metrics, and you can get it by simply pasting the token contract address in your DMs with the bot. There are two possible views for the Token Report: π **Brief** and π **Detailed**. As the name suggests, the π **Detailed** view provides more metrics and details compared to the π **Brief** view.
### Monitor (All Chains)
This setting is **common across all chains**, and it sets the default view for the [Trade Monitor](/trade-monitor.md). A Trade Monitor is a tool that can be used to monitor your positions in real time. There are three possible views for the Trade Monitor: π **Brief**, π **Detailed** and π **Extended**. As the name suggests, the π **Detailed** view provides additional details on your position compared to the π **Brief** view. The π **Extended** view is similar to π **Detailed** view with the only exception that the summary of positions in the Trade Monitor is displayed in a **non-collapsible quote**. For the π **Brief** and π **Detailed** views, this summary is normally displayed in a collapsible-quote that can be extended and minimized at will.
---
# 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.maestrobots.com/global-settings/general-settings.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.