> For the complete documentation index, see [llms.txt](https://seer-2.gitbook.io/seer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://seer-2.gitbook.io/seer/why-did-previous-prediction-markets-fail/regulatory-attacks.md).

# Regulatory Attacks

As prediction markets can be used as a way to gamble and trade synthetic versions of stock/commodities (even if it’s far from being their more exciting usecases), it is unsurprising that they caught the attention of the regulators.

We saw two ways where it led to project failure:

* Overresponding to the regulatory environment.
* Underresponding to it.

**Overresponding**

Web2 prediction markets have generally been overresponding, the best example is PredictIt which thought the approval of US regulators as an experimental project. This led to the project having an extremely low trading limit of 850$ per market and per user preventing it to work as a free market (extremely successful actors have limited influence on the markets and the amount traded are too low to justify the existence of professionalised actors).

Worse, the regulators are trying to shut down the project\[23], showing that the regulatory road is subject to the whim of bureaucrats and politicians .

The other way to overrespond is to make systems which are so « decentralized » that they are unusable. An example would be Augur, whose contracts were purely permissionless, so permissionless that when they had to be updated, the only way was to shutdown the previous version for people to migrate to the new one which led to a downtime of TIME years (and broke long term markets).

Another example would be the Gnosis team which created Omen, but instead of putting it under their governance gave it to another DAO (dxDAO) which wasn’t aligned with their interests and ultimately abandoned it.

**Underresponding**

Other projects have treated prediction markets as a regular business. A good example would be Polymarket who was acting both as a developer, front end host, liquidity provider and oracle for its markets while operating as a classic company. It received a fine of 1.4 M$ \[24] which at the time was even higher than the total liquidity of the platform. Note that since the incident there has been some improvements.

We will see in the Decentralised Governance section how those issues can be solved.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://seer-2.gitbook.io/seer/why-did-previous-prediction-markets-fail/regulatory-attacks.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.