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

# InfoFi

InfoFi turns verifiable, useful community participation into transparent USDC reward allocations.

## InfoFi share of Community rewards

For a Community-enabled launch, the creator chooses the starting split between Staking and InfoFi during launch. Staking may receive **20%–80% of the Community allocation** and InfoFi receives the remainder, so InfoFi may also start from **20%–80% of Community**. The default is **50% Staking / 50% InfoFi**.

The selected split applies from epoch 1. Later governance can change that split within the same bounds for future eligible epochs. Changing the split changes the size of the InfoFi pool; it does not change the scoring or qualification rules below.

## Public rules

* Rewards are organized by token and epoch.
* Configured X author-to-wallet attribution, contribution timing, a positive historical canonical stake balance, and a reference to at least one configured market identifier determine basic eligibility.
* A post must pass the epoch's versioned semantic qualification. Engagement cannot make a post pass.
* Irrelevant content, ticker spam, copy-pasta, and integrity-disqualified activity receive zero regardless of engagement.
* The finalized epoch publishes pool totals, verifiable claim data, algorithm version, and claim status.
* A wallet can claim its finalized allocation once.

```
Attributed activity + historical stake -> eligibility -> semantic review -> allocation -> USDC claim
```

## InfoFi and Mindshare

[Mindshare](/community/mindshare.md) is the public discovery and measurement surface around indexed market activity. InfoFi is the reward qualification, finalization, and claim system. A post can appear in the Mindshare feed or contribute to visible market context without qualifying for an InfoFi allocation.

Mindshare currently supports 24H and 7D views and can display lifetime finalized InfoFi earnings for visible contributor wallets. Those lifetime totals include finalized InfoFi/content allocations only; they do not include staking, creator, referral, Launch Partner, or protocol earnings.

## Published scoring guarantees

The semantic service evaluates market relevance, informational value, originality, specificity, narrative understanding, and integrity. A basic genuine market opinion may qualify; sophistication and audience size are not requirements. Engagement can amplify already-qualified information but cannot create eligibility. Stake alignment is bounded and cannot rescue weak content. One qualifying contributor may receive the full InfoFi pool.

Prompts, thresholds, dimension weights, engagement weights and saturation points, aggregation curves, early-signal calibration, stake curves, and anti-abuse heuristics remain private. Eligibility rules, algorithm version, pool size, final allocations, on-chain root, claim proof, and historical results remain auditable. Each finalized epoch permanently records its scoring and semantic-model versions.

## Narrative feedback

Selected high-signal eligible contributions may become bounded evidence for later narrative-classifier runs. The selection count and weighting are intentionally private. This improves market context without treating engagement as semantic truth and without automatically training or changing model weights. After finalization, there are no retroactive monetary claims for that epoch.

## External hosted tokens

External-but-Souless-hosted token support is a planned Mindshare/InfoFi V2 capability, not part of the current V1 support boundary. See [Mindshare — V2: external Souless-hosted tokens](/community/mindshare.md#v2-external-souless-hosted-tokens) for the intended separation between Souless-launched markets and externally hosted markets.


---

# 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/infofi.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.