> 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/community-mode.md).

# Community Mode

Community Mode attaches staking, fee-funded rewards, contribution recognition, Mindshare context, and bounded governance to an eligible market. It is external to the token.

```
Ordinary ERC-20
       │
       ▼
Community Mode
       │
       ├──→ 1:1 liquid staking ──→ Participation history
       ├──→ USDC reward epochs ──→ Wallet claims
       ├──→ InfoFi + Mindshare ──→ Contribution context and rewards
       └──→ Bounded governance
```

Enabling Community Mode does not wrap the market, restrict transfers, require a Souless router, or upgrade the ERC-20. If Souless interfaces were unavailable, the token and Uniswap market would continue to work.

## Starting allocation

Creator and Community share a fixed **70%** of collected USDC-side LP fees. The default starting policy is **60% Creator / 10% Community**, but a creator can choose a different starting allocation when launching with Community Mode enabled:

* Community may start from **10% to 70%** of LP fees.
* Creator receives the remainder of the fixed 70% pool: `Creator = 70% - Community`.
* This means Creator may start from **60% down to 0%**.

The Community allocation is then split between Staking and InfoFi. At launch, Staking may be set from **20% to 80% of Community rewards** and InfoFi receives the remainder. The default is **50% Staking / 50% InfoFi**.

The launch-selected values are initialized as the token's genesis Community policy and apply from **epoch 1**. The creator does not need to wait for a governance proposal or a later epoch to establish that starting allocation.

## After launch

Governance may ratchet the Community share upward from the market's established floor, reducing Creator share by the same amount inside the fixed 70% creator/community allocation. Governance cannot later reduce Community below that floor. Independently, governance may set Staking to 20%–80% of Community rewards for a future eligible epoch; InfoFi receives the remainder.

Finalized allocations must consume a feature's full available pool or leave that feature's full amount as carryover.

Referral and Genesis Launch Partner allocations are separate temporary overlays funded from the protocol residual. Launch-time Community settings and later Community governance cannot redirect those allocations.

## Current deployments

| Network     | Community Rewards Distributor                | Community Governance                         |
| ----------- | -------------------------------------------- | -------------------------------------------- |
| Arc Mainnet | `0x7F78bA801587E143c0D79b230ff1Dc903A53Fc5f` | `0xF7D06C796D2F196974A8191D2d227779C0bb07E3` |
| Arc Testnet | `0x30bD3ec17292B6E2A0D203e21b1711dba779E3A6` | `0x7169b87F191Da91a5Fcc733DAA328b798252300C` |

See [Arc Mainnet](/networks-and-reference/arc-mainnet.md) and [Arc Testnet](/networks-and-reference/arc-testnet.md) for the complete deployment tables.


---

# 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/community-mode.md?ask=<question>&goal=<user_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.