Liquidity
In a betting pool, liquidity is token collateral already deposited in a smart contract. It can accept wagers and pay valid claims under encoded rules.

Instant settlement starts long before the final whistle.
A late goal lands, the oracle confirms the score, and a winning on-chain ticket becomes claimable within seconds. There is no cashier scrambling to collect losing stakes or transfer money from a house account. The contract can pay only from assets it already controls.
That is the job of a betting liquidity pool. Providers deposit tokens before wagers are accepted, and the protocol reserves enough of that balance against possible winnings. Once the result arrives, the contract releases the reserved amount to winners and returns any unused portion to available liquidity. A displayed pool balance is not necessarily spendable: some funds may already back unsettled bets. If deposits are too small—or withdrawals leave too little available liquidity—the protocol must limit stake sizes, reduce offered odds, or stop taking new bets rather than promise an unfunded payout.
Liquidity
In a betting pool, liquidity is token collateral already deposited in a smart contract. It can accept wagers and pay valid claims under encoded rules.
Liquidity supplier
An individual, DAO, protocol treasury, or market operator may add capital, usually in exchange for fees and a proportional claim on the pool.
Pool share
The receipt or accounting position representing a supplier’s portion. Its value can rise with betting revenue or fall when winning payouts consume collateral.
Outcome exposure
Deposited capital is not merely parked. Until withdrawal is permitted, it backs the market’s listed outcomes and bears the net payout risk defined by that contract.
Tokens become pool liquidity only after they are deposited and usable by the contract. Even when no bet is being settled, that capital remains exposed until the contract’s withdrawal conditions are met; the supplier cannot simultaneously spend it elsewhere.
A supplier deposits approved tokens. The contract records the contribution and adds usable collateral to the pool balance.
When a bettor takes a position, the contract accepts the stake only if the pool can cover the resulting exposure under the on-chain betting process.
The contract updates balances and reserves enough collateral for potential winnings. Reserved funds remain in the pool but cannot safely support withdrawals or additional bets.
After the event, an oracle or approved resolution process submits the outcome. Finality may require a waiting or dispute period.
Once settlement is final, losing positions release their reserves. Winning claims become withdrawable, and the contract transfers payment from pooled collateral according to its payout rules.
The contract enforces deposits, exposure limits, reserves, and transfers. It usually does not determine who won the real-world event. That result comes from the designated oracle or governance process; the contract then applies it mechanically.
A winning claim is useful only if spendable assets remain available at settlement. Collateral reservation protects those assets from withdrawals, new bets, or other uses while the result is unresolved. Once the outcome becomes final, the reserved amount can be transferred to winners rather than merely recorded as money owed.
The funding mix depends on the pool design:
Suppose losing positions release $65, but an additional $80 is required beyond the winners’ returned stakes. The missing $15 must come from capital already committed by liquidity providers. A spread or fee may have reduced that shortfall beforehand, but neither creates funds after the result.
This is the core risk taken by providers: losing wagers often offset winning claims, yet they may not offset them completely. Reserving collateral makes that residual exposure payable even when the betting book finishes heavily one-sided.
A liquidity pool does not always “take the other side” like a traditional bookmaker. The source of a payout depends on how bets are paired and priced; protocols using different liquidity models can therefore show similar balances while carrying very different obligations.
All stakes enter a common pot. After fees, winners divide the money supplied by losing bettors, so the final payout per winning unit remains unknown until betting closes. Collateral accumulates as wagers arrive and is effectively committed for the event’s duration.
An order book matches bettors offering opposite positions at agreed odds. Each side provides the funds needed to honor its own potential loss, commonly when an order is matched rather than merely posted. The platform may custody or escrow that collateral, but it is facilitating counterparties—not necessarily funding winners itself.
An AMM quotes prices from a formula and accepts trades against pooled liquidity. Here, liquidity providers supply collateral before demand appears, and protocol rules continuously adjust prices and reserve requirements as positions become unbalanced. Winning claims may draw partly from losing stakes and partly from provider-funded reserves.
The practical distinction is when certainty arrives: pari-mutuel payouts become clear after the pool closes, order-book liability becomes fixed at matching, and AMM exposure changes with each trade. Hybrid designs can combine these mechanics, so the settlement rules matter more than the label.
Consider a market with only Outcome A and Outcome B, both offered at even-money odds. Bettors stake $100 on A and $60 on B. A winning ticket returns twice its stake, including the original principal.
Before settlement, the pool must be ready for either result:
| Final result | Winning claims | Stakes collected | Provider capital needed |
|---|---|---|---|
| Outcome A | $200 | $160 | $40 |
| Outcome B | $120 | $160 | $0 |
If A wins, its bettors receive $100 of returned stake plus $100 of profit. The $60 staked on losing Outcome B covers most of that profit; $40 of provider capital absorbs the imbalance.
If B wins, its bettors receive $60 of returned stake plus $60 of profit. The losing $100 staked on A covers the profit completely, leaving $40 that can be released according to the pool’s rules.
This is the basic accounting behind how an automated market maker uses pooled liquidity. Prices may move as bets arrive, but the pool still tracks the largest potential claim and reserves enough collateral to honor it.
Fees should remain a separate line item. If the platform charges a trading or entry fee, that revenue does not replace the $200 or $120 payout principal unless the rules explicitly say so.
The pool does not reserve for both outcomes paying simultaneously. It holds enough for the largest valid settlement liability, then releases any collateral no longer needed once the result is final.
A pool’s headline balance can overstate its usable depth. Bet capacity comes from unencumbered collateral—assets left after reserving enough for unsettled claims. A large pool can therefore accept bigger stakes with less disruption, while a heavily utilized pool may have little room despite holding substantial funds.
Dynamic odds help prevent demand from accumulating on one outcome. As more money backs one side, its odds generally shorten, reducing the payout promised on additional bets and making the other side relatively more attractive. In automated markets, a large order may move through several price levels; this difference between the initial quote and average execution price is slippage.
Several controls reinforce that pricing response:
Together, these mechanisms keep promised payouts within available assets. Deeper pools usually offer steadier prices and larger capacity; shallow or highly committed pools respond with sharper odds movement, smaller maximum bets, or temporary closure.
Check oracle challenge periods, contract audits, collateral type, withdrawal queues, and emergency controls. “Withdrawable” liquidity can shrink precisely when markets become volatile or disputed.
Identify backing: bettor stakes, counterparties, provider deposits, or a mix. Confirm the tokens sit in the named contracts.
Calculate the largest net payout from open interest, odds, and limits; do not rely on headline TVL.
Subtract reserved claims, locked funds, and capital serving other markets from visible on-chain balances.
Check the oracle, finality period, void conditions, market wording, and treatment of delayed or ambiguous outcomes.
Look for lockups, queues, pauses, and any provider right to remove backing before settlement.
Find challenge windows, adjudicators, appeal rights, and who absorbs losses from oracle or contract failures.
A winning bet does not create money. Payment depends on capital committed beforehand, properly reserved, and released under enforceable settlement rules. Documentation describes the promise; contract balances and transaction history show whether the backing exists.