When a Nevada state court issued a temporary restraining order, attention turned quickly to Kalshi and whether the company had stopped taking wagers from Nevada residents. Now, just days after that 14‑day TRO took effect, questions are emerging over Kalshi’s compliance and how some Nevada users appear able to place sports-style bets despite the court’s directive.
What the temporary restraining order aimed to do
A temporary restraining order (TRO) is designed to freeze a situation while the court sorts out the law. In this case, the 14‑day TRO reportedly sought to halt Kalshi’s activity that a Nevada court says falls within state wagering regulations while the parties litigate jurisdiction and statutory issues.
Practically speaking, a TRO can require a company to suspend certain services to a defined group — here, Nevada residents. Enforcement of a TRO requires both clear language in the order and mechanisms to verify compliance, which is where ambiguity can creep in.
Why do some Nevada users still see markets?
There are several plausible explanations for why bets continued to appear on Kalshi for some Nevada accounts. One possibility is technical lag: geofencing, IP blocks, and app store updates don’t always propagate instantly, so customers on the edge of enforcement can slip through for hours or even days.
Another possibility is user-side workarounds, such as VPNs or proxy servers that obscure location. Those tools aren’t new, and they complicate any operator’s efforts to comply with geographically limited injunctions. Finally, there’s the question of whether certain account types or open positions were carved out by the order, allowing preexisting contracts to remain active.
Enforcement challenges for courts and platforms
Court orders travel through legal channels; they don’t always translate into instant engineering changes. Companies must balance legal risk with technical feasibility, and sometimes that produces a messy interim period where front-end controls lag behind legal obligations.
From the court’s point of view, a TRO violation can lead to contempt proceedings and sanctions. From the platform’s side, accidental noncompliance — for example, incomplete geoblocking — is different from willful violation, and the remedy depends on intent, speed of correction, and documented efforts to comply.
Possible explanations at a glance
Possible explanation
What it would imply
Technical propagation delay
Temporary, fixable; shows rollout gaps rather than deliberate disobedience.
User circumvention (VPNs/proxies)
Compliance harder to guarantee; operators may need stricter identity checks.
Order carve-outs for existing contracts
Exposes the company to contempt and potential penalties if proven.
Deliberate noncompliance
Exposes company to contempt and potential penalties if proven.
How regulators and the company might respond
Regulators can ask for immediate compliance reports and logs showing user location and transactions. If discrepancies remain, they can return to court for emergency enforcement or contempt hearings to compel quicker action.
Kalshi, for its part, would be expected to demonstrate the steps it took to stop Nevada betting — snapshots of geofence settings, transaction timestamps, and communications with users are typical evidence. Transparency, in this moment, both reduces legal risk and reassures other users.
What Nevada users and bettors should know
If you’re a Nevada resident who placed bets after the TRO was announced, treat those positions cautiously. They may be subject to reversal or dispute if a court later determines they were placed in violation of the order. Holding onto documentation — receipts, timestamps, and screenshots — can be important if a dispute arises.
Operators and bettors often learn the hard way that legal orders and user habits don’t sync up neatly. I’ve watched similar situations where users assumed a service was still legal simply because the interface remained usable, only to face account freezes or voided wagers when the legal dust settled.
Practical steps to reduce risk
Stop placing wagers if you’re in the affected jurisdiction until the legal picture clears.
Save transaction records and communications from the platform.
Follow public filings and official notices rather than social chatter for the authoritative position.
At this stage, the picture remains murky: some Nevada accounts still seeing Kalshi markets could reflect technical lag, user circumvention, lawful carve-outs, or something more troubling. Courts move deliberately, and the next few days of filings and compliance reports should make the facts clearer — or at least give the parties a chance to tidy up the mess.
