Developing Liquidity Systems for Prediction Markets on Ethereum and L2

A 12% spread and slippage of several percent make prediction markets useless for traders. This is where UX breaks down: users are not willing to pay such a fee for uncertainty. We develop liquidity systems that make markets deep even before organic interest appears. Our approach combines Fixed Product AMM, conditional tokens, and dynamic LP incentives. As a result, even a niche market can attract volumes up to $500k without slippage. Each contract is audited for reentrancy and correct outcome distribution, ensuring LP fund safety.

How AMM Works for Prediction Markets

LMSR and Its Limitations

LMSR (Logarithmic Market Scoring Rule) is historically the first AMM for prediction markets. Outcome prices are calculated as p_i = e^(q_i/b) / sum(e^(q_j/b)), where q_i is the number of shares of outcome i, b is the liquidity parameter. Advantage: mathematically guaranteed market maker — the market is always liquid. Disadvantage: unlimited market maker losses in extreme moves.

A later CPMM (Constant Product, as in Uniswap v2) is used in Polymarket: for a binary market YES_shares * NO_shares = k. YES price = NO_shares / (YES_shares + NO_shares). Simpler implementation, bounded losses. CPMM is 3x more gas-efficient than LMSR for binary markets.

Conditional Tokens (ERC-1155)

The modern standard for prediction markets is the Gnosis Conditional Tokens Framework. Each event outcome is a separate ERC-1155 token. Collateral (e.g., USDC) is locked in the ConditionalTokens contract. When the condition is resolved (resolveCondition()), holders of winning outcome tokens can redeem collateral 1:1. This allows building composite markets: combinations of outcomes from multiple independent conditions — "AND-markets". For example, a position "ETH > $5000 AND BTC > $100k by December" is an intersection of two conditional tokens.

Architecture of Liquidity Provisioning

Automated Market Making via Fixed Product AMM

For each market, a liquidity pool is deployed based on Fixed Product AMM (FPMM). LPs deposit equal amounts of all outcomes (for binary markets — YES and NO tokens). Initial outcome price = 50/50.

The FPMMFactory contract creates an FPMM instance for each market:

function create(
    address conditionalTokens,
    address collateralToken,
    bytes32[] memory conditionIds,
    uint[] memory outcomeSlotCounts,
    uint fee // basis points
) external returns (address fpmm)

Fee goes to liquidity providers — their incentive. But fees from prediction markets are usually low (0.1-2%), and the risk for LPs is significant: LPs hold positions in outcomes until resolution. If the market becomes highly one-sided, LPs accumulate many losing tokens that could become worthless.

Incentive Mechanics for LPs

The simplest approach is liquidity mining: additional rewards in the protocol token for LPs. But this is temporary; after mining ends, liquidity leaves.

A more sustainable approach is dynamic fee: higher fees on low-liquidity markets, lower on highly competitive ones. Implementation: fee = base_fee + liquidity_adjustment, where liquidity_adjustment is inversely proportional to pool depth. For example, a pool with $2M TVL generates $5000 in daily fees at 0.5% turnover.

Another pattern is a shared liquidity pool: instead of per-market pools, a single basket of liquidity is distributed across several markets. The contract automatically allocates liquidity where price impact is highest. Risk is diversified, capital efficiency is higher. LP commission savings reach 30%.

Oracle Resolution and Dispute Mechanism

The most sensitive part is resolving the outcome. Two approaches:

Centralized oracle. A trusted reporter address calls reportPayouts(). Fast but centralized. Acceptable for the initial phase with a multisig reporter.

Optimistic oracle (UMA-style). A proposer suggests an outcome with a bond. 48-72 hour dispute window. A disputer can challenge with a bond. If challenged, it goes to voting via UMA DVM or Kleros. The loser loses their bond. Resistant to manipulation: cost of dispute > reward from incorrect resolution.

Chainlink + Sports/Events API. For sports events, Chainlink Any API with verified sources (ESPN, official sports APIs). Declarative, automatic, no human factor. Limitation: not all events have public APIs.

Why Gas Is a Bottleneck for Prediction Markets

Prediction markets with many outcomes (>2) create gas issues. For an event with 10 outcomes (e.g., World Cup, 32 teams), an FPMM swap requires updating balances of all 32 tokens in one transaction. This is O(n) SLOAD/SSTORE operations per trade.

Optimization: lazy evaluation — store only delta changes, recompute full state only when necessary (e.g., on redeem). But this complicates logic and requires thorough invariant testing.

For markets with >5 outcomes on Ethereum mainnet, it is economically more sensible to deploy on Polygon or Base. L2 gas allows working with 20-30 outcome markets without issues. Gas cost comparison:

Development Process

1. Analytics (3-5 days). Choose AMM mechanics (FPMM vs LMSR vs custom), oracle strategy, LP incentive model, target chain.
2. Contracts (2-3 weeks). Conditional tokens setup + FPMM factory + LP incentives + oracle adapters. Foundry with property-based tests: "sum of probabilities always = 1", "redeem never exceeds collateral".
3. Oracle integration (1 week). Chainlink API or UMA optimistic oracle setup, dispute mechanism.
4. Frontend (1-2 weeks). wagmi/viem integration, trading interface, probability display, LP dashboard.

What's Included in Our Work:

• Smart contracts in Solidity (Foundry, tests, audit)
• Integration with conditional tokens and FPMM
• Oracle setup (Chainlink/UMA/custom)
• Frontend development for trading interface and LP dashboard
• Deployment on L2 (Polygon, Arbitrum) for gas savings
• Documentation and team training
• Technical support after launch

Timeline Estimates

A basic protocol for binary markets with a centralized oracle — 1-2 weeks. A full system with an optimistic oracle, LP incentives, and multi-outcome support — from 4-6 weeks.

Cost is determined after discussing market types and resolution mechanics. We are a team with years of experience in smart contracts, having delivered over 20 DeFi projects. Get a consultation: we will assess your project and propose a liquidity system architecture. Contact us to discuss.

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.