UMA API AND WEBSOCKET
Resolution data,
without the indexer.
Query and stream proposals, challenge windows, disputes, settlement, and final outcomes for Polymarket markets through one Bravado schema.

Proposed outcome
YES
Status
Proposed
Challenge window
1h 42m
Disputed
No
Resolution source
UMA
Challenge window
Resolution is a lifecycle,
not a boolean.
A market moves through proposal, challenge, dispute, settlement, and redemption. Bravado exposes each state.

Query the state.
Don’t decode the chain.
Bravado indexes the resolution lifecycle and returns the state your application actually needs.
Without Bravado
UMA contracts
RPC
Event logs
ABI decoding
Request correlation
Proposal state
Challenge timers
Disputes
Settlement
Your database
build the indexer

With Bravado
{
market, status,
proposal,
challenge_window,
dispute, settlement
}
Your app asks a question. Bravado handles the chain state.
HTTP to query.
WebSocket to watch.
Pull the complete resolution state when you need it, then subscribe to changes as the oracle lifecycle moves forward.
HTTP
GET /resolution
bravado.get_trader_pnl
await response…
Resolution
Resolving
resolution.settled
Outcome
YES
status
SETTLED
Remaining
- - -
WebSocket
resolution.settled
resolution.settled
Every resolution event, in order.
The complete lifecycle for auditing, analytics, and UI timelines.

Resolution timeline
LIVE
18:00:00
Requested
resolution request created
18:04:12
Proposed
outcome YES · bond posted
18:04:13
Challenge opened
window running
00:00:00
Disputed
escalated to DVM
00:00:00
DVM vote
tokenholders resolve
00:00:00
Settled
outcome YES
RESOLUTION LAYER
Resolution, from
proposal to payout.
Track every resolution event, dispute, and settlement across the full prediction-market lifecycle.
Challenge windows
Know when the answer can still change.

Resolution proposal
bond
$5,000
Disputes
See the entire escalation, not just the outcome.

Pre Confirmation
Can be surfaced from the mempool before on-chain confirmation.

Mempool
proposal tx 0x84…991
Bravado
PRE-CONFIRMED
Chain
CONFIRMED
Market Mapping
Ask about the market, not the oracle request.

UMA settlement
0x84…F91
Market · outcome
YES
BUILT FOR PRODUCTION
Resolution data you
can actually build on.
Full lifecycle exposed
Every stage queryable, not just the final outcome.
Pre-confirmed events
Pending proposals and disputes surfaced from the mempool before on-chain confirmation.
Market-correlated
Resolution records mapped to the market IDs you already use no separate oracle-request lookup layer.
State, not determination
Bravado exposes the resolution state. It never determines the outcome that stays with UMA's DVM.
