> For the complete documentation index, see [llms.txt](https://docs.unitas.so/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.unitas.so/overview/up.md).
# UP
UP Token Overview
UP is the native ecosystem and governance token of Unitas, designed to support long-term ecosystem participation, protocol governance, and alignment among users, contributors, partners, and other stakeholders.\
\
UP is intended to support governance participation over selected protocol and ecosystem parameters, including risk frameworks, product integrations, incentive programs, and broader ecosystem development.\
\
UP does not represent equity, debt, ownership, dividend rights, interest rights, or any claim on protocol revenue or assets of Unipay Labs Limited or any affiliated entity.
***
### Design Principles
The UP token is designed around four core principles:
1. **Long-term Alignment**\
UP rewards long-term participants who actively govern and support the protocol, rather than short-term speculative behavior.
2. **Sustainable Ecosystem Utility**\
UP’s utility is intended to grow with the development of the Unitas ecosystem, including product adoption, integrations, liquidity programs, governance participation, and long-term community involvement.
3. **Governance Participation**\
UP is designed to support phased governance participation. Governance may cover selected protocol parameters, ecosystem proposals, integrations, incentive programs, and risk-management frameworks, subject to technical readiness, security review, and applicable legal / compliance requirements.
4. **Transparency and Verifiability**\
Unitas commits to honest, ongoing disclosure of protocol revenue and economic activity as the basis for governance decisions.
***
## Governance
Unitas plans to introduce UP-based governance in phases. Once launched, UP holders are expected to be able to participate in governance processes covering selected protocol and ecosystem matters, which may include:
* Risk-management frameworks
* Ecosystem incentive programs
* Supported strategies and integrations
* Product parameters
* Liquidity and distribution programs
* Other protocol or ecosystem proposals within the approved governance scope
The governance framework is expected to include proposal discussion, off-chain signaling, and on-chain voting where appropriate. Final governance scope, voting rules, quorum requirements, proposal thresholds, and execution procedures will be published before official launch.
***
## sUP: Staked UP
Unitas plans to introduce a voluntary UP staking / locking mechanism as part of its phased governance framework.
The purpose of sUP is expected to be long-term governance alignment and ecosystem participation. sUP may represent locked UP and may be used for governance eligibility, voting weight, or other non-revenue-share ecosystem functions, subject to the final governance design.
The planned sUP mechanism is not based on block production, validator operation, consensus participation, or mining. It is expected to be a deposit / lockup-based mechanism.
sUP does not introduce additional UP supply and does not represent a separate token issuance. Final parameters, including lock periods, cooldown rules, voting weight, and eligibility criteria, will be published before official launch.
***
## Protocol Revenue
Unitas protocol revenue is primarily generated through product-level yield-sharing and strategy operations related to yield-bearing assets such as USDu / sUSDu and XGLD. For relevant yield-bearing products, net strategy yield is generally allocated according to the product-level revenue framework:
* 80% to holders of the relevant yield-bearing product
* 10% to the Insurance Fund
* 10% to Treasury / platform operations
This product-level revenue allocation does not represent dividends, revenue distribution, interest, guaranteed yield, or any claim on protocol revenue for UP holders.
Treasury / platform revenue is used to support protocol development, security, audits, infrastructure, integrations, operations, and ecosystem growth.
***
## Tokenomics
* Total supply: 1,000,000,000 UP
* Circulating supply at TGE: 12.6%
* Allocation:
* Ecosystem & Community: 45%
* Liquidity & Exchange Programs: 18%
* Investors: 22%
* Team & Advisors: 15%
* Ecosystem & Community allocation supports:
* User incentive programs and ecosystem campaigns
* Community growth
* Partner integrations
* Product adoption
* Liquidity & Exchange Programs allocation supports:
* Exchange integrations
* Market making
* Liquidity provisioning
* Trading and liquidity campaigns
***
## Vesting
* Team & Advisors:
* 12 month cliff
* 24 month vesting duration
* Linear unlock after cliff
* Investors:
* 12 month cliff
* 24 month vesting duration
* Linear unlock after cliff
* Vesting aligns token distribution with:
* Long-term protocol development
* Governance participation
***
## ‼️ Important Notice
UP is not a stablecoin, yield-bearing asset, equity instrument, debt instrument, or investment contract. UP does not represent ownership, dividend rights, interest rights, redemption rights, or any claim on Unipay Labs Limited, the Unitas protocol, or protocol revenue.\
\
UP holders do not currently receive protocol revenue distributions, guaranteed yield, fixed returns, or profit-sharing. Any future utility expansion, governance rollout, or staking / locking mechanism will be subject to technical readiness, security review, legal / compliance review, and official disclosure.
---
# 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://docs.unitas.so/overview/up.md?ask=&goal=
```
`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.
