> For the complete documentation index, see [llms.txt](https://subunit.gitbook.io/subunit-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://subunit.gitbook.io/subunit-docs/governance-tokenomics/tokenomics/usdsts-subvault-token-shares.md).

# $STS - Subvault Token Shares

The Subvault's decisions are entirely governed by $STS (Subvault Token Shares), which are the shares issued when staking into the Subvault.

**Owners of $STS have the right to decide on what properties are onboarded to the Subunit Protocol.**

These decisions will be made via Snapshot.box.

**Let's recap the flow:**

1. You stake USDc into the Subvault
2. You get $STS in return
3. You now use this $STS to vote on whether to accept a property on the platform via snapshot.box
4. Your $STS tokens will be diluted when that onboarding occurs (each $STS will be worth less USDc)
5. You will be issued $UNIT tokens that represent ownership of the new property's DAO 


---

# 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://subunit.gitbook.io/subunit-docs/governance-tokenomics/tokenomics/usdsts-subvault-token-shares.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.