Will ConsenSys have a market cap above $1B–$3B at IPO closing? [ resolves 2027-01-01 (179D) ]
Consensys IPO closing market cap above $2B?
polymarket: [B] multiple sources, tie-break·objective outcome methodology ›
markets · by resolution date · marks: daily snapshot
resolution architecture
| venue | proposer | source | citation | arbitration | class | analyst notes |
|---|---|---|---|---|---|---|
| polymarket | Whitelisted Proposers | uncommitted | not provided | Optimistic Oracle (UMA) | Other | — |
verbatim rules
polymarket
This market will resolve to “Yes” if the official closing price for Consensys’ market capitalization on its first trading day is above the value specified in the title. Otherwise, it will resolve to “No”.
If no IPO occurs by December 31, 2026, 11:59 PM ET, this market will resolve to “No”.
Market capitalization is defined as the total number of outstanding shares multiplied by the closing share price on the first trading day.
Resolution will be based on the primary exchange’s official listing page. In the event that the relevant figure is not displayed, another reliable source will be used.
In the event of an interruption in the course of the normal trading session on Consensys’s first day of trading (e.g., a circuit breaker or half-day), the market will resolve according to the official closing price of the abbreviated session. If no such official closing price is published, the market will resolve according to the next trading day on which an official closing price is published, treating that as the first day of trading.
platform source field
polymarket.resolutionSource → ∅ no committed source — see rules text above recent wire items
monitoring status: active no active wire
No CM Signal wire has been published for this event yet.
CM Signal’s news-cycle scan surfaces the day’s top stories alongside the prediction markets pricing them. When a story references this event, its wire is published here and links back to this page.
programmatic access · four surfaces, same payload
One canonical record at every surface — embedded JSON-LD, REST, MCP, and /llms.txt.
| HTML | browsers, AI grounded search, crawlers (embedded JSON-LD @type: Dataset) | https://clearmarket.fyi/events/consensys-ipo-closing-market-cap-above/ |
| JSON | REST API for developers | https://api.clearmarket.fyi/v1/events/consensys-ipo-closing-market-cap-above |
| MCP | agentic AI tool call (Claude Desktop, Cursor, Continue) | clearmarket.get_event("consensys-ipo-closing-market-cap-above") |
| AGENT | AI crawler discovery index | /llms.txt |
Snapshot 2026-07-06. Venue data via Kalshi + Polymarket APIs. Editorial fields (tags, editorial_notes) are ClearMarket-drafted with AI assistance under editorial review. Derived fields (venues_covered, resolution_clarity_grade, rcg_score) computed at serve time. Full per-field map in the JSON record under field_provenance.
raw JSON record · same payload returned by REST endpoint {
"event_id": "CM-EVT-B9JZW4XFG1",
"slug": "consensys-ipo-closing-market-cap-above",
"question": "Will ConsenSys have a market cap above ___ at IPO closing?",
"category": "crypto",
"tags": [
"crypto",
"ipo",
"consensys",
"market-cap",
"2027",
"web3-infrastructure"
],
"venues_covered": [
"polymarket"
],
"market_count": 3,
"cumulative_volume_usd": 321888,
"resolution_clarity_grade": "B",
"rcg_score": 76,
"rcg_caps": [
"uncommitted_illustrative"
],
"resolution_source": null,
"resolution_source_url": null,
"source_status": "no_committed_source",
"source_of_record": null,
"resolution_source_list": null,
"arbitration_model": "uma_oracle",
"proposer_model": "managed_whitelist",
"field_provenance": {
"question": {
"source": "clearmarket_editorial"
},
"tags": {
"source": "clearmarket_editorial",
"ai_drafted": true
},
"resolution_clarity_grade": {
"source": "derived",
"method": "rcg_v2_7factor"
},
"venues_covered": {
"source": "derived"
}
}
}