Why Kalshi Mentions Markets Resolve The Way They Do
The four rules every mention contract has to answer before you trade — and how they caused three of the most disputed resolutions so far.
⚡ 30-Second Answer
Every mention market answers four questions in its rules:
- What exact phrase qualifies?
- Who must say it?
- Where (live audio, transcript, captions, graphics)?
- What is the “source of truth” Kalshi will check?
If a contract resolves No and you think the word was said, the failure is almost always in #3 or #4 — not #1.
📜 The Four Rule Questions
#1WHAT: What exact phrase qualifies?
Each mention contract defines the precise word or phrase that triggers a Yes resolution. "Border" and "borders" may be different. "ICE" the agency and "ice water" are different. Root words, plurals, and abbreviations are not interchangeable unless the contract rules explicitly say so. Read the exact phrasing in the contract terms before trading.
#2WHO: Who must say it?
The contract defines which speakers count. A commentator, a sideline reporter, and a moderator reading audience questions are three different scopes. If the contract says "the host," a guest panelist saying the word does not trigger resolution. Speaker scope mismatches are the second most common source of disputed resolutions.
#3WHERE: Where does it need to appear?
Live audio is not the same as an official transcript. Closed captions are not the same as on-screen graphics. Transcripts are cleaned — filler words, false starts, and off-mic audio are routinely removed. The contract specifies which medium is the resolution source. If you heard it live but the transcript was cleaned, the contract resolves based on the transcript.
#4SOURCE OF TRUTH: What source will Kalshi actually check?
This is where most disputed resolutions originate. Contracts specify a named-outlet list, an official transcript provider, or a "consensus of credible reporting" standard. If a rally happens and no approved outlet covers it, the event did not happen for resolution purposes — even if attendee video exists. The source-of-truth rule is the contract's final arbiter.
🧪 Three Cases That Confused Traders
The Sanders rally case
Words were said at a public rally. Attendee video confirmed it. No approved outlet covered the event.
Contracts resolved No.
This is a Rule #4 failure, not a bug. The contract's source-of-truth list did not include attendee-captured video or social media posts. Because no named outlet published coverage of the event, the resolution source contained no evidence of the phrase. The rules worked exactly as written — the gap is in what the rules consider evidence, not in whether Kalshi followed them.
The Coinbase self-mention case
A CEO read mention-market terms during his own company's earnings call.
Contracts resolved Yes, as the rules specified.
The open question is not whether the resolution was correct under the rules — it was. The open question is whether mention markets where a named speaker can trigger their own contract are "readily susceptible to manipulation" under CFTC Core Principle 3. That is a listing standard applied before a contract is approved, not a resolution standard applied after trading.
High-multiplier repricing
A contract priced at 93 cents dropped to 30 cents within hours of first opposing liquidity.
No resolution dispute — this is order-book mechanics.
A 93-cent price implies roughly a 93% probability of Yes. That means roughly 7% of the time, the event does not happen — and when it does not, the repricing is violent because: (1) the order book on the No side was thin, (2) early sellers have outsized price impact, and (3) the base rate was already stretched. The 93x potential payout on the No side is the mirror image of that thin book. This is not a platform error; it is the math of low-probability event pricing.
🧭 Decision Tree: “I think my contract resolved wrong”
Did the approved source cover the event?
├─ No → The resolution is correct per the rules.
│ You are looking at a Rule #4 failure.
│ No dispute path changes this.
│
└─ Yes → Did the official transcript contain the
exact phrase?
├─ No → Transcripts are cleaned. The "live
│ audio" you heard is not the resolution
│ source. Rule #3 applies.
│
└─ Yes → Was the speaker in the scope defined
by Rule #2?
├─ No → Speaker scope mismatch.
│ Rule #2 applies.
│
└─ Yes → Was the exact phrase required
(vs. variants)?
├─ Match → File a formal
│ dispute with
│ Kalshi support.
│
└─ Variant not accepted
→ Rule #1 applies.🚫 What This Page Does Not Say
- We do not call any specific Kalshi resolution “right” or “wrong.” The rules are specific and public; the contract terms are filed with the CFTC.
- We do not allege manipulation. “Readily susceptible to manipulation” is a CFTC listing standard (Core Principle 3). Whether mention markets meet that threshold is an open regulatory question, not a settled fact.
- We do not advise traders to buy or sell any mention contract.
📚 Frequently Asked Questions
🔗 Related Reading
Earnings Mentions Markets Explained
How earnings-specific mention contracts work.
Is Kalshi Safe?
Kalshi's regulatory status, CFTC oversight, and fund protection.
How Markets Settle
The general settlement process across platforms.
Contract Wording Literacy
How to read prediction market contract terms before trading.
Polymarket Resolution-Clause Fallback
The Polymarket-side analog: how fallback clauses can flip a market to 50-50 if the trigger event never happens.
Source transparency: Rule descriptions on this page are based on Kalshi's published contract terms and help documentation. Case descriptions reference publicly resolved contracts and do not cite secondary journalism, affiliate sites, or user-generated content. CFTC Core Principle 3 language is sourced from cftc.gov. This page does not receive compensation from any prediction market platform.