Will MicroStrategy be margin called in 2026? [ resolves 2027-01-01 (179D) ]
Will MicroStrategy be margin called in 2026?
polymarket: [C] multiple sources, no tie-break·reporting consensus methodology ›
markets · by resolution date · marks: daily snapshot
polymarket 1 market
| market | resolves | P(YES) | vol (24h) | vol (cum) | RCG | venue id | ||
|---|---|---|---|---|---|---|---|---|
| Will MicroStrategy be margin called in 2026 | 2027-01-01 | 8.0% | $38 | $76K | C | 0x48f7e0…3c20 |
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 MicroStrategy incorporated is margin called on any of its Bitcoin-backed loans by December 31, 2026, 11:59 PM ET, resulting in either a forced liquidation of Bitcoin by a lender or MicroStrategy posting additional collateral or making a loan repayment in response to the margin call. Otherwise, this market will resolve to "No."
A margin call is defined as a lender formally requiring MicroStrategy to either provide additional collateral or repay part of a loan due to the value of Bitcoin collateral falling below the required loan-to-value (LTV) ratio. Voluntary Bitcoin sales by MicroStrategy that are not explicitly in response to a margin call will not count.
The primary resolution sources will be SEC filings, official MicroStrategy statements, and a consensus of credible financial reporting.
platform source field
polymarket.resolutionSource → ∅ no committed source — see rules text above sources (3)
- SEC filings from rules text · editorial
- official MicroStrategy statements from rules text · editorial
- a consensus of credible financial reporting from rules text · editorial
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-microstrategy-be-margin-called-in-2026/ |
| JSON | REST API for developers | https://api.clearmarket.fyi/v1/events/will-microstrategy-be-margin-called-in-2026 |
| MCP | agentic AI tool call (Claude Desktop, Cursor, Continue) | clearmarket.get_event("will-microstrategy-be-margin-called-in-2026") |
| 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-27GSKRDLZ7",
"slug": "will-microstrategy-be-margin-called-in-2026",
"question": "Will MicroStrategy be margin called in 2026?",
"category": "crypto",
"tags": [
"business",
"crypto",
"microstrategy",
"margin-call",
"bitcoin-holdings",
"2027"
],
"venues_covered": [
"polymarket"
],
"market_count": 1,
"cumulative_volume_usd": 75505,
"resolution_clarity_grade": "C",
"rcg_score": 37,
"rcg_caps": [
"multi_source_no_conflict_rule",
"commitment_uncommitted_placeholder"
],
"resolution_source": null,
"resolution_source_url": null,
"source_status": "no_committed_source",
"source_of_record": null,
"resolution_source_list": [
{
"name": "SEC filings",
"url": null,
"provenance": "clearmarket_editorial"
},
{
"name": "official MicroStrategy statements",
"url": null,
"provenance": "clearmarket_editorial"
},
{
"name": "a consensus of credible financial 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"
}
}
}