> For the complete documentation index, see [llms.txt](https://nextmars2009.gitbook.io/better/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://nextmars2009.gitbook.io/better/3/challenges-for-blockchain-prediction-market.md).

# Challenges for blockchain prediction market

While the various Defi products are extremely hot, the prediction market is quite cold. Although smart people know that the prediction market is certainly valuable and likely to blow up in the future, why is the prediction market still in an awkward position of "Get up early and catch up late"?

Throughout the history of the blockchain prediction market, there have been several major problems.

1\) Low liquidity in the long-tail market. Every particular market is likely to be a long-tail market, as there is not enough liquidity if no one is trading, which makes trading impossible and will ultimately lead to a failure to be widely accepted by users.

2\) Poor performance of the underlying public chain. This is the Achilles heel of Ethereum.

3\) High user threshold and poor product interaction experience.

4\) The oracle is not decentralized enough.

5\) The opportunity cost of funds during the waiting period for prediction results.

6\) Lack of sustained attractiveness of the prediction topic.

7\) Regulatory compliance issues. This is the sword of Damocles for most prediction markets.


---

# 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://nextmars2009.gitbook.io/better/3/challenges-for-blockchain-prediction-market.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.