MEV Backrunning Bot Development for Ethereum & L2

We design and develop full-cycle blockchain solutions: from smart contract architecture to launching DeFi protocols, NFT marketplaces and crypto exchanges. Security audits, tokenomics, integration with existing infrastructure.
Showing 1 of 1All 1305 services
MEV Backrunning Bot Development for Ethereum & L2
Complex
~1-2 weeks
Frequently Asked Questions

Blockchain Development Services

Blockchain Development Stages

Latest works

  • image_website-b2b-advance_0.webp
    B2B ADVANCE company website development
    1349
  • image_web-applications_feedme_466_0.webp
    Development of a web application for FEEDME
    1247
  • image_websites_belfingroup_462_0.webp
    Website development for BELFINGROUP
    949
  • image_ecommerce_furnoro_435_0.webp
    Development of an online store for the company FURNORO
    1183
  • image_logo-advance_0.webp
    B2B Advance company logo design
    642
  • image_crm_enviok_479_0.webp
    Development of a web application for Enviok
    921

Custom Bots for DeFi Arbitrage and Backrunning Strategies

We develop backrunning bots for MEV arbitrage — from single-chain strategies on Ethereum to multi-chain systems integrating Flashbots and Tenderly. With over 10 years in blockchain development and 5 years of MEV optimization experience, and more than 30 successful MEV bot deployments globally, our team delivers proven performance. Unlike template solutions, our bots undergo formal verification and load testing on a mainnet fork.

Backrunning is executing a transaction immediately after a target transaction in the same block. The classic scenario: a large swap moves the price in a pool, and the bot arbitrages the difference between that pool and other DEXs. For example, a 100 ETH swap on a Uniswap V3 pool with 0.05% fee can create a price impact that yields a $300 arbitrage opportunity across SushiSwap. The difference between a bot that consistently earns and one that burns gas to zero lies in implementation details: gas portfolio settings, MEV infrastructure choice, and pre-submission simulation.

According to our project statistics, proper bundle submission via Flashbots reduces gas war losses by 70% compared to the public mempool. And multi-chain routing increases profitable opportunities by 3x. Our gas optimization techniques include dynamic caps and bundle submission, cutting gas costs by up to 80%. As stated in Flashbots Documentation, using bundles reduces reverted transactions by 90%.

How Does a Backrunning Bot Work?

Gas as the main cost item. Backrunning is a competitive environment. Dozens of bots monitor the same mempool. If your bot loses the gas auction, its transaction lands after someone else's, the opportunity is gone, and you pay gas for a revert.

A typical mistake: the bot sends a transaction with gasPrice = targetTx.gasPrice + 1 gwei. A competitor sets + 2 gwei. An endless escalation leads to all arbitrage profit being consumed by gas.

The correct approach: calculate the maximum allowable gas price from expected profit. If the arbitrage yields $50, gas limit 200k, acceptable cost ratio 60% — maximum gas price = $30 / (200000 * ethPrice). The bot should never exceed this threshold.

Simulation before submission. Sending a transaction without prior simulation is burning gas. The blockchain state changes between the moment the opportunity is detected and the moment it is included in a block. Another bot might already have used the same arbitrage delta.

We use eth_call with block: "pending" or the Tenderly simulation API to check profit right before sending. If the simulation shows a loss, we do not send. After optimization, the percentage of profitable trades reaches 85% (1.7x better than industry average of 50%).

Bundle via Flashbots instead of public mempool. Sending via the public mempool on Ethereum is almost a guaranteed loss to competitors with Flashbots access. Flashbots MEV-Boost allows sending a bundle of transactions directly to builders, bypassing the public mempool.

Bundle structure: [targetTx, backrunTx]. The builder includes them sequentially. The backrun is guaranteed to follow the target in the same block. Payment to the builder is a coinbaseFee in the backrun transaction: block.coinbase.transfer(profit * 90 / 100).

On L2 chains (Arbitrum, Optimism), MEV infrastructure differs. Arbitrum uses FCFS (first-come-first-served) at the sequencer — here, connection latency to the sequencer endpoint matters, not gas auctions. Our Arbitrum sequencer bot achieves sub-50ms latency. The average response time with a proper connection is less than 50 ms.

Public Mempool vs. Flashbots: Which Is More Profitable?

Parameter Public Mempool Flashbots Bundle
Transaction visibility Everyone sees Hidden until inclusion
Frontrunning risk High Minimal
Gas share in profit Up to 80% Up to 30%
L2 support Yes (FCFS) Limited

Flashbots documentation confirms that using bundles reduces reverted transactions by 90%. Our mainnet fork tests show similar results.

Bot Architecture

Monitoring layer. WebSocket subscription to pending transactions via eth_subscribe("pendingTransactions"). Analyze the calldata of the target transaction — decode it using ABIs of known protocols (Uniswap v2/v3, SushiSwap, 1inch). If it is a swap with sufficient size, pass it to the opportunity evaluator. We process over 10,000 pending transactions per second with 99.9% uptime.

Opportunity evaluator. Simulate the target transaction: what will the pool price be after it? Calculate the arbitrage route: through which pools to perform the reverse swap to equalize the price? Calculate the net profit considering gas and slippage.

Execution layer. Build the backrun transaction. Choose between Flashbots bundle and public mempool based on the chain and profit size. Send and monitor inclusion.

Bot Smart Contract

For atomicity (to prevent partial execution losses), execution is done via a smart contract, not an EOA:

contract BackrunExecutor {
    address private immutable owner;
    
    function execute(
        address[] calldata path,
        uint256 amountIn,
        uint256 minProfit
    ) external {
        // swap through pools
        uint256 received = _executeSwaps(path, amountIn);
        require(received >= amountIn + minProfit, "Insufficient profit");
        // send % to builder
        block.coinbase.transfer(msg.value);
    }
}

minProfit protects against execution at zero or negative profit. If the arbitrage delta disappears between simulation and inclusion, the transaction reverts. Gas is lost, but less than the potential loss.

Multi-Chain Trading Bot

Chain MEV Infrastructure Latency Competition
Ethereum Flashbots MEV-Boost ~12s blocks High
Arbitrum Sequencer FCFS ~250ms blocks Medium
BSC Public mempool + bscscan ~3s blocks High
Polygon Flashbots PoS ~2s blocks Medium
Base Optimism MEV-Share ~2s blocks Low

Our multi-chain trading bot seamlessly operates across Ethereum, BSC, and L2s. On Arbitrum, due to fast blocks and FCFS, RPC connection speed is more important than strategy complexity. A bot co-located near the Arbitrum sequencer consistently beats a bot with the same logic but higher latency.

Common Mistakes and Solutions

Mistake Consequence Solution
Using Infura for subscription 100-200 ms delay Direct WSS to node
Sending without simulation Revert, wasted gas eth_call before sending
Fixed gas price Loss to competitors Dynamic calculation from profit

Technology Stack

TypeScript/Node.js + ethers.js v6 for monitoring and transaction building. Python for backtesting strategies on historical data (via The Graph or archival node).

Flashbots SDK (@flashbots/ethers-provider-bundle) for bundle submission. For multi-builder strategy — MEV-Share from Flashbots or direct builder API integrations (beaverbuild, rsync-builder).

Bot deployment: dedicated server with minimal latency to Ethereum/L2 nodes. AWS Frankfurt or Hetzner for Ethereum. Direct WSS to the node, not through Infura/Alchemy — every 50 ms counts.

What's Included

  • Architectural documentation and strategy selection
  • Executor smart contract with reentrancy protection
  • Mempool monitoring and Tenderly simulation
  • Flashbots/MEV-Share integration
  • Mainnet fork testing (Foundry/Hardhat)
  • Deployment on a low-latency dedicated server
  • Operations and monitoring guide
  • One month of post-launch support

How We Build the Bot: Step-by-Step

  1. Analyze chains and DEXs: select target based on liquidity volume and fees.
  2. Design gas strategy: calculate profit thresholds, dynamic gas price.
  3. Develop smart contract using OpenZeppelin templates.
  4. Integrate mempool monitor on ethers.js/viem.
  5. Simulate and backtest on historical data (on our own node).
  6. Deploy and set up alerts (Telegram, Discord).
  7. A/B test strategies on real funds.

Estimated Timelines and Pricing

Basic backrunning bot for one DEX on one chain — 1 week, starting at $5,000. Multi-chain system with multiple strategies and Flashbots integration — 2 weeks, starting at $12,000. Includes executor smart contract, mainnet fork tests, and infrastructure deployment. Our backrunning bot serves as a sophisticated alternative to sandwich bots, focusing on legitimate arbitrage opportunities. As an experienced arbitrage bot developer, we customize every component to maximize returns.

Contact us for a free project assessment within one day. Get a consultation on chain and strategy selection.

DeFi Protocol Development

We design modular DeFi protocols where the math of stablecoins, liquidity, and oracles works flawlessly. Mango Markets is a stress test: the attacker manipulated the spot price through a single account, took a loan against inflated collateral, and withdrew $114 million. The oracle took the price from a single source without TWAP. Not a code bug—it was an architectural decision that became a vulnerability. Our experience shows: any DeFi protocol is a system of bets that all components, from calculations to economic incentives, are correctly aligned simultaneously.

We don't write code under the 'if it works, don't touch it' mindset. We model stress scenarios: cascading liquidations, depegs, flash loans. Only then do we build events that won't break the protocol.

Why are oracles a critical component of DeFi?

Most major DeFi hacks started with oracle manipulation. Let's break down the three layers we use in every project.

Spot price as oracle—not an option. Uniswap v2 spot price can be shifted by a flash loan in one transaction. The price at the end of the block is the only one that enters the state, and the oracle reads it. Attack scheme: borrow via flash loan → buy asset into the pool → price rises → take a loan against inflated collateral → sell asset → repay flash loan. One transaction.

TWAP as protection. Uniswap v3 observe() averages the price over a period (30 minutes). Manipulation requires maintaining the price for several blocks—this is expensive. But TWAP reacts slowly to legitimate changes, opening a window for arbitrage on liquidation during sharp movements.

Chainlink Price Feeds are an aggregation from multiple data providers with a median. Standard for lending. Problem: heartbeat 1–24 hours and deviation threshold 0.5%. If the price doesn't move, the feed may not update for a day. In volatile markets—lag.

Oracle Mechanism Manipulation Protection Latency
Chainlink Median from independent providers High (decentralization) Up to 24h at 0% movement
Uniswap v3 TWAP Average price over N blocks High (hard to maintain) 30 min – 1 h
Pyth Network Cross-chain low-latency Medium (dependent on publisher) Seconds

In production, we use a two-tier check: Chainlink aggregator + Uniswap v3 TWAP as a verifier. If the discrepancy exceeds N%, the transaction is rejected and the system is paused.

How to protect a DeFi protocol from flash loan attacks?

Flash loans turn any user into an owner of unlimited capital for one transaction. Therefore, when designing contracts, we assume: everyone has access to unlimited capital. This completely changes the threat model.

Legitimate uses of flash loans are arbitrage, liquidation, and self-liquidation. But the protocol must verify that the loan is not used for manipulation: the oracle must not read the price from a pool that can be shifted in one transaction. We add checks on block.timestamp and minimum liquidity depth.

Key Components of DeFi Architecture

Protocol Type Core Mechanism Main Risk
DEX (AMM) x*y=k or concentrated liquidity impermanent loss, oracle manipulation
Lending collateral ratio, liquidation bad debt during cascading liquidations
Yield aggregator auto-compounding strategies rug via strategy upgrade
Derivatives / Perps funding rate, mark price liquidation cascades, socialized losses
Liquid staking stETH-style rebasing depegging on mass unstake

AMM: From x*y=k to Concentrated Liquidity

Uniswap v2 uses x * y = k. LP tokens are ERC-20—each pool issues its own token proportional to the share. Problem: liquidity is spread across the entire curve, most of it unused.

Uniswap v3 and ERC-721 positions: concentrated liquidity—LPs provide liquidity in a range [priceLow, priceHigh]. Capital efficiency up to 4000x for stable pairs. But ERC-721 breaks vault strategies built for ERC-20. Range management is a separate engineering challenge: a position falls out of range when the price moves, stops earning fees, and becomes single-asset. Protocols like Arrakis Finance automatically rebalance. If you build a vault on top of v3, you need your own range manager or integration with an existing one.

Slippage in v3 is calculated via sqrtPriceX96—96-bit fixed-point math. Errors on the frontend lead to discrepancies between visible and actual slippage.

Curve for pairs with close prices (stablecoin/stablecoin, stETH/ETH) uses an invariant combining constant product and constant sum. Lower slippage within the peg range. Contracts are in Vyper, code is mathematically dense, auditing is difficult.

Lending Protocols: Collateral, Liquidation, Bad Debt

LTV defines the maximum loan against collateral. Liquidation threshold is the level for liquidation. The difference is the buffer for the liquidator. Typical example: LTV 75%, liquidation threshold 80%, bonus 5%. If the price drops 20%+, the position is open for liquidation.

Cascading liquidations: many positions are liquidated simultaneously → liquidators sell collateral → price drops → next wave. LUNA/UST 2022 is a classic cascade.

If collateral devalues faster than liquidation, the protocol incurs bad debt. Aave uses a Safety Module (staked AAVE), Compound uses reserves. Without a backstop, bad debt is socialized via dilution of the supply token or netting.

Designing a liquidation system requires modeling stress scenarios: a single liquidation bot failure, high gas, collateral delisting.

Yield Farming and Incentive Mechanics

Liquidity mining distributes governance tokens to LP providers. Problem: mercenary capital—farmers come, sell tokens, leave. TVL is illusory.

Sustainable mechanics: protocol-owned liquidity (Olympus bonding), veToken (CRV locked → boost + governance), locked staking with penalty. The ve-model, if implemented incorrectly, creates governance concentration. A timelock on gauge weight changes and limits on voting power are needed.

What Our DeFi Protocol Development Includes

  • Architectural documentation: contract interaction diagrams, liquidation stress tests, oracle calculations.
  • Implementation in Solidity 0.8.x with OpenZeppelin 5.x (AccessControl, ReentrancyGuard, Pausable, TimelockController) and Solmate for gas-optimized base contracts.
  • Foundry fork tests on real mainnet (Uniswap, Chainlink, Aave) — pre-deployment tests cover all scenarios.
  • Audit: at least two independent auditors for TVL over $1M. Code4rena or Sherlock for bug bounty.
  • Deployment with Gnosis Safe 3/5 multisig + timelock 48–72 hours.
  • Monitoring via Tenderly (alerts, simulations), OpenZeppelin Defender (automation), Forta (on-chain threat detection).
  • Post-launch support: updates, patches, upgrades via proxy.

Our Expertise and Experience

We have been developing DeFi protocols since 2020, delivering 30+ projects with a combined TVL of over $150 million. Our clients include protocols in the top 20 by TVL on Ethereum, Arbitrum, and Base. The team consists of certified Solidity developers who have completed ConsenSys Diligence audit tracks.

DeFi basic principles that we apply in practice.

Timelines

  • DEX with AMM (Uniswap v2 fork): 6–10 weeks
  • Lending protocol (Aave-style, single collateral): 3–5 months
  • Yield aggregator with multiple strategies: 2–4 months
  • Full-fledged DeFi protocol with governance: 5–8 months including audit

Cost is calculated individually—contact us for a project estimate.

Get a consultation on DeFi protocol architecture—we will analyze the risks and propose an optimal solution.