> For the complete documentation index, see [llms.txt](https://vizo.gitbook.io/vizo-exchange-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://vizo.gitbook.io/vizo-exchange-docs/documentation/getting-started/editor.md).

# 3. Market Size and Product Positioning

### 3.1 Market Background Overview

By 2025, prediction markets will leap from a niche sector to a "**scalable trading and risk control tool**."

* **Regulatory & Compliance channels are opening.**
* **Trading volume is rapidly expanding**. Driven by sports and macro events, regulated platforms like Kalshi have disclosed weekly volumes exceeding $100 million (growing 10x over 2024). Industry observations suggest Q3 2025 aggregate volume across major platforms topped $3 billion, reflecting real demand and liquidity spillover.
* **DeFi Growth**: Prediction markets are seen as a high-elasticity branch of DeFi, with projected high compound growth rates (40%+) from 2025–2035.
* **Overall**: "Compliance Entry + Liquidity Expansion + Multi-platform Resonance" is upgrading prediction markets from "speculative scenarios" to infrastructure for price discovery and hedging.

*However, existing markets focus mostly on social events, lacking deep binding with real financial markets. This limits the audience to "niche speculators." VIZO identifies this gap and aims to combine the massive stock derivatives market with decentralized prediction markets.*

***

### 3.2 The Necessity of VIZO

At this industry inflection point, VIZO provides a system-level upgrade via its Dual-Engine Trading Architecture, Contribution-Based Market Making Incentives, Endogenous Compliance/Security, and Asian Content Strategy.

1. **Supply-Side Structural Gap**: Balancing Price Discovery and Playability. Current platforms are unbalanced: either "Pool-only" (easy to start, poor depth) or "Orderbook-only" (professional, hard to scale). VIZO Solution: Dual Mode (Peer-to-Peer Pool + CLOB). Placing "approachable odds aggregation" and "sustainable price discovery" in one system.
2. **Demand-Side User Segmentation**: From Entertainment to Professional Expression. Growth comes from the progression of "Newbie → Active User → Market Maker/Pro." VIZO Solution: Range, Binary, and 10-minute Crypto Markets lower the barrier, while CLOB handles "Duels, Fine-grained Pricing, Hedging," creating a natural upgrade path and increasing LTV.
3. **Liquidity Incentives:** From "Wash Trading" to "Contribution." VIZO Solution: Allocating 34% of tokens long-term to participants who "make prices more credible and depth more usable." This creates a self-growing liquidity network and clear incentive-contribution alignment for institutional funds.
4. **Compliance First & Fund Security**: VIZO Solution: Global license applications, endogenous KYC/AML, Geo-fencing, Dispute Arbitration. Fund security uses Segregation of Contract/Op Funds, MPC/Multi-sig, Time-locks, providing institutional-grade assurance.
5. **Asian Content Strategy**: VIZO Solution: Unifying Financial Markets and Pan-Entertainment Markets (Social/Stars/Sports). Using "Leaderboard + For You" for localization, creating a dual network effect of viewpoints and liquidity.
6. **Economic & Governance Sustainability**: VIZO Solution: Managing incentives via Weekly/Monthly Gates and Unlock Pools. Using GMV/OI tiers to prevent hyperinflation. Retaining parameter hot-updates and Black/White lists for governance.


---

# 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://vizo.gitbook.io/vizo-exchange-docs/documentation/getting-started/editor.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.