Launch markets without building the operations stack
Outcome can focus on distribution, liquidity, and the trading experience while Risk Labs handles the resolution lifecycle.
Outcome Finance · July 2026
Prediction markets infrastructure
From market rules
to user payouts.
Outcome owns the market and trading experience. Risk Labs handles rule validation, proposal review, and trusted resolution delivery.
Explore the integration250k+markets per month
99.6%automatically resolved
2M+markets resolved to date
Production infrastructure behind the resolution workflows used by Polymarket and Predict.fun.
01 / Why Risk Labs
The infrastructure layer behind the market.
Outcome gets a production-tested path from market definition to final payout—without assembling a separate market operations and resolution organization.
Improve rules before users trade
Risk Labs checks formatting, resolution values, sources, dates, ambiguity, and market collisions before creation.
Move from event end to settlement automatically
Lifecycle monitoring, proposal intake, review, and signed results arrive through one integration.
Keep control of the market
Outcome remains in control of its contracts, trading state, multisig, user experience, and payouts.
02 / Integration lifecycle
One flow. Two clear owners.
Every step has one responsible system. The lifecycle moves left to right from market creation to payout.
Outcome / HyperEVM
Risk Labs / Resolution
Submit rules
Send the question, sources, dates, resolution values, and metadata.
Validate + create
Rule checks, suggested improvements, canonical question ID.
Trade
Bind the question ID to the HyperEVM market and open trading.
Signal resolution ready
A webhook tells Outcome the market can now be resolved.
Pause trading
New orders and matching stop before the resolution is published.
Proposer network
Submit the proposed resolution and start the review lifecycle.
AI review proposal
AI agents test the proposed answer against the market rules and evidence, escalating ambiguity for extra review.
Disputed?
Was the reviewed proposal challenged?
Arbitrate dispute
The Outcome multisig records its decision on HyperEVM.
Sign final result
Read the final state and produce the signed settlement result.
Settle + pay users
Verify the signature, settle on HyperEVM, and pay users.
No disputeDirect settlement
When the review window closes without a challenge, Risk Labs signs the reviewed result and sends the settled event to Outcome for verification and payout.
DisputedArbitrated settlement
If challenged, Outcome's multisig records the decision on HyperEVM. Risk Labs reads that onchain result, signs it, and returns it to the same settlement path.
03 / Integration surfaces
Pull when you need it. Push when it changes.
Outcome gets a simple API for creation and reconciliation, plus signed webhooks for every lifecycle transition.
REST APIOutcome → Risk Labs
POST /create/validateCheck rule format, resolution values, dates, sources, edge cases, and collisions. Return required changes and suggestions.
POST /create/submitCreate the canonical Risk Labs market from an approved validation attempt. Liveness and oracle reward are configurable.
GET /market/{identifier}Read or reconcile the latest metadata, lifecycle state, review status, and signed resolution.
WEBHOOKSRisk Labs → Outcome
resolution_readyPause trading before a resolution is published
proposedA proposed resolution was received; review has started
extended_reviewMore review time is required
disputedRoute the market into multisig arbitration
settledDeliver the final result and settlement signature
Every delivery includes
A unique event ID, current market state, and a request signature. Outcome verifies, deduplicates, durably records, and returns a fast 2xx. Failed deliveries are retried.
04 / Operating model
Clear boundaries. Shared success.
Outcome keeps control of the product and chain. Risk Labs runs the specialized resolution infrastructure behind it.
Outcome ownsProduct + chain
- Market selection and commercial strategy
- Trading, order matching, and liquidity
- HyperEVM market and payout contracts
- Multisig arbitration for disputed markets
Risk Labs ownsResolution infrastructure
- Market-rule validation and improvements
- Canonical market identity and lifecycle state
- Proposer-network integration
- Review, escalation, and signed final results
05 / Explore the system
See the infrastructure in production.
Follow live oracle requests in the Explorer or review the Risk Labs integration contracts and examples.
Oracle ExplorerBrowse requests, proposals, disputes, and settlements.oracle.uma.xyz ↗Risk Labs DocumentationReview the market API, webhooks, and request examples.docs.3po.dev ↗
Accessing the docsOpen docs.3po.dev and enter the shared partner password provided by Risk Labs. If you do not have it, ask the Risk Labs team for access.
06 / Disputed resolution
A narrow path, designed together.
The leading design is for the Outcome multisig to record an arbitration decision on HyperEVM. Risk Labs reads and verifies that onchain state, then continues the normal signed settlement flow.
01Proposal disputed
→02Outcome multisig arbitrates
→03Decision recorded on HyperEVM
→04Risk Labs reads, signs, and settles
Open design workArbitration contract · finality requirement · event format · Risk Labs authentication and read path
07 / Path to launch
Three steps to production.
Start with one market, prove the complete lifecycle, then scale the same integration across Outcome's market catalog.
Configure
Provision Outcome's API key, webhook destination, signer allowlist, and market-creation policy.
Prove one market
Validate, create, trade, resolve, and settle one market through the complete lifecycle.
Launch
Finalize the HyperEVM dispute bridge, then scale the same integration across Outcome's catalog.
The core integration already exists.
The primary co-design work is the disputed-market bridge between Outcome's HyperEVM multisig and Risk Labs.