> For the complete documentation index, see [llms.txt](https://superfluid.gitbook.io/superfluid/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://superfluid.gitbook.io/superfluid/protocol-overview/use-cases/social-and-community.md). # Social & Community ### Gradual Social Token Incentives Instead of airdropping social tokens to community members and creator audiences in one go, what if you could stream social tokens to them by-the-second over time? This is powerful as it is more aligned with ongoing loyalty. For example, the longer a community NFT holder holds their NFT, the more social tokens they will accrue. This is opposed to the NFT holder getting the airdrop at once and immeadiately selling the NFT as the airdrop has been acquired. Check out Reverb, a hackathon project that uses this concept. Reverb's music platform streams social tokens to individuals for the different artists they listen to 👇 {% embed url="" %} ### Perpetual Conditional Rewards (PCR) Superfluid Protocol has plenty of potential to improve the way we incentivize our communities. One good example of this is the PCR model. ![](/files/4wBDf4wplUskQJJAJGLj) With the PCR, rewards can be distributed to participants ($PCR holders in the graphic) based on their progress towards a particular KPI metric. Funding of rewards can be done with money streams and the distribution to participants is accomplished with the Superfluid Instant Distribution Agreement. The KPI completion status is verified with UMA's KPI Options. A community might use this to incentivize members to boost Twitter followers (the KPI being follower count) or development activity (the KPI being # of GitHub repo stars) and in all, to provide a scalable incentive system to reward members for driving results. Read more on the PCR concept here 👇 {% embed url="" %} --- # 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 dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter: ``` GET https://superfluid.gitbook.io/superfluid/protocol-overview/use-cases/social-and-community.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal. 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.