JIT Liquidity System Development for Uniswap v3

Development of a JIT Liquidity System

JIT liquidity is an MEV strategy that Uniswap Labs calls "honest MEV" as opposed to sandwich attacks. The mechanics: in the same block as a large swap, a provider adds concentrated liquidity around the current price, earns fees from that swap, and removes the liquidity in the same block — three on-chain operations plus fees in one transaction. According to our backtests, the JIT strategy generates 3–5 times more fees than passive liquidity provision in the same range. On Ethereum mainnet at 30 gwei gas and a pool fee of 0.3%, the average income from a single JIT cycle on ETH/USDC is about $50–200, with gas costs of $10–30. On L2, like Arbitrum, gas is 10–20 times cheaper, making JIT profitable for swaps from $100.

Our team specializes in turnkey JIT systems: from mempool analysis to deployment of gas-optimized contracts. Over our work, we have completed more than 20 projects for clients from different jurisdictions.

How JIT Intercepts Fees

Concentrated liquidity and fee share. In Uniswap v3, swap fees are distributed proportionally to liquidity in the active tick range. If a JIT position adds $1M liquidity in a narrow range at the moment of the swap, while all other LPs have $500k in that same range, JIT receives 66.7% of the swap fee.

The strategy is profitable when:

• The swap is large enough (otherwise fees don't cover gas for three operations).
• The tick range is narrow enough (larger share, less temporary loss while holding).
• The position is held for one block (zero impermanent loss risk).

Minimum swap size for break-even depends on network and gas: on Ethereum mainnet at 0.3% fee and average gas price, a swap in the thousands of dollars is needed; on L2 (Arbitrum), a few hundred.

Why JIT Only Works with Bundle Submission

JIT requires seeing the swap in the mempool before it is included in a block. Private mempool via Flashbots MEV-Share or public mempool via WebSocket — between transaction detection and inclusion of your bundle — seconds.

Optimal infrastructure:

• Own node with MEV-Geth or reth with mempool websocket.
• Connection to Flashbots MEV-Share to view hints about pending swaps.
• Bundle submission via eth_sendBundle — atomic inclusion of all three transactions in one block.

Without bundle submission, JIT does not work: if addLiquidity and the swap end up in different blocks, the strategy is pointless and unprofitable.

JIT System Architecture

Off-chain Components

Mempool scanner: WebSocket subscription to node, filtering Uniswap v3 swaps by exactInputSingle/exactInput selector. Decode calldata to determine pool, size, slippage.

Profitability calculator: for each candidate computes:

1. Expected fee = swapAmount * feeTier.
2. Fee share = depositAmount / (poolLiquidity + depositAmount).
3. Gas cost of bundle = (addLiq + removeLiq + collect) * gasPrice.
4. Net profit = (fee * share) - gas.

If net profit exceeds threshold (a few tens of dollars), bundle is sent.

Bundle builder: creates three transactions for Flashbots bundle:

• tx1: mint position in the required tick range.
• tx2: original swap (backrun).
• tx3: burn + collect position.

Smart Contract for JIT Operations

The contract wraps liquidity operations and minimizes gas:

function executeJIT(
    address pool,
    int24 tickLower,
    int24 tickUpper,
    uint128 liquidity,
    bytes calldata swapData
) external onlyOperator {
    // tx1: add liquidity
    INonfungiblePositionManager(NPM).mint(MintParams({...}));
    // tx2: forward swap (in bundle via Flashbots — separate tx)
    // tx3: remove liquidity + collect
    INonfungiblePositionManager(NPM).decreaseLiquidity(...);
    INonfungiblePositionManager(NPM).collect(...);
}

Important: the contract must have sufficient balance of both pool tokens to add liquidity. Balance management is a critical operational aspect.

Tick Range Selection

A narrow range maximizes fee share but increases risk: if the swap moves price outside the range, the JIT position becomes inactive. For a swap without significant price impact (<0.5%), a range of ±0.3% from current price is sufficient. For large swaps with 1–2% price impact, the range should be expanded to ±2%.

Risks and Limitations

Revert risk of bundle. If the original swap reverts (e.g., due to trader's slippage protection), the entire bundle reverts. Gas for addLiquidity is lost. Mitigation: only include swaps with loose slippage tolerance (>1%).

Competition with other JIT bots. On highly liquid pairs (ETH/USDC), dozens of bots compete for the same swaps. Gas wars via priority fee can destroy profit. A more profitable strategy is on mid-cap pairs with low competition.

Uniswap v4 and JIT. With the advent of hooks, pools may introduce a beforeAddLiquidity hook with a minimum holding time — a direct countermeasure against JIT. Several pools are already testing such mechanisms.

Process and Timeline

Total: 1–2 weeks to launch. Cost is calculated after specifying target pools and networks. Contact us for an individual estimate.

What's Included

• Documentation: architecture diagram, configuration description, launch instructions.
• Access: repository with code, deployment docs, API keys (if required).
• Training: system walkthrough, knowledge transfer to your team.
• Support: one week of post-release monitoring and critical bug fixes.

Our engineers have years of experience in blockchain development and the DeFi market. We guarantee transparent support at all stages. Schedule a consultation to learn how JIT can increase your returns on Uniswap v3.

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.