> For the complete documentation index, see [llms.txt](https://versus-x.gitbook.io/versus-x/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://versus-x.gitbook.io/versus-x/opportunity/market-gaps.md).

# Market gaps

Currently, the iGaming sector lacks or doesn’t fully satisfy the following:

**Skill gaming ecosystems:** The iGaming industry lacks true skill gaming options that allow players to compete in high-quality multiplayer or single-player games with integrated wagering. Current skill-adjacent offerings in iGaming, such as poker, daily fantasy sports, and esports betting, still involve significant elements of chance, external variables, or passive prediction rather than direct player performance. Meanwhile, web3 gaming lacks comprehensive skill gaming ecosystems that reward players purely based on their abilities rather than their financial investment. The prevalent play-to-earn model often prioritizes token holdings over genuine gaming talent, deterring players seeking platforms where skill determines success.

**High-quality, realistic sports games:** Despite their competitive nature and widespread popularity, sports remain underexplored in both sectors. In iGaming, wagering is largely limited to fantasy sports and sports betting, both of which involve predicting outcomes of events outside the player's control rather than competing directly. The market lacks high-quality, realistic sports games where players can wager on their own performance. In web3 gaming, blockchain-based sports games often lack the depth, graphics, and polish offered by traditional gaming platforms. The sector has yet to deliver sports games that can compete with established web2 titles while integrating meaningful wagering mechanics.

**Compete-to-earn wagering mechanism:** While sports focused skill gaming ecosystems are largely absent from iGaming, the specific mechanic of direct, real-time competition between players for real stakes is even rarer. Traditional iGaming operators offer extensive catalogs of slots, table games, and chance-based formats, yet none feature head-to-head multiplayer matches where the winner takes the pot based solely on their in-game performance. In web3 gaming, the play-to-earn model has demonstrated limited sustainability, with projects like Axie Infinity experiencing dramatic collapses due to token inflation outpacing demand. What the market lacks is a community-driven competitive platform where players face off against real opponents, where stakes scale with ambition, and where financial rewards flow directly from winning. This is the gap the compete-to-earn mechanism is designed to fill: a sustainable, transparent model where multiplayer competition and player skill are the sole drivers of earnings.


---

# 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://versus-x.gitbook.io/versus-x/opportunity/market-gaps.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.