Do Kalshi’s geofences actually work? The app-version gap, explained

Explainer · Updated August 18, 2026 · 18+ · Not legal or betting advice · By BetG8 Editorial · Prediction Markets

What a geofence order actually requires

Three states have ordered Kalshi to stop offering certain event contracts to their residents, and in each case the remedy is the same: not a shutdown, but a fence. Kalshi keeps operating; it just has to keep a defined set of markets away from people located in that state.

That sounds like a technical problem with a technical answer, and to a point it is. All three orders point at commercial location-verification technology, and Kalshi engaged GeoComply, a Nevada-licensed vendor already used across regulated US sports betting. The harder part is the definition of “offering.” A court order tells an operator to stop serving a market to a state. It does not usually specify which build of which app that control has to live in. Until this month, nobody had to ask.

The three orders, and their deadlines

The Washington order is the broadest of the three. It covers sports, elections, politics, entertainment, culture, technology and science markets, plus so-called “mention” contracts. Markets on commodities, climate, economics and finance are explicitly left alone. The two-stage structure — a rough IP-and-residency fence first, a comprehensive one two weeks later — is itself an acknowledgement that this is not a switch you flip.

What happened in Nevada

Nevada’s deadline was August 12. On August 13, Gaming Control Board investigators placed nine separate trades on Kalshi’s mobile app while connected to cell networks inside the state. On August 14 the board took that to the First Judicial District Court and asked for $120,000 a day plus the state’s legal fees, arguing the company had profited from continued violation of Nevada law.

Kalshi’s answer, sent to the board on August 15 and repeated publicly by general counsel Rick Heaslip the following day, was not that the fence works and the trades did not happen. It was that the investigators got through by misrepresenting their residence and, in at least one case, by using a prior version of the Kalshi app that was not subject to geofencing. Kalshi said it had hired a state-approved vendor and kept regulators updated throughout the rollout.

The board rejected the framing, calling the accusations baseless and saying Kalshi “cannot obscure the fact it missed an agreed-upon deadline to comply with Nevada law.” The court has not ruled.

Why Michigan matters to the Nevada fight

Here is the part that turns a two-party dispute into an industry question. Michigan set the same August 12 deadline, with the same vendor. The gaming outlet InGame tested it and found that the block applied only to users who had installed the latest version of the Kalshi mobile app — and that the company does not require the update. An InGame reporter with an account registered in Indiana placed trades on sporting events from inside Michigan. After manually updating the app, the geolocation controls engaged and in-state sports trades were blocked. The outlet reported no prompt telling users to update.

That is an independent reproduction of exactly the mechanism Kalshi describes in Nevada, in a different state, by a party with no stake in the Carson City case. It does two things at once: it corroborates Kalshi’s explanation of how the investigators traded, and it undercuts the conclusion Kalshi draws from it. If an old build is a loophole a state investigator has to deliberately exploit, it is also a loophole any ordinary user is sitting inside by default, simply by not updating.

The question this leaves open

Strip out the accusations and a narrow, answerable question remains: when a court orders an operator to stop serving a market to a state, is the order satisfied by a control that exists only in the newest version of an app the operator does not force anyone to install?

There are real arguments on both sides. Mobile platforms make forced updates awkward, and an operator cannot reach into a phone. Server-side enforcement — rejecting the trade at the exchange rather than hiding the market in the client — would close the gap, but it is a different piece of engineering than a client-side geolocation SDK, and no order we have seen specifies which one is required.

Whichever way Nevada’s court goes, the answer will not stay in Nevada. Michigan already has the same fact pattern. Washington’s comprehensive deadline lands September 2 with the same vendor and the same penalty rate. Every state that has treated a geofence as the practical remedy now has a reason to ask how the fence is built, not just whether one was ordered.

What to watch next

• August 19, 2026 — Washington’s preliminary IP-and-residency fence is due.
• September 2, 2026 — Washington’s comprehensive fence is due; $120,000 a day runs after that.
• Pending — whether the Carson City court finds Kalshi in contempt, and whether penalties run from August 12.
• Watch for — any order that specifies server-side enforcement rather than an app-level control. That would be the first order written with this gap in mind.

FAQ

Does Kalshi’s geofence block everyone in a restricted state?

Not necessarily. Testing in Michigan reported by InGame found the geolocation controls took effect only for users running the current version of the Kalshi mobile app. Users on an older build were still able to place sports trades from inside the state, and the app did not prompt them to update. Kalshi has made the same point in Nevada, where it says state investigators traded through a prior version.

Which states have ordered Kalshi to geofence?

As of August 18, 2026: Nevada and Michigan, both with August 12 deadlines, and Washington, with a preliminary geofence due August 19 and a comprehensive one due September 2. Each order covers a different list of market categories.

What penalties are on the table?

Nevada’s Gaming Control Board has asked its court for $120,000 a day plus legal fees. Michigan has threatened up to $500,000 a day. Washington’s order carries $120,000 a day if the September 2 deadline is missed.

Is this a technology failure or a compliance failure?

That is the open question, and a Nevada court will answer part of it. The geolocation vendor, GeoComply, is a state-licensed location verification firm. The dispute is not really about whether its technology works but about whether an operator has complied with a court order when the control ships only in a version many users have not installed.

Does this affect Polymarket too?

The orders discussed here are directed at Kalshi. Polymarket faces its own state actions, including Baltimore’s consumer protection lawsuit filed August 13, 2026, but the app-version geofence question documented in Nevada and Michigan concerns Kalshi’s mobile app specifically.

Sources

• Gambling Insider: Nevada seeks daily fines as Kalshi blames investigators for geofencing workaround
• InGame: Kalshi’s geofence applies only to the updated app
• Gambling Insider: Prediction markets weekly roundup, August 14, 2026
• Washington State Standard: Kalshi ordered to sharply curtail operations in Washington
• GeekWire: Kalshi ordered to shut down sports and election markets in Washington by September 2

See the dated prediction market change log

Back to BetG8 home