# Supply

## Total Supply: <mark style="background-color:green;">1,000,000 UOS</mark>

\
The $uOS token serves as the core utility and governance token for the Universal Operating System protocol.  The token facilitates multiple revenue streams including:\
\
**App Store Revenue:** Fees from app sales and subscriptions within the uOS ecosystem\
**Premium OS Features:** Subscription fees for enhanced storage and advanced features\
**Agent Task Fees:** Fees collected from completed agent tasks and computations\
**Tokenized IP Revenue:** Royalties from agent-created content and licensing\
**Infrastructure Fees:** Hosting and OS usage fees for verified agents\
\
The token also functions as a governance mechanism, granting holders voting rights over critical protocol decisions including future upgrades and treasury management. Through the vote-escrow system (veUOS), token holders can lock their tokens to receive enhanced governance power and protocol revenue sharing.<br>

## Initial Claims & Migration: <mark style="background-color:green;">10% (100,000 UOS)</mark>

\
The SOL/UOS to WETH migration enabled protocol transition from Solana to Base. The process includes snapshotting SOL/UOS balances, generating Merkle proofs for claims, and implementing a secure claim system via uos.earth. All eligible holders receive UOS tokens at a 0.1:1 ratio.

All UOS/SOL holders get 0.1:1 UOS/WETH\
Claims available via uos.supply\
Immediate availability upon launch\ <br>

## Protocol Emissions: <mark style="background-color:green;">60% (600,000 UOS)</mark>

\
The veUOS system enables token holders to lock their UOS tokens to receive enhanced governance power and protocol revenue. Locking periods range from 1 week to 2 years, with longer locks providing higher voting power and revenue share. Each lock position is represented as a unique veNFT, allowing holders to manage multiple positions. Weekly rewards are distributed based on lock duration, amount, and protocol utilization.

Vote-escrow mechanism for governance\
Lock periods: 1 week to 2 years\
Weekly reward distributions\
Revenue sharing from protocol fees\
Multiple lock positions via veNFTs\ <br>

## Treasury: <mark style="background-color:green;">10% (100,000 UOS)</mark>

\
A 10% allocation of all newly minted $uOS is directed towards the UOS treasury, governed by the decentralized autonomous organization (DAO). This allocation is designed to support the ongoing development of $uOS and its related infrastructure, with a 4-year linear vesting period.

* DAO governed <br>

## Team: <mark style="background-color:green;">10% (100,000 UOS)</mark>

\
Linear vesting via Sablier ensures transparent and predictable token distribution, preventing large token unlocks that could impact market stability. This approach aligns long-term incentives between the team, treasury, and protocol success.\ <br>

## Initial DEX Liquidity: <mark style="background-color:green;">1% (10,000 UOS)</mark>

* &#x20;Uniswap v2 pair bootstrapping

## LP Staking Rewards: <mark style="background-color:green;">9% (90,000 UOS)</mark>

* 9% (90,000 UOS)&#x20;
* Incentivize liquidity providers\
  Distributed through Pool2\ <br>

## Contracts:&#x20;

uOS : Base  = [0xbE8728795b935bf6E2a9253Ce7a2Ef6fA831f51E](https://basescan.org/address/0xbe8728795b935bf6e2a9253ce7a2ef6fa831f51e)\
uOS : SOL  = [79HZeHkX9A5WfBg72ankd1ppTXGepoSGpmkxW63wsrHY](https://solscan.io/token/79HZeHkX9A5WfBg72ankd1ppTXGepoSGpmkxW63wsrHY)\
\
uOS - treasury = [0x5510d7fbA6E690771ED09E9260B58e094E4aa586](https://basescan.org/address/0x5510d7fbA6E690771ED09E9260B58e094E4aa586)

uOS - team = [Sablier ](<https://basescan.org/tx/0xae219d647261926155db2bd4ea35ea5ba7c4760f4c0dcf7e7553949e6f18b5f2 >)


---

# 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://universal-operating-system.gitbook.io/universal-operating-system/tokenomics/supply.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.
