> 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/economics-and-business/images-and-media.md).

# 7. Economic & Commercialization Model

## 7.1 Business Model & Revenue 

**a) Platform transaction fee is fixed at 1%, distributed according to the following proportions:**

1. 33% -  Liquidity Provider Rewards
2. 33% - DAO Governance Fund & Protocol Treasury (Operations and Maintenance)
3. 33% - Token Holders

**b) Market Listing Fee:** 

* Partners (brokers, exchanges) can pay listing fees.

**c) Data Services**: 

* Open market APIs to quantitative trading and financial research institutions.

**d) Ecosystem Token Value Capture:**

* A portion of the transaction fees is used to repurchase the platform token (PST), forming a value closed-loop.

***

## 7.2 Game Model 

#### **Cryptocurrency 10-Minute Session Up/Down Prediction Game** 

* **Predict**: The rise/fall of the next 10m K-line relative to the opening price.
* **Options**: UP / DOWN (optional FLAT if "absolutely unchanged" determination is needed).
* **Timeline**: 
  * t<sub>0</sub> Market Creation → t<sub>0</sub> + 10min market is the betting period (users always bet on the next market; betting is not supported while the current market is running);
  * t<sub>1</sub> = t<sub>0</sub> + 10m Closing → The opening price (price at t<sub>0</sub>) and the closing price (t<sub>1)</sub> are used to determine the win/loss.&#x20;
  * If the closing price is greater than the opening price, it is UP; otherwise, it is DOWN.
* **Source**: Aggregated exchange price, resolution 1m/10m; locked data snapshot must be written to on-chain/backend immutable ledger.
* **Settlement (Parimutuel)**: The winning pool divides the entire pool proportionally fee = 0
  * Individual Settlement = ![](/files/RoS2gI5YO8MCwVMRhIZi),&#x20;
  * where S<sub>u</sub> = individual bet amount,&#x20;
  * S<sub>w</sub> = total amount of winning side,&#x20;
  * S<sub>all</sub> = total amount in the pool.

#### **Stock Range Game (Friday Closing Price Range)**&#x20;

* **Goal**: Predict "which discrete price range this Friday's closing price will fall into".
* **Range**: 5 buckets (example) \[\<A], \[A∼B), \[B∼C), \[C∼D), \[≥D], ranges are automatically generated.
* **Timeline**:&#x20;
  * Fri After close, the next market opens for sale.&#x20;
  * Fri Close(t−Δt) is the betting deadline (suggested Δt=30min).&#x20;
  * Fri Close Fetch the official closing price (Nasdaq/NYSE official consolidated closing price).
* **Settlement**: Hitting the range = winner; the winning side divides the entire pool proportionally        (fee = 0).

#### **Stock Daily Up/Down Prediction Game (Daily relative to open price)**&#x20;

* **Goal**: Predict whether the closing price vs. opening price is up or down on the day.
* **Options**: UP / DOWN.
* **Timeline**: Reg-hours open → opens for sale; close - Δt stops sales (suggested Δt=30min, to avoid last-minute rush). Determined by the opening price and official closing price of the underlying stock on the day.
* **Source**: Compliant data source (NASDAQ/NYSE official close).

#### Dual-Stock "Which Rises More" (Single-Day Competition)&#x20;

* **Goal**: Compare the percentage gain of two stocks on the day, which one is greater.
* **Options**: A\_higher / B\_higher.
* **Timeline**: Both assets on the same trading day,&#x20;
  * open: opens for sale,
  * &#x20;close - Δt: stops sales (Δt suggested 30min).&#x20;
  * Different exchanges/time zones: calculated based on their respective official opening/closing; must be aligned to the same calendar day.
* **Settlement**: The winning side divides the entire pool proportionally.
* **Special Note**: Any asset trading halt/no closing price; Company action (split/merger) effective on the day → use adjusted price or declared rules.

***

## 7.3 Market Odds Model&#x20;

The market currently includes two mainstream mechanisms: Pari-mutuel / CLOB, each with its own pricing formula, betting/settlement calculation, slippage and fund depth impact, fee model, risk limit calculation, and example values.

* **Phase One Model**: Parimutuel Contract Pool Design Document - V1.0&#x20;
* **Phase Two Model**: "VIZO" CLOB Setup PRD - V2&#x20;

***

## 7.4 SKU Category Planning (TBA)

***

## 7.5 Assets

**a) Financial Assets (17)**&#x20;

* Apple, code: AAPL
* Microsoft, code: MSFT
* Nvidia, code: NVDA
* Amazon, code: AMZN
* Alphabet (Google's parent company), code: GOOGL
* Meta (formerly Facebook), code: META
* Tesla, code: TSLA
* TSMC, code: TSM
* Broadcom, code: AVGO
* AMD, code: AMD
* Qualcomm, code: QCOM
* Oracle, code: ORCL
* Intel, code: INTC
* S\&P 500 ETF, code: SPY
* Nasdaq 100 ETF, code: QQQ

**b) Crypto Assets (4)**&#x20;

* BTC
* ETH
* BNB
* SOL

**c) Dual-Asset Competition Types (7)**&#x20;

* AAPL vs MSFT
* GOOGL vs NVDA
* INTC vs AMZN
* AVGO vs TSM
* META vs TSLA
* ORCL vs QCOM
* AMD vs TSLA

**d) Markets in Other Fields** \
[https://ai.feishu.cn/wiki/QYXLwnFLXiEFQ0kenBecjENwnje?from=from](https://www.google.com/search?q=https://ai.feishu.cn/wiki/QYXLwnFLXiEFQ0kenBecjENwnje?from%3Dfrom)\_copylink


---

# 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/economics-and-business/images-and-media.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.