Contracts
All Props Oracle contracts live on Polygon mainnet. The oracle uses USDC.e as its bond token for UMA assertions, which is the same token Polymarket and most Polygon-deployed UMA products use.
| Contract | Address | Purpose |
|---|---|---|
| EventRegistry | 0x… (published at launch) | Maps canonical event IDs to single-slot assertion streams such as player stats, lines published, game outcomes, and voids. Bucketed MARKET_RESOLUTIONS claims do not write here. |
| UMA Optimistic Oracle V3 | 0x… (UMA deployment) | Stores assertion state and emits the AssertionMade log containing the market-resolution payload. Consumers read logs, not storage, for the payload itself. |
| USDC.e (bond token) | 0x2791bca1f2de4661ed88a30c99a7a9449aa84174 | Bond token for all Props Oracle assertions. Consumers do not interact with this directly. |
The EventRegistry ABI is published in the repository and is intentionally minimal. For registry-backed streams, the main method is events(bytes32 canonicalEventId), which returns the RegisteredEvent struct containing assertion IDs and finalization flags. For MARKET_RESOLUTIONS, consumers should use UMA OOV3 assertion IDs discovered from logs or an indexer.
The UMA OOV3 address listed above is UMA's own canonical deployment on Polygon, not a Props Oracle contract. Consumers that want to subscribe to AssertionMade events or verify assertion state independently should use that address directly per UMA's own documentation.