Will Elon tweet 140–154 times May 30–June 6?
Probability
0¢
1h
+0.0pp
24h
-0.4pp
24h Vol
$0.00
Liquidity
$0.00
Orrery restored this market from Polymarket's closed-market records. Treat the numbers below as last-known market context, then verify the resolution source before citing the outcome.
Canonical status
confidence: mediumSource status (Polymarket)
Derived status (Orrery)
Reason
Upstream marked the market closed/settled with NO price dominant.
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
LOW risk- End date
- Jun 6, 2025
- UMA status
- resolved
- Resolution source
- Market type
- Multi-outcome (neg-risk)
- Part of a multi-outcome event (neg-risk): only one market can resolve YES.
Probability (last 7 days)
+0.0pp 7dResolution & Risk
LOW risk- End date
- Jun 6, 2025
- UMA status
- resolved
- Resolution source
- Market type
- Multi-outcome (neg-risk)
- Part of a multi-outcome event (neg-risk): only one market can resolve YES.
Verification Brief
A guided checklist for what must be proven before this market is treated as reliable context.
The market appears resolved. The useful check is whether the source and final oracle state match the displayed outcome.
Verification goal
Map resolution-relevant sources to the exact criteria needed to avoid misreading price as settlement.
What needs proof
Primary source
requiredConfirm the primary tracker / counter and whether it directly answers the market's resolution question.
Current evidence: Post Counter
Contract wording
requiredExtract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule.
Orrery verification task Will Elon tweet 140–154 times May 30–June 6? State: Resolved NO — officially resolved Need sources for: 1. Primary source: Confirm the primary tracker / counter and whether it directly answers the market's resolution question. 2. Contract wording: Extract the exact condition that makes YES resolve true and note any exclusions, time zone, deadline, or fallback rule. 3. Liquidity context: Check whether the move is supported by enough liquidity and volume to treat it as meaningful context. Drop only durable links that map to one criterion. Research only. Not trade advice.
Orrery verification brief Will Elon tweet 140–154 times May 30–June 6? State: officially resolved Verify: Primary source + Contract wording Price is not settlement. Research only. Not trade advice.
Market link goes in reply
A controlled loop for durable sources. Every source must answer one criterion from this Verification Brief.
Sources
0
Criteria covered
0
Reviewed
0
Awaiting review
0
Submit a source mapped to a criterion
Recent source checks
Pilot audit summary
Research only · Not trade advice · Every source maps to one criterion
Timeline
critical · price · trade flowRecent 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
1Market Description
This market will resolve according to the number of times Elon Musk (@elonmusk), posts on X between May 30, 2025, 12:00 PM ET and June 6, 2025, 12:00 PM ET. For the purposes of this market, only main feed posts, quote posts and reposts posts will count. Replies will NOT count towards the total - however, replies on the main feed such as https://x.com/elonmusk/status/1786073478711353576 will be counted by the tracker. Deleted posts will count as long as they remain available long enough to be captured by the tracker (~5 minutes). The resolution source for this market is the ‘Post Counter’ figure for posts found at https://www.xtracker.io/. Individual posts can be viewed by clicking "Export Data". If the tracker does not update correctly in accordance with the rules, X itself may be used as a secondary resolution source.
Why this category?
confidence: mediumCategory
Source
Matched term
TechReason
No rule fired; using Polymarket's own category hint "Tech".
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 "Will Elon tweet 140–154 times May 30–June 6?"?
As of Thu, 04 Jun 2026 13:58:48 GMT, YES is priced at 0% implied probability on Polymarket. The price changed -0.4pp in the last 24 hours, +0.0pp in the last hour, and +0.0pp in the last 7 days.
When does this market resolve?
This market resolves by Jun 6, 2025 (2025-06-06T12:00:00.000Z). Resolution is determined from UMA optimistic oracle (resolved).
What source determines the outcome?
Resolution is sourced from UMA optimistic oracle (resolved). 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?
$0.00 of trading volume in the last 24 hours. Lifetime volume on Polymarket: $232.5K. Open liquidity in the YES/NO orderbooks: $0.00. Spread between best bid and best ask: 0.1¢.
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.
Top Holders
11 wallets- Shrill-Placode5.0K
- Murky-Oversight2.6K
- Sweet-Yahoo695
- Tame-Bob500
- Rapid-Vanilla329
- 0xa5ef…2966173.1K