# Tokenomics

## Supply and Distribution

The supply and distribution structure of OS tokens is as follows:

### **Total Supply**: 1 billion (1,000,000,000) OS

### Distribution

<figure><img src="/files/zXIpxtfYz0YKqlfHxpSy" alt=""><figcaption></figcaption></figure>

<table><thead><tr><th width="162.35546875">Breakdown</th><th width="85.24609375">%</th><th width="158.10546875">Amount</th><th width="96.55078125">OS/iOS</th><th>Description</th></tr></thead><tbody><tr><td>Bonding Curve</td><td>30%</td><td>300,000,000</td><td>iOS &#x26; OS</td><td></td></tr><tr><td>Genesis Liquidity</td><td>5%</td><td>50,000,000</td><td>OS</td><td></td></tr><tr><td>Ecosystem</td><td>15%</td><td>150,000,000</td><td>OS</td><td>Airdrop, Grant, Fund</td></tr><tr><td>Incentives</td><td>10%</td><td>100,000,000</td><td>iOS</td><td>Voter Incentives, Liquidity Incentives</td></tr><tr><td>DAO</td><td>10%</td><td>100,000,000</td><td>iOS</td><td>Future contributors</td></tr><tr><td>Emissions</td><td>30%</td><td>300,000,000</td><td>iOS</td><td></td></tr><tr><td><strong>Total Supply</strong></td><td><strong>100%</strong></td><td><strong>1,000,000,000</strong></td><td></td><td></td></tr></tbody></table>

## Value Accrual

The Story.fun protocol is designed to continuously accumulate value for the OS token.

### OS Token Flywheel

The value creation mechanism of the OS token operates in the following flywheel structure:

<figure><img src="/files/leZDUnLmduEJAJTH7p25" alt=""><figcaption></figcaption></figure>

#### **ai(3,3) Flywheel Structure**:

* **$iOS Voters**:
  * Receive 100% of trading fees
  * Acquire voting incentives from AI Agents
  * Determine liquidity direction through emission
* **Traders**:
  * Benefit from low slippage
  * Optimized price execution
  * 100% of trading fees forwarded to iOS holders
* **Liquidity Providers (LP)**:
  * Receive emissions from iOS voters
  * Provide liquidity to AI Agents
  * Provide low slippage to traders
* **AI Agents**:
  * Acquire liquidity from LPs
  * Provide voting incentives to iOS voters
  * Promote value circulation within the ecosystem

### OS Demand/Supply Pressure Design

The value creation mechanism of the OS token operates through the following demand and supply pressures:

* **Demand Increase Factors**:
  * **Launchpad Transactions**: All launchpad transactions are made in OS, creating continuous demand
  * **iOS/aiOS Staking**: Demand for OS staking to obtain voting rights and rewards
  * **Portfolio Token Distribution**: High-growth potential AI Agent project tokens distributed to the OS community, creating additional value
  * **aiOS Buyback Mechanism**: All trading fees and incentives are bought back as iOS and re-staked, creating continuous demand
* **Supply Limitation Factors**:
  * **Project Graduation**: When projects graduate from the launchpad, OS liquidity is locked, reducing supply
  * **PVP Rebase**: Early withdrawal penalties are redistributed to stakers, reducing circulating supply
  * **Emission Reduction**: Gradual reduction of emissions over time

### Protocol Value Convergence Structure

Story.fun is designed to converge all value within the ecosystem to the OS token:

* **Fee Monetization**:
  * All DEX trading fees are distributed to iOS/aiOS stakers
  * More trading volume → More fees generated → Higher staking yield → Increased OS demand
* **Launchpad Value Capture**:
  * All projects successfully graduated from the launchpad lock OS liquidity
  * More projects graduate → More OS is locked → Supply decreases
* **Self-Reinforcing Cycle**:
  * OS value increase → More staking → More liquidity → More trading volume → More fees → OS value increase
* **Ecosystem Expansion Effect**:
  * As the OAISIS ecosystem expands, more use cases and integrations contribute to OS token value
  * The value of services provided by AI Agents like Ossy and StoryGPT is reflected in the OS token

Through this design, the OS token functions beyond a simple governance token, serving as an asset that captures the value of the entire OAISIS ecosystem. As AI Agents grow in Story.fun, their value is designed to continuously converge to the OS token.


---

# Agent Instructions: 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://oaisis.gitbook.io/story.fun/dive-deep/tokenomics.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.