> For the complete documentation index, see [llms.txt](https://cura-docs.openrank.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cura-docs.openrank.com/channel-wallet-and-tokens.md).

# Channel Wallet and Tokens

Using Cura, moderators can setup a community wallet and launch a channel token, distribute it fairly to community members, and set up sustainable incentives for engagement and contribution.&#x20;

In crypto social, engagement is more than participation—it’s an asset. Cura takes this concept further by transforming contributions into ownership, creating sustainable, thriving and aligned communities.&#x20;

This unlocks a contribution and reputation based incentives system that enables Farcaster channel moderators to launch tokens for their channel/community.&#x20;

## Why Contribution and Reputation based Channel Tokens

* **Empowered Communities:** Channels can create self-sustaining economies aligned with their goals and values.
* **Rewarding Engagement:** Members are incentivized for meaningful contributions, fostering stronger connections.
* **Fair Token Distribution:** Transparent processes ensure fairness, reducing zero-sum behavior and farming.
* **New Revenue Streams:** Swap fees from token trading provide ongoing revenue opportunities for the channel.


---

# 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://cura-docs.openrank.com/channel-wallet-and-tokens.md?ask=<question>&goal=<endgoal>
```

`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.
