> 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/mindshare.md). # Mindshare Mindshare is Souless' public intelligence layer for showing which markets and contributors are earning meaningful attention across the indexed social graph. It is related to InfoFi, but it is not itself the reward ledger: Mindshare is the discovery and measurement surface, while InfoFi determines eligibility, finalizes reward epochs, and produces claimable USDC allocations. > **Current scope:** V1 covers markets hosted by Souless today. Support for eligible external tokens is planned for V2 and is not live yet. ## What Mindshare shows The overview and token-detail surfaces support two Mindshare windows: * **24H** — the default view. * **7D** — a true seven-day Mindshare/InfoFi window, including comparison with the preceding seven days. Depending on the view, indexed data includes market Mindshare score, mentions, qualified mentions, participants, rank/share, contributor rankings, trending contributors, and score history. The 7D history is represented as 28 six-hour buckets. Changing the Mindshare window does **not** silently change unrelated trading statistics. Market volume, price change, and sparkline fields that are defined as 24-hour market context remain 24-hour values. Mindshare also exposes **lifetime finalized InfoFi rewards** for visible contributor wallets. That total includes finalized InfoFi/content allocations only; it does not include staking, creator, referral, Launch Partner, or protocol earnings. ## Social feed Mindshare includes an indexed X feed associated with Souless markets. The feed can be viewed globally or scoped to one token. The current feed supports: * original posts, replies, and quote posts; * pagination for browsing older activity; * photos, video, animated GIFs, previews, and alt text when available; * one post associated with every relevant Souless market rather than duplicated copies; * token-specific views; * live updates; * moderation without deleting the underlying indexed X record. The feed reads Souless' indexed data rather than calling X every time a user opens or scrolls it. ### Feed visibility is not reward eligibility A post appearing in Mindshare does **not** mean that it earned an InfoFi reward. Feed inclusion, semantic relevance, InfoFi qualification, final allocation, and claim status are separate states. A post can therefore be visible as market context while receiving zero InfoFi allocation. The public [InfoFi](/community/infofi.md) rules remain authoritative for reward eligibility. ## Contributor badges Where an X identity has been linked to a wallet, Mindshare can show market-specific badges: * **Top 10 Holder** and **Top 100 Holder** — based on eligible liquid and staked holdings. * **Staker** — for wallets participating in Souless staking. * **Early Believer** — based on the corresponding InfoFi record. * **Creator** — for the market's creator. Wallet-based badges are only attributed to an X author when Souless has a verified identity link. ## What contributors need to know To participate in InfoFi around a Souless market: 1. Use the X identity linked to the wallet you want Souless to attribute. 2. Make the market you are discussing clear enough for Souless to identify it. 3. Meet any staking or participation requirement shown for the relevant reward period. 4. Publish original, market-relevant information rather than ticker spam, copy-pasta, or engagement bait. 5. Remember that engagement can strengthen already-qualified content but cannot make irrelevant content eligible. 6. Wait for the reward period to finalize before treating an amount as claimable. Mindshare can display activity before an InfoFi reward period is finalized. Claimability exists only after the final allocation is published. ## How Mindshare and InfoFi connect ``` Verified X activity │ ├──────────────→ Mindshare feed and market/contributor views │ └──→ InfoFi eligibility → semantic qualification → reward allocation → USDC claim │ └── finalized results feed lifetime reward reads back into Mindshare ``` Mindshare is therefore a public discovery layer over community activity; it does not bypass or replace the InfoFi scoring and reward process. ## Moderation and integrity Moderation can limit, hide, or remove an item from the Mindshare presentation without deleting the indexed source record. Content marked potentially sensitive can also be shown in a limited state. Indexed posts, rankings, badges, and derived Mindshare values can be temporarily unavailable or corrected if upstream data changes. Finalized InfoFi claims remain governed by the published reward record. ## V2: external tokens hosted on Souless **Planned — not available in V1.** V2 is intended to let eligible tokens that were launched elsewhere be hosted on Souless so their communities can use Mindshare and participate in InfoFi without relaunching or replacing the token. An externally hosted token remains an external asset. Souless will identify it clearly as hosted rather than Souless-launched, and hosting will not imply that it received Souless' launch mechanics, permanent-LP guarantees, creator terms, referral terms, or Launch Partner economics. When V2 is enabled, each hosted market will show the participation requirements, reward source, supported market, and claim rules that apply to it before users contribute for rewards. The same basic separation remains: Mindshare shows and measures community attention, while InfoFi determines which contributions qualify and what becomes claimable. --- # 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/mindshare.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.