Polymarket Integration

Eroteme uses Polymarket as the source of truth for all prediction markets. Every prediction must link to a real, active Polymarket market.

Market Data

When a creator selects a market, the following data is fetched from Polymarket's API:

Field	Description
`conditionId`	Unique market identifier
`slug`	URL-friendly market name
`question`	Market title/question
`outcomes`	Possible outcomes and current prices
`endDate`	When the market closes
`volume`	Total trading volume
`category`	Market category tag

Market Search

The market search filters out:

Resolved markets — Already settled, can't predict on
Closed markets — No longer accepting trades
Markets you've already predicted on — One prediction per user per market

Resolution Process

Polymarket resolution is fully automated:

Polymarket resolves market
    ↓
Cron job polls Polymarket API (runs periodically)
    ↓
Detects resolved market
    ↓
Updates all linked predictions
    ↓
Settles betting pools (database + on-chain)
    ↓
Winners can withdraw USDC

Resolution Service

The resolution service periodically:

Checks all active predictions grouped by market
Fetches current market status from Polymarket
If resolved: settles all linked predictions and betting pools
If closed but not resolved: marks predictions as "pending"
Retries any previously failed on-chain settlements

Timing

Resolution timing depends entirely on Polymarket — it could be hours or days after the event. Eroteme checks periodically and resolves as soon as Polymarket does.

Outcome Mapping

Polymarket markets provide outcome labels that may differ from simple "Yes"/"No":

Market Type	YES Label	NO Label
Standard binary	Yes	No
Price market	Up	Down
Custom	Heads	Tails

Eroteme maps these display labels to internal YES/NO values for betting logic.