Polymarket processed over $1.5 billion in trading volume for the US presidential elections. The mechanics of a prediction market are simple: users buy shares of an event, the share price equals implied probability. If the event occurs, the share is worth $1. If not, $0. The market aggregates information and 'predicts' probabilities more accurately than most analysts. Building such a system technically involves three independent tasks—market creation, liquidity maintenance, and automated resolution—each with its own vulnerabilities. Our team has 5+ years of experience in DeFi, having delivered over 20 blockchain projects on Ethereum, Polygon, and Solana. Contact us to discuss your task.
How to Avoid Oracle Manipulation?
The most vulnerable part of a prediction market is the resolution mechanism. The resolution mechanism decides whether the event occurred. There are three options: trusted oracle (centralized), Chainlink/UMA (dependence on third-party protocols), optimistic resolution with a dispute period (decentralized, but latency). Oracle manipulation is one of the main threats. Chainlink is fast and reliable for verifiable events like crypto prices, but not suitable for subjective outcomes (elections, polls). UMA Optimistic Oracle is flexible and works for any event, but resolution takes 2–3 days in case of a dispute. A centralized multisig is fast and simple but requires trust and carries reputational risk. In our implementation, we choose the appropriate mechanism for each market type. For crypto price markets—Chainlink. For subjective events—UMA Optimistic Oracle. Multisig—only as a fallback when other mechanisms fail.
Why Liquidity Is the Main Problem for Prediction Markets?
Prediction markets traditionally use two approaches to liquidity: CLOB and AMM. CLOB allows users to place limit orders, providing accurate prices and minimal slippage when liquidity is sufficient, but new markets without liquidity remain empty. AMM always accepts trades via a formula, but the protocol may incur losses by subsidizing liquidity. Our approach is Hybrid: initial liquidity through protocol-seeded AMM, CLOB for large traders. The AMM uses a constant product formula adapted for binary outcomes, with LP positions acting as automated market makers.
Token Standard for Shares: ERC-1155
Each market has at least two outcome tokens (YES/NO, or multiple for multi-outcome). ERC-1155 is the right choice: a single contract manages tokens for all markets, batch transfer reduces gas when trading multiple markets simultaneously. When a market is created, conditional tokens are minted: for each 1 USDC of collateral, 1 YES + 1 NO token is created. The total value of YES + NO = 1 USDC (before resolution). After resolution, one token becomes redeemable for 1 USDC, the other becomes 0. This is the pattern of the Gnosis Conditional Tokens Framework—a battle-tested library for prediction markets. We build on top of CTF, not from scratch.
System Architecture
Contract Layer
| Component |
Purpose |
| MarketFactory |
Creates new markets. Parameters: question, resolution source, expiry, initial liquidity. Deploys an AMM pool for each new market. |
| ConditionalTokens (CTF) |
Gnosis open-source contract for issuing conditional tokens. Audited multiple times, with production history on Polymarket. |
| FixedProductMarketMaker (FPMM) |
AMM contract for each market. Uses a constant product formula adapted for N outcomes. LP providers add liquidity, receive LP shares, and earn from trading fees. |
| ResolutionModule |
Manages the resolution process. Integrates with Chainlink/UMA, provides a dispute mechanism. |
| TreasuryManager |
The protocol takes a fee (0.5–2%) from each trade. Manages protocol reserves used for initial seeding of liquidity for new markets. |
Market Creation and Initial Liquidity
Bootstrapping liquidity is one of the hardest tasks. Strategy: Protocol-seeded markets—popular markets (elections, crypto events)—the protocol adds initial liquidity from the treasury. LP shares remain with the protocol. User-created markets—anyone can create a market by depositing initial liquidity. This incentivizes market creators—they earn trading fees from their own market. Conditional liquidity rewards—LPs in the first N days after market creation receive additional governance tokens. An analogy to Uniswap liquidity mining.
Gas Optimization for Polygon/L2
Prediction markets run on L2—gas on Ethereum mainnet makes small trades ($10–50) economically unviable. Polygon is the historical choice of Polymarket. Alternatives: Base, Arbitrum. On L2, gas is 10–100x cheaper. ERC-1155 batch transfer reduces gas by 40–60% when trading multiple tokens simultaneously. Multicall pattern for batch operations.
Development Process
More about the stages
- Analytics (5–7 days). Define market types, resolution mechanisms for each type, protocol tokenomics. Study Polymarket, Augur, Metaculus as references.
- Contract development (5–8 weeks). CTF integration or custom implementation, FPMM logic, resolution modules. Testing via Foundry: fork tests, fuzz tests on AMM invariants (sum of probabilities = 1).
- Resolution integrations (2–3 weeks). Chainlink for verifiable events, UMA Optimistic Oracle for subjective events.
- Frontend (3–5 weeks). Interface for market creation, trading UI, portfolio, resolution tracking. wagmi + viem for contract interactions.
- Audit (mandatory). The complexity of conditional token logic and the potential volume of funds—mandatory external audit.
Typical Mistakes in Prediction Markets
- Incorrect resolution without a dispute mechanism. A rogue oracle could resolve a market in favor of one outcome for a disputed result. Without a dispute mechanism, users have no recourse.
- Infinite approval exploit. If the UI requests an infinite approve on the CTF contract and a vulnerability is discovered in it, an attacker could drain all approvals. Use limited approves or EIP-2612 permit.
- Front-running during resolution. Between the submission of a result by the oracle and its on-chain processing, there is a window for front-running. Use a commit-reveal scheme or VDF (Verifiable Delay Function) for critical markets.
Conditional tokens are a set of contracts from Gnosis that implement conditional token logic. A user deposits collateral (USDC) and receives a set of outcome tokens. When the event occurs, one token becomes redeemable for $1, and others become worthless. The framework ensures atomicity of operations and safe resolution.
What We Deliver
- Smart contract development (Solidity, Foundry)
- Integration of Chainlink and UMA oracles
- Frontend creation using wagmi/viem
- Deployment on Polygon/Arbitrum/Base
- Code documentation and technical specification
- Training of the client's team in market management
- Post-launch support (2 months)
We will evaluate your project in 2 days. Contact us for a consultation. Order turnkey prediction market development.
Timeline Estimates
| Product Type |
Timeline |
| MVP (binary markets, Chainlink, basic AMM) |
6–8 weeks |
| Full platform (UMA, user-created markets, CLOB) |
2–4 months |
Pricing 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.
| Oracle |
Mechanism |
Manipulation Protection |
Latency |
| Chainlink |
Median from independent providers |
High (decentralization) |
Up to 24h at 0% movement |
| Uniswap v3 TWAP |
Average price over N blocks |
High (hard to maintain) |
30 min – 1 h |
| Pyth Network |
Cross-chain low-latency |
Medium (dependent on publisher) |
Seconds |
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
| Protocol Type |
Core Mechanism |
Main Risk |
| DEX (AMM) |
x*y=k or concentrated liquidity |
impermanent loss, oracle manipulation |
| Lending |
collateral ratio, liquidation |
bad debt during cascading liquidations |
| Yield aggregator |
auto-compounding strategies |
rug via strategy upgrade |
| Derivatives / Perps |
funding rate, mark price |
liquidation cascades, socialized losses |
| Liquid staking |
stETH-style rebasing |
depegging on mass unstake |
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.
