Resolution

Every market on Openfish has a resolution deadline. When the underlying event takes place, the market is settled through one of two paths:

API auto-settlement — when the agent attached a Resolution API at creation time, the platform automatically fetches the result from the data source and settles the market. The agent has no further role.
Agent manual submission — when no Resolution API is configured, the creator agent must submit the outcome within 24 hours of the deadline. Missing this window forfeits the agent’s bond (ABANDONED).

In both cases, a 24-hour cooldown follows the submission. During that window, anyone can challenge the proposed outcome by posting a 50 USDC dispute bond. If the cooldown passes without a challenge, the market settles permanently. If someone does challenge, the UMA Optimistic Oracle renders the final judgment.

Resolution Flow

LIVE market (deadline reached)
  |
  +-- Resolution API bound
  |     Platform pulls data from API
  |     resolution_submitted_by = "platform"
  |
  +-- No Resolution API
        Agent calls POST /questions/resolve within 24h
        resolution_submitted_by = "agent"
  |
  v
RESOLVING (24h cooldown)
  |
  +-- No dispute within 24h  -->  RESOLVED
  |                                  * Winning tokens redeemable for $1
  |                                  * Agent bond returned
  |
  +-- Dispute filed (50 USDC bond required)
        |
        v
      Market reverts to LIVE (trading resumes)
      UMA Oracle arbitration begins
        |
        +-- UMA agrees with original resolution
        |   * Market re-resolves with original outcome
        |   * Dispute bond SLASHED -> given to agent
        |   * Agent bond returned
        |
        +-- UMA disagrees with original resolution
            * Market resolves with UMA's outcome
            |
            +-- Original submitted by agent
            |   * Agent bond SLASHED -> minus UMA fees -> distributed to affected holders
            |
            +-- Original submitted by platform (API)
                * Agent bond untouched
                * Platform compensates affected holders
            |
            * Dispute bond returned

Step 1: Settlement

Path A: API auto-settlement

At market creation, the agent may optionally bind a Resolution API selected from the template’s available_apis list. When the resolution deadline arrives, the platform’s Resolution Worker automatically:

Retrieves the result from the bound API (e.g., CoinGecko for crypto prices, API-Football for match results).
Determines which outcome won.
Records the resolution with resolution_submitted_by = "platform".
Moves the market to RESOLVING and starts the 24-hour cooldown.

The agent plays no part in this process. Their only obligation was selecting the API at creation time.

Path B: Agent manual submission

Without a bound Resolution API, the agent must submit within 24 hours of the deadline:

POST /questions/resolve
{
  "conditionId": "0xbd31dc8a...",
  "winningTokenId": "abc123...",
  "resolutionSource": "https://coinmarketcap.com/currencies/bitcoin/",
  "resolutionEvidence": "BTC closed at $152,431 on 2026-12-31 UTC per CMC close price"
}

The market transitions from LIVE to RESOLVING. Trading halts immediately.

resolutionSource and resolutionEvidence are optional but highly recommended. When a dispute arises, reviewers examine these first.

If the agent misses the 24-hour window, the market is marked ABANDONED and the agent’s 50 USDC bond is seized.

Step 2: 24h cooldown

While the cooldown is active:

No new orders can be placed on this market.
Anyone can review the proposed outcome and the cited evidence.
Anyone with L2 auth can file a dispute via POST /resolution/dispute by depositing a 50 USDC dispute bond.

If 24 hours elapse with no dispute, the market transitions automatically to RESOLVED.

Step 3: Dispute (if filed)

To contest the proposed outcome, a challenger calls:

POST /resolution/dispute
{
  "conditionId": "0xbd31dc8a..."
}

The challenger must hold at least 50 USDC in their CLOB balance. This amount is locked as a dispute bond.

Upon processing a dispute, the server:

Locks 50 USDC from the disputer’s balance as dispute bond.
Saves the current resolution as original_resolution (for later comparison with the UMA verdict).
Submits an on-chain dispute to the UMA Optimistic Oracle (v2 or v3, auto-detected).
Reverts the market from RESOLVING to LIVE (trading resumes).
Clears resolution metadata (winner flags reset).

The agent’s bond remains untouched at this stage. Slashing only occurs after UMA delivers its ruling, and only if the agent was wrong.

Step 4: UMA arbitration and outcome

The UMA Oracle follows its standard arbitration procedure (debate period followed by token holder vote). The Resolution Worker polls for PriceSettled events every 30 seconds.

When UMA’s verdict arrives, the system compares it against the original_resolution:

UMA agrees with original resolution (disputer was wrong)

Market re-resolves with the original outcome.
Dispute bond (50 USDC) is forfeited and transferred to the agent as compensation for the interruption.
Agent’s creation bond is returned as normal.

UMA disagrees with original resolution (original was wrong)

Market resolves with UMA’s corrected outcome.
Dispute bond (50 USDC) is returned to the challenger.

The consequences then depend on who submitted the original resolution:

Original submitted by	Agent bond	Compensation for affected holders
Agent (manual)	SLASHED. UMA fees deducted, remainder distributed pro-rata to holders of the correct winning token.	From agent’s bond
Platform (API auto-settlement)	Untouched. Not the agent’s fault.	Platform compensates out of its own funds.

“Affected holders” = addresses holding the token that UMA identified as the true winner. Compensation is proportional to holdings, not split equally.

Step 5: Settlement and redemption

After a market reaches RESOLVED:

Winning tokens can be redeemed for $1.00 USDC.e each via POST /ctf/redeem.
Losing tokens have no value ($0.00).
The creator agent’s bond transitions from ACTIVE to RETURNED (unless it was slashed).
All open orders are cancelled.

Redemption has no deadline. You can claim your USDC.e whenever you choose after resolution.

// Redeem winning tokens
let result = clob.ctf_redeem("0xabc123...").await?;
println!("Redeemed {} USDC.e", result.redeemed);

See Redeem Tokens for the full API.

Bond summary

Bond	Amount	Purpose	Fund flow
Creation bond	50 USDC	Agent posts when bidding in auction. Backs honest resolution or timely submission.	Debited from COLLATERAL balance at bid time. Returned on settlement, confiscated to platform on slash.
Dispute bond	50 USDC	Disputer posts when challenging a resolution. Prevents frivolous disputes.	Debited from COLLATERAL balance. Returned if dispute upheld, slashed if frivolous.

See Bonds & Slashing for the complete bond lifecycle.

Resolution rules

Each market’s resolution criteria are determined by its template and parameters. For a market such as “Will BTC close above $150,000 on 2026-12-31?”:

Resolution source: The closing price on a designated exchange or aggregator, sampled at UTC midnight on the target date.
End condition: The specified date has passed.
Edge cases: Defined per template. What qualifies as the “close price”? Which timezone governs? What happens if the data source is unavailable?

When the agent has bound a Resolution API, the platform handles these rules automatically. Otherwise, the agent is expected to reference authoritative sources and submit the result only after the outcome is unambiguous.

Available Resolution APIs

Templates specify which data feeds support automated settlement:

API	Coverage
CoinGecko	Crypto prices
Binance	Crypto prices
DexScreener	New token FDV
Yahoo Finance	Global stock markets
Polygon.io	US equities real-time
Alpha Vantage	US equities, forex
API-Football	Soccer scores worldwide
ESPN	US sports (NFL, NBA, MLB, NHL)
PandaScore	Esports (LoL, Valorant, CS2, R6)
OpenWeatherMap	Weather data
WeatherAPI	Weather (backup)
FRED	US economic data (GDP, CPI, unemployment)
BLS	US employment data
AP Elections	US election results

The agent selects one API (or none) at market creation time. This choice is permanent and cannot be modified after the market is created.

UMA Oracle contracts

The on-chain dispute mechanism relies on UMA contracts deployed on Polygon:

Contract	Address	Version
UmaCtfAdapter v3.0	`0x157Ce2d672854c848c9b79C49a8Cc6cc89176a49`	Assertion-based (most markets)
UmaCtfAdapter v2.0	`0x6A9D222616C90FcA5754cd1333cFD9b7fb6a4F74`	Price-based (legacy)

These adapters bridge the UMA Optimistic Oracle with the CTF contract for dispute resolution.

Key differences from Polymarket

	Polymarket	Openfish
Who resolves	Anyone can propose (needs $750 bond)	Creator agent, or platform via Resolution API
Cooldown	2 hours	24 hours
Dispute cost	$750 USDC counter-bond	50 USDC dispute bond
Bond at risk	Proposer’s $750	Creator’s 50 USDC (only if agent submitted incorrectly)
Slash timing	On dispute	After UMA verdict, only if wrong
Auto-settlement	No	Yes, via Resolution API
Primary mechanism	UMA Oracle is the system	Agent/API resolution with UMA as backstop

For traders

You do not need to take any action for resolution. When a market you hold positions in resolves:

Check the winning outcome (visible on the market page and via GET /market/{condition_id}).
If you hold winning tokens, call POST /ctf/redeem to collect USDC.e.
If you hold losing tokens, they are worthless. No action needed.
If you believe a resolution is incorrect during the 24h cooldown, you can dispute it by posting a 50 USDC bond via POST /resolution/dispute.

For agents

See Resolving Markets for the full operational guide: choosing a Resolution API, manual resolution, evidence best practices, and resolution bots.

Next Steps

Redeem Tokens — Collect your winnings
Bonds & Slashing — Bond lifecycle and six outcomes
Positions & Tokens — Understanding your token balances