MicroStrategy announces >1000 BTC purchase May 26-June 1?
Probability
56¢
1h
+20.0pp
24h
-1.5pp
24h Vol
$1.3K
Liquidity
$668.58
Canonical status
confidence: mediumSource status (Polymarket)
Derived status (Orrery)
Reason
Liquidity is below $1,000 — price discovery is unreliable.
The derived status is computed from the source flags plus the live YES price, so a market trading near a rail can read as PRICE-PINNED while upstream is still active. That isn't the same as resolved.
Resolution & Risk
HIGH risk- End date
- Jun 2, 2026
- UMA status
- n/a
- Resolution source
- Primaryannouncements made within the market's designated time frame regardless of when the actual purchases were madeLinkTypeAmbiguous wording
- Market type
- Binary
- Market expires Jun 2, 2026 — dispute window active.
- Wide spread (15.0¢) — liquidity risk on entry/exit.
Probability (last 7 days)
+0.0pp 7dWhy did it move?
Structured · 3 factors- 01Price move
Down 2pp over 24h
Now 56¢; +20.0pp in the last hour.
- 02Active signal
Resolution-risk observation firing
Expires in 68h. Spread is extremely wide.
- 03Spread cost
Wide spread — 15.0¢
Bid-ask spread is wide enough that intraday moves overstate any tradeable advantage. Most of the headline pp move would be eaten by spread on a market order.
What to track next
- Verify the resolution source on this page — exchange feed, official release, news consensus — before treating any move as new information.
- Set an alert for resolution status changes — expiry is in 68 hours.
Verification actions only — never trade recommendations.
Each factor is grounded in a single named metric you can verify on this page — probability, volume, liquidity, signal, resolution state. No predictions, no prose hallucinations.
Resolution & Risk
HIGH risk- End date
- Jun 2, 2026
- UMA status
- n/a
- Resolution source
- Primaryannouncements made within the market's designated time frame regardless of when the actual purchases were madeLinkTypeAmbiguous wording
- Market type
- Binary
- Market expires Jun 2, 2026 — dispute window active.
- Wide spread (15.0¢) — liquidity risk on entry/exit.
Timeline
critical · price · trade flowCritical
- Jun 2, 04:00 UTCScheduled resolutionHIGH
Market resolves in 67.6h
- 08:26SignalMEDIUM
Resolution risk
Expires in 68h. Spread is extremely wide.
Price movement
-1.5pp over the last 24h, now 56¢.
Biggest hourly move: -46.5pp at May 28, 19:00 UTC (to 25¢).
Show top 8 of 33 hourly moves
- May 28, 21:00 UTC · -40.0pp → 31¢
- May 28, 20:00 UTC · -40.0pp → 31¢
- May 28, 19:00 UTC · -46.5pp → 25¢
- May 28, 17:00 UTC · -37.5pp → 34¢
- May 28, 15:00 UTC · -38.0pp → 33¢
- May 28, 14:00 UTC · -37.5pp → 34¢
- May 28, 12:00 UTC · -37.5pp → 34¢
- May 27, 22:00 UTC · -39.5pp → 24¢
Active signals
Recent Trades
No recent trades visible from the Data API for this market. That usually means liquidity is thin or this market is between event windows.
Related Markets
6- 23¢-2.9
MicroStrategy sells any Bitcoin by May 31, 2026?
Crypto · Vol $868.6K
- 0¢-0.2
Will Bitcoin reach $85,000 in May?
Crypto · Vol $448.8K
- 0¢-0.1
Will Bitcoin reach $90,000 in May?
Crypto · Vol $313.0K
- 69¢-2.1
MicroStrategy sells any Bitcoin by June 30, 2026?
Crypto · Vol $290.3K
- 4¢-3.5
Will Bitcoin dip to $70,000 in May?
Crypto · Vol $261.2K
- 39¢-11.0
Will Bitcoin dip to $72,500 in May?
Crypto · Vol $238.6K
Market Description
This market will resolve to "Yes" if MicroStrategy announces a purchase of more Bitcoin than the number specified in the title between the dates in the title (from 12:00 AM ET on the first date to 11:59 PM ET on the last date). Otherwise, this market will resolve to "No". This market will resolve based on announcements made within the market's designated time frame regardless of when the actual purchases were made. The resolution source for this market will be official information from MicroStrategy or Michael Saylor. For reference, MicroStrategy's reported BTC holdings can be tracked at: https://www.strategy.com/purchases
Why this category?
confidence: highCategory
Source
Matched term
btcReason
Question text contains the high-signal keyword "btc" — matched the Crypto rule.
Categories come from a deterministic engine: manual overrides (highest priority) → sports hard markers → event-tag rules → keyword rules → Gamma category hint → default. The engine is versioned in category-overrides.ts; methodology lives at /methodology.
FAQ — questions readers actually ask
What is the current Polymarket probability for "MicroStrategy announces >1000 BTC purchase May 26-June 1?"?
As of Sat, 30 May 2026 08:26:59 GMT, YES is priced at 56% implied probability on Polymarket. The price changed -1.5pp in the last 24 hours, +20.0pp in the last hour, and +0.0pp in the last 7 days.
When does this market resolve?
This market resolves by Jun 2, 2026 (2026-06-02T04:00:00.000Z). Resolution is determined from https://www.strategy.com/purchases.
What source determines the outcome?
Resolution is sourced from https://www.strategy.com/purchases. Polymarket's UMA optimistic oracle is the final settlement layer; if the published source is ambiguous, UMA tokenholders adjudicate. Source-extraction confidence is shown in the Resolution & Risk block above.
How much is being traded on this market?
$1.3K of trading volume in the last 24 hours. Lifetime volume on Polymarket: $2.8K. Open liquidity in the YES/NO orderbooks: $668.58. Spread between best bid and best ask: 15.0¢.
Is this a trade recommendation?
No. Orrery describes — never predicts. Every signal on this market carries explicit Evidence, Backtest, and Action tiers. The Action is always one of: Watch only, Inspect timeline, Create alert, Verify source, or Ignore — never Buy or Sell. The probability above is the market's collective implied probability, not a forecast Orrery is publishing.
How fresh is this data and where does it come from?
This page revalidates from the public Polymarket APIs every 30 seconds. Probability and 24h-change come from Gamma; the chart series comes from the CLOB orderbook history; trade and holder data come from the Data API. The fetched-at timestamp on each block tells you exactly how old the underlying upstream pull was.
Alerts
In-app banners fire as soon as a rule is satisfied. Email digests are wired to a server-side cron and continue while your tabs are closed. Telegram and Discord are planned — every existing rule will keep working as channels light up.