Best Practice to Configure the MEV Sandwich FlashBot

Fine-tuning your FastlyBot MEV Sandwich FlashBot is an essential step to align it with your trading strategy. Follow these comprehensive steps for a seamless configuration process

Open Configuration File: Locate the configuration file, named env.js, in the MEV Sandwich FlashBot directory.

Config file for fastlybot MEV Sandwich FlashBot

Edit with Precision: Use a text editor of your choice to open the configuration file. This file is your canvas for customization. Tailor the bot's behavior by adjusting parameters such as:

  1. PRIVATE_KEY:

    • Purpose: This is where you provide the private key associated with the wallet you want to use for transactions.
    • Usage: Replace 'your_private_key' with your actual private key.

  2. FLASH_BOT_RELAY_SIGNING_KEY:

    • Purpose: This is an Ethereum private key that does NOT store funds and is NOT your bot's primary key, just generate a random wallet and put it's private key here, it works as un identifier, the more successfull transaction you made the bigger is your priority for your bundle to be included in the next block.
    • Usage: Replace 'YOUR_FLASH_BOT_RELAY_SIGNING_KEY' with your actual private key for a wallet that doesn't store any funds.

  3. WEBSOCKET_PROVIDER_LINK:

    • Purpose: This is the link to the WebSocket provider that the bot uses for real-time market data.
    • Usage: Replace 'wss://websocket_url' with the actual WebSocket provider link.

  4. AMOUNT:

    • Purpose: Specifies the amount of cryptocurrency (in BNB or ETH) that the bot will use to conduct transactions.
    • Usage: Set the desired amount. In the provided example, it's set to 0.01 Eth.

  5. GAS_BRIBE_IN_GWEI:

    • Purpose: This variable represents the gas bribe in Gwei (a unit of Ethereum's cryptocurrency).
    • Usage: in the context of Ethereum transactions, users can include a gas fee, often referred to as a "gas bribe," to incentivize miners to prioritize their transaction. It's main role is to ensure faster inclusion of its transactions in a block.

  6. MINIMUM_LIQUIDITY:

    • Purpose: This variable sets a threshold for the minimum liquidity in the trading pair's pool.
    • Usage: Liquidity is the amount of a particular token available for trading in a liquidity pool. The MINIMUM_LIQUIDITY variable, means that the bot will only consider trading pairs with a liquidity pool size greater than MINIMUM_LIQUIDITY. This threshold helps filter out pairs with extremely low liquidity.

  7. MARKET:

    • Purpose: Indicates the target market for the bot (e.g., Uniswap, Sepolia).
    • Usage: Modify it based on your preferred market.

  8. LEVEL:

    • Purpose: Establishes the threshold level between transaction value and token liquidity, impacting potential profit.
    • Usage: Adjust based on your strategy. Larger levels can yield bigger profits but might reduce frontrunning opportunities.

  9. SANDWICH_OPTIONS:

    • Purpose: Specifies the mode of the bot: 'ALL,' 'INCLUDE,' or 'EXCLUDE.'
    • Usage: Choose the option that fits your strategy. In this example, it's set to 'INCLUDE' which is the better and saffer option

  10. INCLUD_TOKENS_LIST:

    • Purpose: If 'SANDWICH_OPTIONS' is set to 'INCLUDE,' this list defines tokens the bot will frontrun.
    • Usage: Add or remove token addresses based on your preferences.

  11. EXCLUD_TOKENS_LIST:

    • Purpose: If 'SANDWICH_OPTIONS' is set to 'EXCLUDE,' this list defines tokens the bot will not frontrun.
    • Usage: Adjust the list according to your strategy.

Next: How To Select Tokens To front run