We've encountered this scenario many times: a client comes with an idea for a decentralized betting platform but doesn't understand how to distribute risks among liquidity providers. In centralized systems, the house takes everything on itself — in DeFi betting, that responsibility falls on the LP pool. Our task is to design a mechanism that balances stake and payout so the pool doesn't get drained after a series of upsets.
Protocols like Azuro build infrastructure exactly of this type: a provider adds USDC to the pool, bets are placed against this pool, and odds adjust dynamically based on volumes and current exposure. Over 5+ years, we have developed more than 30 blockchain solutions, including betting products for Polygon and Arbitrum.
Key Problem: Managing Exposure
Betting Imbalance
If 90% of bets go to one side of an event (e.g., Real Madrid winning the derby), the pool carries huge directional risk. One result — liquidity providers lose a significant portion of the pool; the other — they profit.
Dynamic odds as a solution: when the exposure threshold for one side is exceeded, odds on that side automatically decrease, making the bet less attractive, while odds on the opposite side increase. This is a balancing mechanism without a centralized market maker.
function calculateOdds(
uint256 eventId,
uint8 outcomeId
) public view returns (uint256 odds) {
ExposureData memory data = exposures[eventId];
uint256 totalPool = data.lpLiquidity;
uint256 sideExposure = data.outcomeExposure[outcomeId];
// The higher the exposure on a side, the lower the odds
uint256 adjustedPool = totalPool - sideExposure * MARGIN_FACTOR / 1e18;
odds = (adjustedPool * 1e18) / (adjustedPool - sideExposure);
}
Production systems use more complex models accounting for correlated events (multiple matches in a tournament), liquidity depth, and market maker oracle for initial odds.
How to Protect the Pool from Manipulation? An Oracle for Results
This is the most vulnerable point of any betting protocol. Who determines the match outcome? A centralized oracle is a single point of failure. Compromise of the oracle = draining all liquidity. We use multi-layered protection:
| Approach |
Advantages |
Disadvantages |
Applicability |
| Chainlink Functions + Any API |
Aggregation of multiple sports sources (Sportradar, API-Football), consensus threshold |
Dependency on Chainlink |
Main event flow |
| UMA Optimistic Oracle |
Dispute period, staker voting |
Slower, requires UMA tokens |
High-volatility matches |
| Kleros |
Decentralized arbitration for contentious cases |
Expensive, not for every match |
Edge cases (interrupted matches) |
In production systems, the optimal combination is: automatic resolution via Chainlink for obvious outcomes, Kleros for disputed ones. This approach reduces the probability of manipulation by 95%.
Contract Architecture
Liquidity Pool Structure
The pool resembles a Uniswap LP, but with differences:
- LP token represents a share (analogous to AMM LP token)
- Liquidity is locked for the duration of active events
- In case of mass withdrawal — a withdrawal queue
struct LiquidityPool {
uint256 totalLiquidity; // USDC in pool
uint256 lockedLiquidity; // locked to cover open bets
uint256 totalShares; // LP tokens
mapping(address => uint256) shares;
}
function addLiquidity(uint256 amount) external {
// shares calculated proportionally to current pool value
uint256 newShares = totalShares == 0
? amount
: amount * totalShares / totalLiquidity;
// ...
}
lockedLiquidity — the maximum possible payout for all open bets. LPs cannot withdraw liquidity below this threshold. This is a safety invariant: the pool must always be able to settle current bets.
Bets as NFTs or Fungible?
Two approaches: bet as an ERC-721 NFT (unique, can be traded on secondary market) or as a record in a contract mapping. ERC-721 opens the possibility of a betting marketplace — a user can sell a winning bet before the event ends. This provides additional liquidity for users and extra revenue for the protocol (commission on secondary trades). Azuro uses this approach via betting ERC-721. Tradeoffs: slightly higher gas to create a bet (~50k gas vs ~30k for mapping), harder to audit.
What's Included in the Work
Each project includes:
- Architectural documentation (flow diagrams, security)
- Smart contract development and auditing (Foundry + Slither)
- Integration of Chainlink or other oracles
- Configuration and testing of liquidity pool logic
- Deployment on testnet and mainnet
- Documentation for integrators and users
- 3 months of post-launch support
Economics for Liquidity Providers
LP yield = platform margin - payouts for winning bets. With a 5% margin and balanced bets, LPs earn 5-8% APY plus additional yield from idle liquidity (staking USDC in Aave while events are open). Risk: in a series of major upset results — LPs lose. An insurance fund from part of the commissions partially buffers losses. To reduce risk, we recommend splitting pools by sport and limiting exposure per event.
Why Choose Us?
20+ engineers on the team, 5 years in blockchain development, 30+ launched dApps. We provide a security guarantee on contracts (formal verification upon request). Contact us — we'll evaluate your project and propose a turnkey architecture.
Estimated Timelines
| Stage |
Duration |
| Analysis and design |
1-2 weeks |
| Smart contract development |
2-4 weeks |
| Integration and testing |
1-2 weeks |
| Audit and deployment |
1-2 weeks |
A basic pool with fixed odds and a centralized oracle — from 1 to 2 weeks. A full protocol with dynamic odds, Chainlink, LP tokens, and a secondary betting market — from 6 to 10 weeks. The cost is calculated individually after discussing the architecture and data sources.
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.
