Intent-Based Trading Protocol Development

Intent-Based Trading Protocol Development

We specialize in designing and deploying intent-based protocols — an architecture where a user signs an intention ("I want to sell 1 ETH for the best USDC price before 15:00 UTC"), and execution is delegated to specialized solvers. Unlike the classic DEX model where a transaction exactly describes details, the intent-based approach adapts to market conditions and protects against slippage. This architecture can reduce slippage by up to 50% compared to AMM on volatile pairs, as well as cut gas costs through batch order processing. Developing a DeFi protocol in this paradigm requires deep understanding of both on-chain and off-chain components.

This approach is implemented in CoW Protocol, UniswapX, and 1inch Fusion, each with its own trade-offs. We help you choose the optimal model for your tasks: batch auction for high volumes or first-solver for low liquidity. In practice, a fill transaction on mainnet costs $5-15, which at high volumes can mean $10-20k in monthly fees. Using batch fill can reduce gas costs by up to 40%, saving $20k on a monthly spend of $50k. For a protocol processing $10M monthly volume, batch fills could save $40k in gas alone.

How does an intent-based trading protocol work?

The user signs a structured message via EIP-712 (typed data visible in MetaMask). The EIP-712 specification ensures secure off-chain signing of structured data. Minimal order structure:

struct Order {
    address maker;
    address inputToken;
    address outputToken;
    uint256 inputAmount;
    uint256 minOutputAmount;
    uint256 deadline;
    uint256 nonce;
    bytes32 partialFillable;
}

Key point: nonce management follows a word + bit scheme (as in UniswapX), allowing up to 256 active orders simultaneously. Cancelling an order — invalidation of a bit in an on-chain mapping without a separate transaction.

Why choose an intent-based model?

Key system components

Settlement contract

The central contract verifies the signature (EIP-712 recovery), checks nonce and deadline, atomically transfers tokens via safeTransferFrom. EVM atomicity guarantees: if the solver doesn't approve outputToken — the entire transaction reverts.

function fill(Order calldata order, bytes calldata signature, uint256 fillAmount) external {
    address signer = ECDSA.recover(_hashTypedData(order), signature);
    require(signer == order.maker, "Invalid signature");
    require(!_usedNonces[order.maker][order.nonce], "Nonce used");
    require(block.timestamp <= order.deadline, "Expired");
    IERC20(order.inputToken).safeTransferFrom(order.maker, msg.sender, fillAmount);
    IERC20(order.outputToken).safeTransferFrom(msg.sender, order.maker, outputAmount);
    emit OrderFilled(orderHash, msg.sender, fillAmount, outputAmount);
}

Solver network and competition

A solver is an off-chain agent monitoring the orderbook and selecting the optimal execution route. A solver's profit is the difference between the real price and minOutputAmount (surplus). Two models are possible:

• On-chain auction (CoW Protocol): all orders for a period are batched together, one winning solver executes everything at a single price. Eliminates front-running within the batch. This model is 3x more gas efficient than a sequence of individual fills.
• Off-chain first solver (UniswapX): the first to execute the order on-chain before the deadline receives the reward. Simpler, but may lead to an MEV race.

We evaluate your specifics and propose the optimal model.

Permit2 integration

Instead of the classic approve (a separate transaction), we use Permit2 — the approval is signed off-chain along with the order. Batch permit allows one-time approval of Permit2 for each token, after which all dApps use it. This is a significant UX improvement.

Solver implementation: search and protection

The solver fetches quotes from AMMs (Uniswap, Curve, Balancer), CEX (Binance API), on-chain orderbooks, and its own inventory. It selects the best price considering gas and fees. If profit < gas * gasPrice * safetyMultiplier — the order is rejected. A common mistake of novice solvers: taking unprofitable orders hoping for MEV — this is not sustainable.

Gas optimization

On mainnet, one fill costs $5-15 at gas $50. For small orders, this is unacceptable. Solutions:

• Deploy on L2 (Arbitrum, Optimism) reduces gas by 10-50x.
• Batch fill — multiple orders in one transaction amortize base gas cost.
• Compact calldata: zero bytes are cheaper, saving 20-40% of calldata gas.

Stack and component table

Smart contract development uses Solidity 0.8.x with Foundry and OpenZeppelin 5. Smart contract audit is performed by external teams.

Process

1. Analytics (3-5 days): select model (batch or first-solver), target tokens and chains, solver network requirements.
2. Design (5-7 days): EIP-712 schema, nonce mechanism, settlement architecture.
3. Development (6-10 weeks): settlement contract, Permit2 integration, orderbook, solver, frontend.
4. Audit: mandatory external audit focusing on signature malleability, reentrancy, nonce.
5. Deployment and support: deploy to target networks, monitoring, documentation.

What's included

• Smart contract development (Settlement, Permit2 wrapper)
• Off-chain solver with liquidity integration
• Orderbook (REST API + WebSocket)
• Frontend with order signing (wagmi + viem)
• API and contract documentation
• Deployment and monitoring setup
• Team training for operations
• 3-month warranty support

Timeline estimates

MVP with basic settlement and one solver — 4-6 weeks. Production-ready protocol with batch auction, open solver network, and gas optimization — 2-3 months. Cost is calculated after defining the model and scope. Typical MVP costs range from $25k to $50k, while a full production system may cost $60k to $120k. We offer turnkey development from design to audit. Contact us for a free project evaluation — we'll analyze your requirements and propose an architecture tailored to your volume and goals.

Order protocol development — describe your task, and we'll select an architecture matching your volume and requirements. Get a consultation to discuss your project details.

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.