Prediction market regulation in the EU may affect whether users can access Polymarket or Kalshi, place new positions, or claim existing outcomes. On September 11, 2026, reporting said ESMA questioned whether the platforms had the authorization needed to operate in the EU and whether their geo-blocking was complete. For users, the practical risks are interrupted access, uncertain settlement procedures, oracle disputes, and funds being locked in a contract or platform while rules are clarified.
What changed this week?
The key development this week is regulatory scrutiny, not a confirmed blanket ban. According to The Block’s report dated September 11, 2026, ESMA said major prediction platforms lacked EU authorization and questioned Polymarket and Kalshi about partial geo-blocking.
That distinction matters. A regulator asking questions can lead to clarifications, stronger access controls, enforcement, or a change in how a service operates. It does not by itself establish that every position will be cancelled or that every user’s funds are immediately unavailable. However, users should treat access and settlement as live operational risks rather than assuming that an onchain position is permanently reachable.
The issue sits within the EU’s broader framework for crypto-asset services. The Markets in Crypto-Assets Regulation, or MiCA, in the EU’s official legal text creates authorization and conduct requirements for covered crypto-asset activities. Whether a particular prediction-market structure falls inside a specific regulatory category can depend on its product design, operator, jurisdiction, and the services it provides. That classification is a legal question for regulators and qualified advisers, not something a wallet interface can determine.
Why authorization matters to prediction-market users
An authorization question is not only a business issue for Polymarket or Kalshi. It can change the way a user interacts with a market and the protections available if something goes wrong.
An authorized service may have obligations concerning governance, disclosures, market conduct, complaints, client assets, and access restrictions. The exact protections depend on the authorization and product. An unauthorized or unavailable service may still have technically functioning contracts, but users could face fewer practical routes for support, recovery, or dispute resolution.
This is especially important for people who think that “onchain” means “outside regulation.” A smart contract can continue accepting transactions while a website, frontend, RPC endpoint, payment provider, or operator blocks users in a particular region. The blockchain may preserve the transaction history, but it cannot guarantee that the user can legally or technically interact with the application.
The European Securities and Markets Authority’s crypto-assets and innovation materials provide the regulator’s broader context for EU crypto supervision. They are useful background, but they do not replace checking the platform’s latest regional terms or any specific notice issued to users.
Geo-blocking: what it can and cannot do
Geo-blocking uses signals such as IP address, account information, device location, identity checks, payment details, or other compliance data to restrict access from certain countries. A partial geo-block can mean that some pages or products are blocked while other functions remain visible, or that restrictions are applied only after a user tries to trade or withdraw.
For a wallet user, the important point is that changing the appearance of location is not a safe solution. Using a VPN, a borrowed account, false identity information, or a third-party access route can violate platform terms and potentially create additional compliance problems. It can also make it harder to prove ownership or complete a withdrawal later.
Possible effects of a new or expanded geo-block include:
- New positions may be unavailable to users in a restricted jurisdiction.
- A frontend may hide markets even though their contracts remain visible on a block explorer.
- Withdrawals or redemptions may require additional identity or location checks.
- Customer support may decline requests from prohibited regions.
- A platform may migrate, pause, or wind down certain markets.
- An account can become inaccessible even when its wallet keys remain under the user’s control.
A blocked interface does not automatically mean that an onchain position has been lost. It does mean that the user must separately investigate the contract, settlement rules, redemption path, and legal status before taking action.
Three layers of risk to separate
Prediction-market users often combine several different risks under the word “platform.” Separating them makes the situation easier to understand.
| Risk layer | What can fail | What the user should verify |
|---|---|---|
| Regulatory and access risk | A service restricts EU users, changes products, or loses a route to market | Current terms, country eligibility, notices, and withdrawal procedures |
| Oracle and resolution risk | The reported real-world outcome is delayed, disputed, or interpreted differently from the market wording | Oracle source, resolution time, dispute process, and finality rules |
| Contract and custody risk | A smart contract, operator, relayer, or custodian prevents movement or redemption | Contract address, admin powers, pause controls, token permissions, and redemption calls |
These layers can overlap, but they are not interchangeable. A self-custodied wallet may protect the private keys for a token while offering no protection against a market resolving according to an unexpected rule. Conversely, a platform may resolve a market correctly while its regional access controls prevent a user from reaching the redemption interface.
For a broader explanation of oracle design and why external data creates a new trust assumption, see How crypto oracles and DeFi price feeds work. For wallet users, the lesson is simple: ownership of a private key is only one part of the risk model.
Oracle resolution is not just a technical detail
A prediction market depends on a definition of the event and a process for deciding whether it happened. That process may use an oracle, a designated data source, an optimistic reporting system, a dispute mechanism, or a combination of these.
Consider a market asking whether an event will happen by a particular date. Several questions can affect the result:
- Which source determines the outcome?
- What time zone and cutoff time apply?
- Does a preliminary announcement count, or only a final official result?
- What happens if the source is delayed, corrected, unavailable, or contradictory?
- Who can challenge a proposed result, and how long is the challenge period?
- Can an administrator pause, amend, or cancel the market?
An oracle does not necessarily “know” the truth. It transmits a selected interpretation of an offchain event into an onchain or platform settlement process. That interpretation may be reasonable and still differ from what a user expected when placing a position.
Before interacting with a market, users should save the market’s original wording, rules, resolution source, and relevant timestamps. Screenshots can help document what was displayed, but they do not override the contract or official terms. If a market is disputed, the applicable rules—not social-media consensus—usually determine the result.
Smart-contract custody versus platform custody
Prediction markets can use different combinations of wallet custody and platform infrastructure. A user may sign transactions with a self-custodied wallet, while the market’s contracts, collateral, frontend, oracle, or redemption process still depend on third parties.
In a fully custodial arrangement, the platform may hold the user’s balance and record positions in an internal account. A regulatory or operational interruption can therefore affect both access and withdrawals directly. In a contract-based arrangement, the user may hold market tokens or claims in a wallet, but the claim may only have value if the contract can settle and a supported redemption route remains available.
Neither model removes risk. Self-custody changes who controls the private key; it does not make an event outcome, oracle, market operator, bridge, stablecoin, or legal status decentralized by default.
Users should distinguish these questions:
- Who controls the private key? Is the position in the user’s wallet or on an internal ledger?
- Who controls settlement? Can an operator, oracle, or administrator pause or change the result?
- Who controls the interface? Can the website restrict the user even if the contract remains live?
- What asset is held? Is the collateral a stablecoin or another token with its own issuer and transfer risks?
- How is redemption performed? Is there a permissionless contract call, or must the platform approve the withdrawal?
This is why a prediction-market position should not be treated exactly like holding a freely transferable cryptocurrency. It may be a conditional claim with dependencies that are not obvious from the wallet balance.
Practical checklist for EU and onchain users
If you hold a position or are considering a new one, take a conservative inventory before the platform changes its access policy:
- Check whether your country is currently eligible under the platform’s latest terms.
- Read any regulatory, geo-blocking, maintenance, or withdrawal notice in your account.
- Record market names, position balances, contract addresses, and transaction hashes.
- Confirm whether positions are held in your wallet or only represented by an account balance.
- Review the resolution source, cutoff date, dispute window, and administrator permissions.
- Keep enough network fees for a possible redemption or transfer, but do not approve unfamiliar contracts merely to test access.
- Revoke unnecessary token approvals only after confirming that doing so will not prevent a needed redemption.
- Avoid phishing links that claim to offer an EU withdrawal or “compliance unlock.”
- Do not use false location data or another person’s identity to bypass a restriction.
- Keep records for tax reporting, including deposits, trades, resolutions, and withdrawals.
If access is blocked, do not assume that repeatedly connecting a wallet or signing a message will fix the issue. Verify the official domain, inspect the requested transaction, and seek platform support through a known channel. A message asking for a seed phrase, private key, or unlimited approval is a scam warning, regardless of the regulatory story attached to it.
What to watch next
The next meaningful signals are likely to be formal notices, platform responses, updated country lists, changes to market availability, and instructions for existing positions. Users should look for clear language distinguishing new trading from the treatment of positions already open and the process for final redemptions.
It is also worth watching how EU authorities classify different prediction-market designs. A centralized operator, a smart-contract protocol with a hosted frontend, and a peer-to-peer settlement system may present different legal and technical questions. Similar user experiences do not guarantee similar regulatory treatment.
For self-custody users, the central takeaway is risk separation. Keep control of your wallet keys, but also understand that access to a prediction market can depend on geography, an operator, an oracle, a contract administrator, and the collateral asset. This week’s ESMA questions make those dependencies more visible; they do not turn every position into a lost asset, but they do make “I can see it onchain” an incomplete answer to whether you can use or redeem it.
