> 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/seer-solution/the-chicken-and-the-egg-problem.md).

# The Chicken and the egg problem

Considering what we have mentioned before and the ecosystem actors present in all Predicition Markets we can arrive to the conclusion that we might Initially face a tridimensional chicken and the egg problem:

* Traders can’t trade if there is not enough liquidity.
* In the absence of subsidies or a significant trading volume allowing them to profit from the spread, providing liquidity is not profitable due to the impermanent loss (see Lack of Liquidity section).
* Information seekers cannot get accurate estimates as markets are only efficient if there are a significant amount of actors participating. They can’t convince other actors either if the markets are not widely used.

Therefore we need to find a way to initially solve the chicken and the egg problem....


---

# 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, and the optional `goal` query parameter:

```
GET https://seer-2.gitbook.io/seer/seer-solution/the-chicken-and-the-egg-problem.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.