Core Concepts

Polystrike is an oracle intelligence layer for Polymarket’s Elon Musk tweet count markets. This page explains the core problem and how Polystrike keeps you correctly informed about the true count.

The Problem: Two Counters, Both Wrong

Polymarket shows traders two tweet counters:

• XTracker (the settlement oracle): Updates every ~5 minutes. This is the number that actually determines who wins and loses.
• UI Counter: Displayed on the Polymarket trading interface. Frequently freezes or lags behind XTracker.

Most retail traders price their positions based on the UI counter. But the UI counter is often severely wrong — sometimes lagging by 5-10+ tweets. That lag is exactly what Polystrike surfaces — so you can see the true count instead of the stale display. (Note: the order book itself usually already tracks the real count, so a UI gap is monitoring information, not a free edge — see Trading Strategies.)

The Solution: A Third Counter

Polystrike maintains its own counter — the real counter — by querying Twitter every second for @elonmusk (every 5 seconds for other tracked accounts) and classifying each tweet against the exact settlement rules.

Counter	Source	Update Frequency	Settlement Authority
UI Counter	Polymarket frontend	Irregular, often frozen	None
XTracker	Settlement oracle	Every ~5 minutes	Yes (determines payouts)
Real Counter	Polystrike	As posts land — measured p50 11.5s from post to count	None (but most accurate)

Measured on production 2026-07-29: a new post is in the real counter a median of 11.5 seconds after it is posted (p90 12.6–15.1s, p99 28.2s, worst observed 631s). The floor is X’s own REST timeline index, which needs about 10.8 seconds at minimum to list a post — we already poll faster than X publishes, so polling harder does not move the median. Against a ~5-minute oracle cycle that means the real counter is usually ahead, and it also catches events the oracle never sees (deleted tweets). Being earlier is not the same as being profitable: the order book generally prices the real count, so treat this as accuracy, not edge.

Deleted Tweets

Elon Musk deletes tweets. If a tweet existed when XTracker last scraped, it counts toward settlement — even if it’s deleted by the time you check Twitter manually.

Polystrike captures tweets a median of 11.5 seconds after posting. If a tweet is later deleted we flag it with is_deleted: true and drop it from the count (is_counted goes to false), because the settlement oracle also removes deleted posts — a post that no longer exists must not be counted against a market that will not count it.

Deletion runs on a slower clock than capture: a full timeline re-read every 10 minutes, which is also what refreshes engagement metrics, and a post must be absent from two consecutive re-reads before we believe it — so a confirmed deletion takes roughly 20 minutes. That is deliberate: X’s timeline transiently omits posts that were never deleted, so a deletion needs to be right rather than fast. If the post reappears, it un-deletes and regains its count automatically. This means:

• Our real counter may diverge from what you see on Twitter right now, in both directions
• Right after a deletion our count is briefly high — we have not confirmed the removal yet, while the oracle may already have dropped it
• A tweet we still show as counted is one we have not yet seen vanish, not a claim that it survived

The is_counted Classification

Not every Elon tweet counts toward Polymarket settlement. The rules are specific:

Tweet Type	Counts?
Main feed post	Yes
Quote post	Yes
Repost (retweet)	Yes
Main-feed reply	Yes
Regular reply	No
Community repost	No

XTracker doesn’t expose this classification. Polystrike classifies every tweet in real time and exposes the is_counted field (Pro tier only).

The Three Deltas

Polystrike tracks three independent lag signals. Each measures a different gap between the counters:

settlement_delta

settlement_delta = real_counter - xtracker_counter

What it means: How far ahead of the settlement oracle we are. A positive value means Polystrike has counted tweets that XTracker hasn’t picked up yet — including deleted tweets.

display_delta

display_delta = real_counter - ui_counter

What it means: How wrong the Polymarket UI is. When this is large, most traders are looking at a stale number and may be mispricing their positions.

internal_delta

internal_delta = ui_counter - xtracker_counter

What it means: The gap between what Polymarket shows and what will actually settle. Can be positive (UI ahead of oracle) or negative (UI behind oracle).

Monte Carlo Predictions

Polystrike runs 1,000 Monte Carlo simulations per active event to produce bucket probability forecasts:

• p5: 5th percentile (optimistic low bound)
• p50: Median expected count
• p95: 95th percentile (pessimistic high bound)

The model is sleep-aware — it accounts for Elon’s Texas timezone sleep schedule. Tweeting velocity drops to near-zero during sleep hours, which is deterministic, not random.

Reliability Window

• Final 16 hours: Most reliable. The model has enough data to project accurately.
• 16-36 hours remaining: Moderate reliability. Use with caution.
• More than 36 hours: Early predictions carry 15-20% overestimation risk. The model tends to extrapolate current velocity too aggressively.

Tiers

Feature	Free	Pro ($79/mo)
Real-time counters & deltas	Yes	Yes
Recent tweets (last 15)	Yes	Yes
is_counted classification	Masked (null)	Yes
Full tweet history + pagination	No	Yes
Monte Carlo predictions	No	Yes
Trading signals (EV, Kelly)	No	Yes
Portfolio analysis	No	Yes
Rate limit	100 req/hr	10,000 req/hr