> For the complete documentation index, see [llms.txt](https://docs.souless.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.souless.fun/community/staking.md). # Staking Staking deposits the real launch token into a universal Community Vault and mints its canonical transferable receipt, `sTOKEN`, at 1:1 atomic units. `sTOKEN` is a withdrawal claim. It does not rebase and the vault does not assign it a second price. The core invariant is `vault assets ≥ canonical receipt supply`. ``` Stake TOKEN ──→ Community Vault ──→ equal sTOKEN to wallet Unstake sTOKEN ──→ Community Vault ──→ equal TOKEN to wallet ``` There is no forced lock. Leaving can reduce current-epoch participation or governance power, but does not forfeit token ownership. ## Staking share of Community rewards For a Community-enabled launch, the creator chooses the starting Staking share during launch. Staking may receive **20%–80% of the Community allocation**, with InfoFi receiving the remainder. The default is **50% Staking / 50% InfoFi**. That starting split applies from epoch 1. Later governance can change the Staking/InfoFi split within the same 20%–80% bounds for future eligible epochs. This percentage determines how the Community USDC pool is divided; it is not a promised staking yield. ## Reward qualification Stake is measured over time from historical canonical-receipt checkpoints. For each constant-balance segment, direct staking weight is `duration × balance^0.6`; an account's epoch weight is the sum of its segments. The staking USDC pool is allocated pro rata by those weights, with deterministic atomic-unit rounding. Reward weights are not a guaranteed return. V1 finalization supports direct canonical `sTOKEN` history. Although adapter registration exists, finalization currently fails closed when an active DeFi adapter is present because a portable historical checkpoint source has not been established. Arbitrary wrappers do not count. Staking rewards are USDC and are claimed from finalized epoch distributions. They are separate from the token returned on unstake. --- # 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 by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://docs.souless.fun/community/staking.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. 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.