Kalshi will collect employment details for some bets to reduce insider-trading risk
The new rule targets informational advantages by requiring certain traders to share work data for specific contracts.

Kalshi, the prediction market platform, will require employment information for some bets as an insider-trading precaution. For decision-makers, it adds friction to certain participants and changes how these markets handle sensitive information.
Kalshi is adding a new compliance step for some prediction market bets: it will require employment information for certain contracts, specifically as an insider-trading precaution.
That headline matters because prediction markets live and die on information. If the “edge” comes from a person’s job, not from public signals, regulators and exchanges both worry about unfair advantage. Kalshi’s approach is essentially a gatekeeping mechanism. It is not saying every trader is doing anything wrong. It is trying to reduce the chance that a contract is being priced based on non-public knowledge tied to employment.
To understand why this is a big deal even if it sounds procedural, zoom out for a second. Prediction markets, unlike most traditional financial instruments, directly reflect beliefs about future events. That makes them powerful for forecasting, but it also makes them sensitive to who knows what, and when. The more a contract’s outcome relates to business operations, corporate strategy, hiring, contracts, litigation posture, or anything else that can be material before it becomes public, the more insider-trading concerns move from theoretical to practical.
Insider trading rules usually hinge on the idea of trading on material, non-public information. The challenge for a venue like Kalshi is that its product is built around trading forecasts. That means the market can attract participants who have different information sources, including professional roles. If Kalshi allows everyone to participate without any guardrails, the platform can become a magnet for the exact compliance nightmare regulators want to avoid: someone trading on privileged context.
So Kalshi’s rule functions like a “permissioning” layer for certain bets. By collecting employment information, the platform can identify whether a participant may be in a position where non-public details could plausibly influence their trading decisions. That is the heart of the precaution. It is also why the stakes feel personal for traders, but also for leadership at the companies building or overseeing market infrastructure: how do you balance openness with a credible compliance posture?
The Engadget source characterizes the hurdle as minor for the wrongdoers. The line you should keep in your head is that the rules may be a “minor hurdle” for people who cheat. In other words, requiring employment data is not the same thing as preventing deception. A motivated actor could still attempt to misreport information or route around the process. That doesn’t mean the rule is pointless. It means the rule is designed for a specific kind of risk reduction, not magical perfect prevention.
This is where board dynamics and product design meet regulatory reality. Exchanges and market platforms often face the question: what can we practically implement that makes enforcement possible and deterrence believable? Collecting employment information is a step that gives the platform something it can use. It can validate, flag anomalies, and demonstrate that it is taking insider-trading risk seriously. Those things matter because, in regulated markets, your compliance story is not just about preventing harm, it is about proving that you were paying attention.
There is a second-order implication here too. Once a venue starts asking for employment details for some contracts, it is shaping participant behavior. Some users will comply easily. Others may choose to avoid those bets entirely if the friction is too high. That could affect liquidity, pricing, and who shows up to trade. In prediction markets, liquidity is not just convenience. It can influence the accuracy of the signal the market generates.
For executives at other market operators, the lesson is straightforward: compliance is becoming part of product UX, even when the underlying technology is trading, not software tools. Rules that seem small on the surface can change who participates and how quickly information flows into prices. And if prediction markets continue to grow, the compliance expectations will likely expand too, especially for contracts that overlap with corporate-specific timelines and potentially material developments.
Kalshi’s employment-information requirement for some bets is a signal of where the industry is going. Prediction markets want scale, but they also need a credible guardrail against insider trading risk. The strategic question for any peer building similar systems is not whether compliance will matter. It will. The question is how you design it so it reduces risk without strangling the market’s ability to function.
This story's Key Insights and Take-aways are locked.
Create a free account to unlock Executive Actions for one credit.
Register to UnlockAlways free for Executives Club members. Join the Club
More in Technology

Oracle warns of a bug hackers used, after Google notified 100+ potentially vulnerable servers
A security flaw Oracle flagged, tied to a cybercrime gang campaign, is pushing boards to audit exposure fast.

Quake Champions gets a free 30th-anniversary battle pass and a massive networking overhaul
Lag compensation changes, new gameplay options, and a big cosmetic drop are the real “still alive” proof.

DeepMind's TacticAI predicts football plays up to 8 seconds early, Palmeiras tests live
A new AI coaching layer can forecast open-play dynamics from broadcast visuals, and Palmeiras is the first to run it live.
