Event contracts are drawing attention in both crypto and traditional finance, but the real mechanics sit in the details. A review written by MetaHub Research and compiled and translated by PANews compares four platforms — Polymarket, Kalshi, Robinhood and TurboFlow — with a focus on quote formation, settlement flow and fee structure, while laying out the split between order-book markets and automated market maker models.
At the simplest level, an event contract lets traders take a position on the outcome of a verifiable question. If the chosen outcome is correct, the contract pays out. If not, that side goes to zero. The article argues that the important part is not the headline format of the market, but the way the contract defines time, price source, settlement logic and exceptions.
What an event contract looks like
The review groups event contracts into several common structures. There are yes/no contracts, such as whether an indicator will reach a target before a specified date. There are higher/lower contracts that compare an expiry price with the entry price. There are threshold contracts, which ask whether a final value is above, below, or not below a set number. There are also multi-outcome contracts, where several mutually exclusive results are listed and priced separately.
In each case, traders are buying and selling exposure to an outcome rather than the event itself. Contract terms generally spell out the market question, cutoff time, time zone, official data source, boundary conditions, payout logic, and the handling of delays, cancellations or unresolved results. Even markets with very similar titles may work under different rules.
How these contracts operate
The article frames the process in six steps. First, the platform defines the question, outcomes, trading deadline and settlement source. Second, prices are formed: order-book venues rely on bids and asks from traders, while automated systems generate prices through a pricing model and show stake and expected return before confirmation. Third, a filled order creates a position on one side of the result. Fourth, trading stops when the deadline, event start or another platform-specific trigger is reached. Fifth, the outcome is confirmed by the platform, exchange or predesignated oracle under the contract terms. Sixth, funds are settled.
For binary contracts, the winning side usually pays $1 per share while the losing side pays $0. Fixed-return products follow the rules locked in at confirmation.
What a 70-cent price means
In binary contracts quoted from $0 to $1, price is often read as an implied probability. If the “Yes” side trades at $0.70, the market is roughly pricing in a 70% chance at that moment. If the final result is “Yes,” the contract typically settles at $1, producing a gross gain of $0.30 before fees and spread. If the result is “No,” the contract goes to $0 and the maximum loss is the $0.70 spent.
The review is careful on one point: a displayed 70% is still just a market price. It does not guarantee that the true probability of the event is 70%. Prices can move with new information, book depth, spread and shifts in supply and demand. For products that use automated pricing and fixed returns, traders also need to look at principal, projected return and maximum possible loss together, because the quoted payout can reflect cycle length, volatility and other risk parameters.
Settlement details that matter
The article highlights several areas users need to check before entering a trade. Settlement sources may come from government agencies, sports organizers, price indexes, exchange data or an oracle. Boundary language matters too: “above 100” usually means strictly greater than 100, while “100 or above” includes equality.
Timing is another major issue. Traders need to know which point in time is used, which time zone governs the market, and whether the price sample is a spot value, a close or an average across a period. The contract also needs clear rules for delays, cancellations, corrected data, interrupted data sources or outcomes that remain unresolved for a long time. Dispute procedures, who can propose the result, how long the challenge window lasts, and who makes the final decision all affect the final payout. Fees, platform commissions, on-chain costs and withdrawal charges also change the actual return profile.
Polymarket: continuous probability trading
Polymarket is described as a prediction market built around continuous trading in event probabilities. It uses an order book for price formation and involves UMA in result confirmation.
Its markets are mainly structured as yes/no outcome shares and span politics, macro, sports, crypto assets and cultural events. These markets usually stay open until the event happens and settlement is completed.
On pricing, Polymarket uses an order book. The probability shown on the page is usually the midpoint between the best bid and best ask. When the spread is wider than $0.10, the platform switches to the last traded price for display. Matching quotes for “Yes” and “No” add up to $1.
On trading and exit, users can buy or sell outcome shares through the book as long as the market is open and a counterparty exists. Limit orders let users control execution price, but thin liquidity may make it difficult to exit at the desired level.
Settlement follows the rules published in advance for the market, with UMA’s optimistic oracle handling the result process. After an outcome is proposed, there is a challenge period. Winning shares settle at $1 each and losing shares settle at $0.
On fees, the article says official documentation currently states that some markets charge takers while makers are not charged. Parameters vary by market type, so users need to check the latest rate before entering.
The review says Polymarket suits traders who want to trade shifting event probabilities continuously, use limit orders and pay attention to market depth. It points to rule wording, spread, on-chain wallet setup, oracle dispute flow and regional availability as the main areas to inspect.
Kalshi: standardized yes/no contracts
Kalshi centers its offering on standardized yes/no contracts with clear market rules and order-book trading.
Its product set is made up mainly of yes/no contracts and threshold contracts. Individual markets usually display a rule summary, expiry conditions and the source used to verify the outcome.
Pricing also runs through an order book, with contracts quoted in cents. A 70-cent “Yes” contract and a 30-cent “No” contract can combine to form $1. Best bid, best ask and executable size directly affect trade execution.
Users can open positions through the order book and sell out if the market is still open and liquidity is available. Resting orders that do not fill can be canceled.
Settlement terms specify the information and data source used for each contract. After expiry, Kalshi confirms the result based on those terms. The platform says settlement confirmation can take from one hour after close to more than 12 hours, depending on the data source.
Fees are calculated using factors that include expected profit, and some markets may also charge makers. Unfilled orders can be canceled without a fee, but users still need to review the actual charges shown on the market page before confirming an order.
The review describes Kalshi as relatively clear in how it presents product rules and verification sources. It may appeal to users who value standardized rules, order-book trading and the ability to exit early, though fee formulas, liquidity and regional eligibility still need to be checked market by market.
Robinhood: a familiar interface tied to partner exchanges
Robinhood is presented less as the venue that defines the contract and more as the interface through which users access partner exchanges. The underlying exchange determines pricing, settlement and special rules.
According to the article, Robinhood’s derivatives business offers event contracts through KalshiEX, ForecastEX or Rothera Exchange and Clearing. Common formats include single yes/no contracts, threshold contracts and combined outcomes.
Individual contracts are usually priced between $0.01 and $0.99. A correct outcome settles for $1 in cash, while an incorrect one settles for $0. The order screen shows price and applicable fees before submission.
Unfilled orders can be canceled, but executed orders cannot be reversed. If the market remains open and there is a buyer, users can sell their position at the current market price. If the market is closed or liquidity is missing, the position has to be held until settlement.
The final result is determined by the relevant partner exchange under the official data source and terms written into the contract. Robinhood cannot alter the exchange’s settlement decision.
Fees may include both exchange fees and Robinhood commissions, with the exact amount shown on the order confirmation page.
The review says this setup may fit existing Robinhood users who prefer a unified interface, but it also stresses that traders still need to identify which exchange actually carries the contract because settlement, fees and special-event handling depend on the specific listing.
TurboFlow: an on-chain ecosystem for retail users
TurboFlow is described as an on-chain trading ecosystem for global retail users that combines prediction markets and perpetual contracts. It offers perpetuals, event contracts and prediction markets on the same platform. The article’s review focuses specifically on its event contract product.
That product takes the form of fixed-window “higher/lower” contracts. Users choose the market, stake amount, cycle and direction. The article says the minimum stake is $2 and the fastest round can finish in 30 seconds, while actual parameters depend on the product page.
Pricing and participation are handled through TurboFlow’s propAMM model. Before confirmation, the interface shows entry price, stake amount, cycle, direction, return rate and projected result. Once the order is confirmed, the return rate for that contract is locked.
For settlement, the entry price is the price when the order is accepted and the settlement price is the price used at expiry. If a trader chooses “higher,” the settlement price must be above the entry price for the direction to be correct. For “lower,” the opposite applies. If the two prices are equal, principal is returned under the official rules.
Position management is notably different from a perpetual contract. Once the countdown ends, the product settles automatically. During the holding period, users do not need to manage margin, funding rates or forced liquidation.
The review says TurboFlow lowers the threshold for participation through a $2 minimum and a 30-second shortest cycle, while integrating prediction-market products and perpetual contracts on the same platform. It also warns that short-duration higher/lower contracts are more sensitive to entry timing, market volatility and the pricing data used.
Where the four models differ most
The side-by-side comparison identifies several structural differences.
- Price formation: Polymarket and Kalshi rely mainly on order books. Robinhood displays market quotes from partner exchanges. TurboFlow’s event contracts use propAMM pricing and show entry price, amount, cycle, direction and locked return before confirmation.
- Time horizon: Polymarket, Kalshi and Robinhood contracts are generally tied to an event deadline. TurboFlow uses a fixed time window and can complete a round in as little as 30 seconds.
- Early exit: The first three models generally allow users to sell positions if the market is open and liquidity is available. TurboFlow’s public process is built more around holding until the countdown ends and then settling automatically.
- Settlement authority: Polymarket uses UMA. Kalshi confirms outcomes under its own market terms and stated sources. Robinhood defers to its partner exchanges. TurboFlow’s event contracts settle automatically under pre-disclosed rules using trusted market data sources and entry and settlement prices generated by multiple oracles.
- Use case: Traders focused on continuously changing event probabilities may look first at Polymarket. Those who prefer standardized market rules may lean toward Kalshi. Users who want a single Robinhood interface need to inspect the partner exchange contract underneath. Traders looking for lower-entry, short-cycle higher/lower exposure may study TurboFlow’s event contracts.
Main risks identified in the review
The article lists several risk categories that apply across these products. There is principal-loss risk, since a wrong directional call can send a contract to zero and fixed-return products can also lose the stake amount. There is rule risk, where overlooking boundary conditions, time zones, data sources or exceptional clauses can create a false expectation about settlement.
Liquidity and spread risk also matter, because the displayed market probability, the actual executable price and the price available for an early exit may differ sharply. Settlement and data risk can arise if official data is delayed, corrected, disputed by an oracle process or disrupted at the source, which may lengthen settlement and trigger special rules. Fees remain a separate drag on returns, whether they come from trading charges, commissions, on-chain network costs or deposit and withdrawal expenses. The review also flags technical and compliance risks tied to account security, smart contracts, platform operations and regional restrictions.
The article’s core takeaway
The review reduces event-contract analysis to five checks: question definition, price formation, trade exit, outcome confirmation and fund settlement. Polymarket, Kalshi, Robinhood and TurboFlow each take a different route through that chain, and in TurboFlow’s case the product under review is only its event-contract segment inside a broader ecosystem that also includes perpetuals and prediction markets.
The final point is straightforward. A platform name does not replace contract-level due diligence. What ultimately determines the result is the wording written into the contract: the time used, the data source, the boundary condition and the rule set for abnormal events.