MEV Sandwich Bot Development for Ethereum

MEV Sandwich Bot Development for Ethereum

We develop professional sandwich bots that exploit the slippage tolerance of DEX users — a proven MEV extraction strategy. Using Rust, Flashbots, and custom simulators, our bots execute arbitrage, liquidations, and sandwiches with over 95% inclusion rate. Specifically, a sandwich bot spots a victim in the mempool, inserts its own purchase before the victim's (frontrun), the victim moves the price up, and the bot sells after (backrun). The difference is the bot's profit, while the victim loses only within their slippage tolerance. This is arbitrage on transaction ordering information.

Developing such a tool is a challenge of speed (mempool latency), economics (profitability calculator), and infrastructure (reliable deployment without losses). With over 10 years in blockchain development and 50+ MEV bots deployed, we create profitable bots in highly competitive environments. We'll assess your project and provide a detailed profitability calculation.

Why Most Sandwich Bots Are Unprofitable

Inaccurate Profit Calculation

The most common mistake is calculating profit without accounting for all costs. Real P&L:

profit = amountOut_backrun - amountIn_frontrun
costs = gasCost_frontrun + gasCost_backrun + builderTip
netProfit = profit - costs

gasCost with aggressive tips on Ethereum mainnet is not negligible — often $3–$8 per bundle. If a sandwich yields $10, but the builder tip is $5, net profit is only $5. The bot must simulate the entire bundle before submission and discard deals with negative net profit. Simulation via eth_call is slow. We use in-process EVM simulators (revm in Rust) for microsecond evaluation, achieving a median delay under 50 ms.

Revert Due to Price Impact Calculation

The bot calculated profit at time T, sent the transaction after 50 ms. In that interval, another bot executed its own frontrun. The pool state changed, price moves more than calculated, the victim exceeds their slippage tolerance, and their transaction reverts. The backrun is unnecessary, but gas for the frontrun is wasted — average cost per failed attempt: $2–$4. Protection: the backrun transaction is conditional — it verifies that the target transaction was actually included. In Flashbots bundles, this is realized via reverting_tx_hashes — if the victim reverts, the entire bundle is dropped.

Competition and Builder Relationships

On Ethereum, 95%+ of MEV bundles go through block builders (Flashbots, beaverbuild). A bot sending transactions directly to the public mempool loses. Proper infrastructure: MEV-Share, direct connections to top builders, monitoring of mev-boost relays. We ensure integration with leading relays to maximize inclusion rate, typically over 90%.

How to Optimize Execution via Flashbots?

The architecture of a production sandwich bot includes:

1. Mempool monitoring with direct peer-to-peer connections and bloXroute feeds. We set up a custom node with --txpool.pricelimit 0.
2. Candidate filtering: only known DEX routers, decoded calldata with slippage > 0.5%, sufficient gas price.
3. Optimal frontrun amount calculation: for Uniswap V2 — analytical solution, for V3 — numerical optimization. Account for marginal cost of each additional dollar.
4. Execution via Flashbots with conditional bundle:

const bundle = [
  { signer: wallet, transaction: frontrunTx },
  { hash: victimTxHash },
  { signer: wallet, transaction: backrunTx }
];

const bundleResponse = await flashbotsProvider.sendBundle(
  bundle,
  targetBlockNumber,
  { minTimestamp: 0, maxTimestamp: 0, revertingTxHashes: [victimTxHash] }
);

revertingTxHashes is key: if the victim reverts, the entire bundle is dropped, the bot doesn't lose gas on a frontrun without a backrun.

Chain Comparison for Sandwich Attacks

Our bots operate on all these chains. For each, we select the optimal strategy — on Ethereum, focus on builder relationships; on BSC, speed and low fees. Average daily net profit per bot can range from $200 to $2000 depending on market volatility.

Key Efficiency Metrics

We monitor every metric via Prometheus + Grafana. We guarantee transparency of operations.

What's Included

• Analysis of target chain and DEX ecosystem (2–3 days)
• Development and testing (2–3 weeks for base version)
• Deployment on mainnet with limited positions and optimization (1–2 weeks)
• Delivery of full documentation, infrastructure access, team training
• 1-month post-launch support

Work Process

1. Research — assessment of MEV opportunities via Dune Analytics and custom scripts.
2. Design — selection of stack, architecture, configuration of mempool feeds.
3. Development — coding in Rust, smart contract deployment, Flashbots integration.
4. Testing — backtesting on historical blocks in Foundry fork, paper trading on testnet.
5. Launch — mainnet deployment, A/B parameter testing.
6. Optimization — continuous tuning to current market conditions.

Estimated Timelines and Pricing

• Base Uniswap V2/V3 bot: 1–2 weeks — $5,000–$8,000
• Multi-DEX + multichain: 3–5 weeks — $12,000–$18,000
• Timelines include all stages from research to optimization

Pricing is project-based; we provide a fixed quote after assessment. Typical ROI: bot recovers development cost within 2–4 months of operation.

Tech Stack

We write the bot in Rust with the alloy library for maximum performance. Critical components — EVM simulator (revm), mempool streaming, bundle submission — are in a single process without inter-process communication. Smart contract for atomic execution is in Solidity 0.8.x with minimal footprint. Monitoring: Prometheus + Grafana.

Rust is 10x faster than TypeScript for transaction simulation — giving an edge in the MEV race.

Common Mistakes in Self-Development

• Using ready-made open-source bots — they are already exploited, competition is high.
• Ignoring gas costs for empty blocks — the bot can operate at a loss.
• Lack of revert conditions — gas loss on every failed frontrun.

We eliminate these issues at the design stage. Contact us for a free consultation — we'll assess profitability and propose the optimal solution.

Source: Flashbots Documentation

MEV on Wikipedia

Contact us for a free project assessment. Get a consultation on strategy and chain 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.

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

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.