> 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/developers/security.md). # Security and trust Souless reduces authority by separating token, market, fee, community, and data responsibilities. It does not remove all trust. ## Contract properties * Launch tokens are fixed-supply and non-upgradeable after one-shot finalization. * Official LP positions cannot be transferred or reduced by the locker. * USDC-side and launch-token-side LP fees use separate paths. * Token-side fees follow a delayed, restricted path separate from USDC-side rewards. * Community governance uses typed, bounded actions and cannot rewrite finalized epochs. ## Trust assumptions Users rely on deployed contracts and dependencies, Arc finality, USDC, Uniswap V3 behavior, and off-chain indexing or classification for display. Reward proofs and published totals allow claims to be checked independently. Launch or reward finalization can be delayed, while public fallback paths limit permanent dependence on one service. An unavailable indexer affects product views, not finalized chain ownership. No completed public audit is claimed here. Never share a seed phrase or private key. Use only an official Souless security contact when one is published. --- # 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/developers/security.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.