> For the complete documentation index, see [llms.txt](https://oaisis.gitbook.io/story.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://oaisis.gitbook.io/story.fun/dive-deep/ai-3-3/staking-and-voting.md).

# Staking & Voting

## iOS Staking

iOS staking is a core element of the ai(3,3) system:

* **Staking Process**: OS token holders can bond OS to iOS at a 1:1 ratio at any time. iOS can be staked at any time.
* **Voting Power**: Voting power is assigned proportionally to the amount of iOS staked.
* **Reward Eligibility**: Only staked iOS can receive protocol fees, voting incentives, and rebase rewards.
* **Active Participation Required**: Unlike ve(3,3), active participation and voting is required every epoch to receive rewards.

<figure><img src="/files/7F6yWTnb4DQ5ecuNs98n" alt=""><figcaption></figcaption></figure>

## aiOS Automated Voting & Reward Collection

aiOS simplifies the user experience and automates ideal voting and reward collection:

* **Automated Voting**: Ossy automatically votes for optimal pools through data analysis
* **Automated Reward Claims**: Automatically claims all rewards after epoch transitions
* **Compound Effect**: All rewards are reinvested to increase the aiOS ratio
* **Time Saving**: Users don't need to waste time on complex voting strategies or reward claiming processes

## Epoch Structure and Reward Distribution

The ai(3,3) system operates based on weekly epochs:

* **Epoch Length**: Each epoch is 7 days (starting Thursday 00:00 UTC)
* **Voting Period**: During each epoch, iOS stakers vote for their preferred liquidity pools
* **Emission Distribution**: Based on voting ratios, the OS emission for the next epoch is distributed to the voted LP pools as iOS.
* **Reward Claims**: After epoch transition, fees and voting incentives from the previous epoch can be claimed


---

# 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://oaisis.gitbook.io/story.fun/dive-deep/ai-3-3/staking-and-voting.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.