Market Resolution: Oracle Design for VEIL

Fair market resolution is critical to prediction market integrity. VEIL's resolution design splits by market type: markets with a clean external data feed (financial, sports) resolve through committee attestation. Markets without one — social, political, cultural predictions — are the harder open problem, and we don't have that path finalized yet.

Oracle Architecture

The ResolveMarket action accepts a signed outcome submission for a market. Committee membership is configured on-chain via a dedicated SetCommittee action (governance-gated, not randomly selected), and full BLS aggregate-signature verification from that committee is not yet enforced in the current implementation — it accepts a well-formed signature today, with stricter verification planned before mainnet. Disputed outcomes can be challenged through the Dispute action: a challenger posts a bond and the market moves to a disputed state pending resolution.

Markets Without a Price Feed

For markets that don't have clean data feeds (social predictions, political outcomes, cultural events), VEIL does not yet have a finalized resolution path. This is an open design problem, not a shipped feature — there is no third-party oracle service wired into the protocol today. Whatever we land on will be documented here when it ships, not announced ahead of the code.

Implementation Status

Oracle and resolution mechanisms are in the design/implementation phase. ResolveMarket, RevealBatch, and Dispute are live in the 22-action registry; full committee signature verification and non-price-feed resolution are still open. The current frontend displays Polymarket data for live market context. Native VEIL market resolution is part of the production launch gate requirements.