> 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/networks-and-reference/changelog.md).

# Changelog

This page records public documentation and protocol-economic changes.

## 11 September 2026

* Marked Souless **LIVE on Arc Mainnet** and published the current production guarded-launch, fee, Community, Token Protection, and Uniswap V3 contract addresses from the 10 September mainnet deployment.
* Updated Arc Testnet to the current launch/community stack: Guarded V3 Launch Coordinator `0x2Ced6CA529b4df254C2e4C76795966a4c9233c6f`, MultiPosition LP Locker `0x4e5D47bf9DbE40e95C3274FD20d303a9C9320897`, Token Fee Timelock `0xD001571374bDF9670Ff03F2130245e0E5E538c42`, Fee Dispatcher `0x09c6Dd59eB008df8dA75a0F10f5089f3010673CE`, Community Rewards Distributor `0x30bD3ec17292B6E2A0D203e21b1711dba779E3A6`, and Community Governance `0x7169b87F191Da91a5Fcc733DAA328b798252300C`.
* Documented launch-time Community policy: a Community-enabled launch may start with **10%–70% Community**, with Creator receiving `70% - Community`; Staking may start at **20%–80% of Community** and InfoFi receives the remainder.
* Clarified that the selected launch policy is active from **epoch 1**. Governance is not required to establish the starting allocation; later governance changes remain bounded and apply to future eligible epochs.

## 7 September 2026

* Updated the published Arc Testnet guarded-launch and fee-routing addresses to the deployment current at that time.
* Removed stale deployment-state language from the public documentation.

## 6 September 2026

* Added the Mindshare Community page with 24H/7D market and contributor views, token-scoped social feed behavior, verified contributor badges, moderation semantics, live updates, and lifetime finalized InfoFi reward reads.
* Documented the planned Mindshare/InfoFi V2 boundary for external-but-Souless-hosted tokens without presenting that support as live V1 behavior.
* Updated Community Mode documentation for Community Reward Policy V3 on Arc Testnet.
* Corrected stale governance/reference language that described protocol fees as having a permanent 25% minimum. The protocol share is the residual and is 20% in the fully loaded Community + referral + Genesis case.
* Added the Launch Partner pool to the fee-accounting flow and fixed stale Community reward-range text encoding.

## 27 August 2026

* Published the first GitBook documentation foundation.
* Documented the Arc Testnet guarded-launch and liquid-staking/governance deployments current at that time.
* Separated launch, Opening, AMM, USDC-side LP, and token-side LP fee explanations.
* Added Launch Guard, market, staking, governance, InfoFi, identity, reputation, data, security, and failure-mode specifications.


---

# 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/networks-and-reference/changelog.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.