Will Curvance launch a token by 2026? [ resolves 2026-07 – 2028-01 ]
Will Curvance launch a token by September 30, 2026?
polymarket: [C] multiple sources, no tie-break·reporting consensus methodology ›
distribution · by resolution date · marks: daily snapshot
polymarket 7 markets
| market | resolves | P(YES) | vol (24h) | vol (cum) | RCG | venue id | ||
|---|---|---|---|---|---|---|---|---|
| June 30, 2026 | 2026-07-01 | 0.5% | — | $13K | C | 0xf88c97…bddc | ||
| September 30, 2026 | 2026-10-01 | — | — | — | C | 0x0ea317…b0e9 | ||
| December 31, 2026 | 2027-01-01 | 17.0% | — | $11K | C | 0xe17ec4…7fc7 | ||
| March 31, 2027 | 2027-04-01 | — | — | — | C | 0xd32f72…192e | ||
| June 30, 2027 | 2027-07-01 | 65.0% | — | $13K | C | 0xebcf67…637a | ||
| September 30, 2027 | 2027-10-01 | — | — | — | C | 0x41ac47…fb92 | ||
| December 31, 2027 | 2028-01-01 | — | — | — | C | 0x4b527f…f952 |
resolution architecture
| venue | proposer | source | citation | arbitration | class | analyst notes |
|---|---|---|---|---|---|---|
| polymarket | Whitelisted Proposers | uncommitted | link | Optimistic Oracle (UMA) | Other | — |
verbatim rules
polymarket
This market will resolve to "Yes" if Curvance officially launches a token by 11:59 PM ET on the date specified in the title. Otherwise, this market will resolve to "No".
Only an official token launched by Curvance will qualify. Stablecoins, memecoins, LSTs and synthetic tokens will not count.
The token must be actively and publicly tradable. Announcements alone do not qualify.
The primary resolution source for this market will be information from Curvance (https://x.com/curvance), however a consensus of credible reporting will also be used.
platform source field
polymarket.description → https://x.com/curvance sources (3)
x.com venue-listed information from Curvance (https://x.com/curvance) from rules text a consensus of credible reporting from rules text
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/will-curvance-launch-a-token-by/ |
| JSON | REST API for developers | https://api.clearmarket.fyi/v1/events/will-curvance-launch-a-token-by |
| MCP | agentic AI tool call (Claude Desktop, Cursor, Continue) | clearmarket.get_event("will-curvance-launch-a-token-by") |
| AGENT | AI crawler discovery index | /llms.txt |
Snapshot 2026-08-04. 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-FH81JD30Q0",
"slug": "will-curvance-launch-a-token-by",
"question": "Will Curvance launch a token by 2026?",
"category": "crypto",
"tags": [
"crypto",
"token-launch",
"curvance",
"defi",
"2026"
],
"venues_covered": [
"polymarket"
],
"market_count": 7,
"cumulative_volume_usd": 37553,
"resolution_clarity_grade": "C",
"rcg_score": 37,
"rcg_caps": [
"multi_source_no_conflict_rule",
"commitment_uncommitted_placeholder"
],
"resolution_source": null,
"resolution_source_url": "https://x.com/curvance",
"source_status": "no_committed_source",
"source_of_record": null,
"resolution_source_list": [
{
"name": "x.com",
"url": "https://x.com/curvance",
"provenance": "platform_api"
},
{
"name": "information from Curvance (https://x.com/curvance)",
"url": null,
"provenance": "clearmarket_editorial"
},
{
"name": "a consensus of credible reporting",
"url": null,
"provenance": "clearmarket_editorial"
}
],
"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"
}
}
}