How to Build a DEX Arbitrage Bot: Gas, MEV, and Profitability Guide

On Uniswap V3 ETH/USDC, the price is $3,201.50; on SushiSwap, it's $3,199.80. The difference is $1.70 per ETH. To make a profit, you need to account for gas: 21,000 + 150,000 (two swaps) ≈ 170,000 gas × 30 gwei × $3,200 / 1e9 ETH = ~$16 on gas. So, for a $1,000 trade, the difference must be at least 1.6%, while for $100,000, 0.016% is enough. DEX arbitrage only works with sufficient position size or price discrepancy — flash loans make this business accessible without own capital. A typical trade yields between $200 and $500 in net profit.

With 5+ years in DeFi and 10+ projects delivered, we ensure reliable bot development. Our clients typically see ROI within 3 months. Gas optimization can save up to $15 per transaction, and development cost starts at $5,000 for a basic bot.

Why DEX Arbitrage Bots Often Fail to Generate Profit

Mempool Competition and MEV

The toughest adversary for a DEX arbitrageur is MEV bots with direct access to block builders. Through Flashbots eth_sendBundle, a transaction goes directly to the builder, bypassing the public mempool. Flashbots provides a private submission mechanism that is 3 times better than public mempool for transaction success rate: the success rate of transactions increases by 2–3 times.

If your bot sends transactions to the public mempool, you're in a losing position. The usual gas auction means other bots see your transaction, assess profitability, and outbid you with higher gas. The solution: send all transactions through Flashbots or MEV Blocker (an aggregator of multiple private relays). Additionally, include multiple transactions in a single bundle with atomic execution.

Our Solidity-based arbitrage bot development incorporates MEV protection through Flashbots, enabling efficient cross-chain arbitrage and smart contract arbitrage. Transaction optimization is critical, and we achieve it through careful gas profiling. Arbitrage between DEXs like Uniswap and SushiSwap is the most common strategy.

Slippage and Real Price Calculation

The problem with most beginner implementations: calculating arbitrage opportunity based on the pool's spot price without accounting for price impact. The actual price after a swap depends on the current liquidity in the active range (Uniswap V3), transaction size, and spread across several tick ranges. For V3, correct calculation requires simulating the swap via the Quoter contract or off-chain via @uniswap/v3-sdk. The difference between spot price and actual execution price for a $100k swap on a medium-liquidity pool is 0.3–1.5%. Without accounting for this, profitability estimates will be wrong.

Gas Optimization: The Difference Between Profit and Loss

On Ethereum mainnet, arbitrage only works with optimized gas usage. A typical mistake: two separate ERC-20 approve + swap adds +43,000 gas overhead. The solution — use permit (EIP-2612) for supported tokens, or pre-approve the maximum amount and avoid re-approving. Even more savings come from atomic arbitrage via flash loan in a single contract: no multiple transfer calls between EOA and DEX, no separate transactions. The entire arbitrage is one transaction: flash loan → swap A → swap B → repay loan → profit. Gas for such a transaction: 200,000 – 400,000 depending on protocols. Optimal gas settings save up to 30% in fees.

How to Build a Reliable DEX Arbitrage Bot

What Technology Stack Is Used?

• On-chain contract in Solidity 0.8.x executes the trade atomically, implements a flash loan callback (Aave IFlashLoanReceiver or Uniswap V3 IUniswapV3FlashCallback), performs swaps, and checks for profit.
• Off-chain executor in Rust monitors pools via WebSocket subscriptions to our own Ethereum nodes, calculates paths using the Bellman-Ford algorithm (see Wikipedia), and submits transactions via Flashbots.

Example contract:

function executeArbitrage(
    address tokenIn,
    uint256 amountIn,
    SwapPath[] calldata path,
    uint256 minProfit
) external {
    // Flash loan from Aave
    // Execute swaps along path
    // Assert profit >= minProfit, else revert
    // Repay flash loan
    // Transfer profit to owner
}

Reverting on insufficient profit is a key protection: if the market moves, the contract rolls back, spending only base gas (~21,000), not the full gas of swap execution.

Comparison of Arbitrage Strategies

Multi-hop arbitrage can be 2 times more profitable than simple two-sided arbitrage. In practice, the flash loan with Flashbots bundle strategy shows 1.5–2 times more profitable transactions compared to regular mempool submission.

Optimal Path Finding: Bellman-Ford

For multi-hop arbitrage (A→B→C→A), finding a profitable path is equivalent to finding a negative cycle in a price graph. The classic algorithm is Bellman-Ford on a graph where nodes = tokens, edges = pools, weights = log(exchange_rate). In practice, for 5–10 DEXes and 50–100 tokens, the graph is small, and Bellman-Ford runs in milliseconds.

Development Process

1. Analytics (2–3 days). Identify target DEXes, networks, token pairs. Analyze the competitive environment — how many bots are already operating in the chosen segment.
2. Contract development (1 week). Flash loan integration, multi-hop swap logic, profit assertion. Test on a mainnet fork using Foundry.
3. Executor development (1–2 weeks). WebSocket pool monitoring, Bellman-Ford / path finding, Flashbots bundle submission.
4. Optimization and deployment (3–5 days). Gas profiling, fine-tuning minProfit thresholds, deployment to production.

Monitoring and Risk Management

An arbitrage bot in production requires monitoring several metrics: transaction win rate (if > 30% revert, executor is too slow), gas efficiency, capital utilization, competitive environment. We use Grafana + Prometheus for metrics and alerts via a Telegram bot.

What's Included in the Work

We provide: source code of the contract and executor, deployment documentation, access to monitoring (Grafana dashboard), team training, technical support for 30 days after launch.

Contact us for a detailed discussion of your project. Order bot development with guaranteed support — get a consultation from experts with 5 years of DeFi experience.

Timeline Estimates

Basic bot (2 DEXes, one network, flash loan) — 1–2 weeks. Multi-DEX, multi-path with Flashbots integration — 2–4 weeks. Cross-chain or advanced MEV strategies — from 6 weeks. Cost is calculated individually.

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.