Market detail
0x37995211…cb7ffb untitled
DisputedEscalated → DVMResolved
No Polymarket slug indexed
Risk factor breakdown
transparent weighted sum → 62/100Dispute & reset timeline
7 on-chain eventsunverified — derived from on-chain event timestamps; lifecycle ordering not independently audited.
- ●InitializedFeb 24, 2026, 15:49
- ✕Disputed (round 1)Mar 9, 2026, 06:43
- ↺Reset (round 1)Mar 9, 2026, 06:43
- ↗Escalated to mainnet DVM (round 1)Mar 9, 2026, 06:43escalated to mainnet DVM ↗
- ◆Proposed (round 1)Mar 11, 2026, 01:12
- ✓ResolvedMar 11, 2026, 04:59
- ✓Settled (round 1)Mar 12, 2026, 00:31
Resolution status
State
Resolved
Reset rounds
1
Pause count
0
Resolution lag
14d 13h
On-chain provenance
auditablequestionId
Polymarket slugnone
Adapter address
Risk score62/100 · Elevated
Off-chain clarificationsunavailable
Resolution criteria
ancillaryText · rendered from on-chain ancillaryDataq: title: Will team A win the 2026 CAA conference championship?, description: This market will resolve according to the team that is officially determined as the winner of the 2026 CAA conference championship.
If at any point it becomes impossible for a listed participant to win the 2026 CAA conference championship per the rules of the CAA (e.g., participant is eliminated), the corresponding market will resolve to "No".
If multiple teams are declared winners, this market will resolve in favor of the team whose listed name comes first alphabetically.
If this event is cancelled, postponed after March 31, 2026, 11:59 PM ET, or a conference champion has not been declared within this timeframe, this market will resolve to "Other".
The resolution source will be official information from the National Collegiate Athletic Association (https://www.ncaa.com/sports/basketball-men/d1); however a consensus of credible reporting may also be used. market_id: 1426797 res_data: p1: 0, p2: 1, p3: 0.5. Where p1 corresponds to No, p2 to Yes, p3 to unknown. This request MUST only resolve to p1 or p2. Updates made by the question creator via the bulletin board at 0x69c47De9D4D3Dad79590d61b9e05918E03775f24 should be considered.,initializer:91430cad2d3975766499717fa0d66a78d814e5c5