# Group & Channel Monetization — From DAO Rooms to Paid Access

Sudo transforms traditional chat groups and channels into tokenized, on-chain micro-communities, where group owners can monetize participation, govern through DAOs, and provide exclusive, token-gated experiences. This integration of ownership, monetization, and governance positions Sudo as the default communication layer for Web3-native communities.<br>

#### 1. Group & Channel Structure

Sudo supports multiple types of groups and channels, each with unique access models and monetization potential:

* Public Groups: Open for anyone to join, with moderation controls and the ability to participate in message rewards.
* Private Groups: Invite-only access, with full owner control over entry and monetization.
* DAO Rooms: Token- or NFT-gated communities where entry is determined by on-chain asset ownership, enabling governance voting, revenue sharing, and advanced community tools.<br>

#### 2. Monetization Tools for Group Owners

Sudo equips group and channel creators with multiple ways to generate income:

* Zoom-Style Meetings: Owners can host encrypted audio and video sessions within their communities. Payment can be made directly in SUDO tokens or through a token burn mechanism.
* Paid Memberships: Owners may charge a one-time or recurring fee for access. Payments are split so that 80% goes to the group owner and 20% is used to buy and burn SUDO, contributing to token scarcity.
* In-Group Ad Slots: Group owners can auction advertising space within their community. Ads are bid on using SUDO tokens, creating an additional token sink.
* Channel Boosting (Visibility): Members can burn tokens to increase the channel’s visibility on the Sudo Explore page. A weekly leaderboard determines which boosted groups gain featured placement.<br>

#### 3. Governance & Moderation

DAO-based groups introduce decentralized governance features:

* Members can vote on bans, adjust reward allocation percentages, and enable or disable specific features such as calls, meetings, and boosts.
* Groups can link to verified smart contracts so that only wallets interacting with those contracts are eligible for auto-onboarding.<br>

This allows DeFi protocols, NFT projects, and DAOs to maintain secure and automated membership lists.

#### 4. Engagement Rewards

Sudo incentivizes both creators and participants:

* Group creators receive referral bonuses when new users join Sudo via their invite links.
* Users earn bonus rewards for joining groups linked to verified smart contracts, encouraging engagement with ecosystem projects.<br>

#### 5. Smart Contract Verification Process

When a group creator links a smart contract to their community, Sudo verifies its authenticity by checking whether the creator’s wallet is the deployer or owner of the contract. Once confirmed:

1. The system scans all unique wallet addresses that have interacted with the contract.
2. Only wallets already registered on Sudo are auto-added to the group.
3. The process creates a direct bridge between a project’s on-chain activity and its private community space.<br>

This capability enables DEXs, DeFi dApps, NFT projects, and DAOs to use Sudo as a fully integrated communication hub.

#### 6. Impact on the Token Economy

Group and channel monetization activities are tightly coupled with SUDO’s deflationary model:

* Creating a group or linking a contract triggers a token burn.
* Paid visibility boosts, username purchases, and DAO feature activations reduce circulating supply.
* As user demand grows, token scarcity increases, accelerating the economic flywheel of higher token value and greater ecosystem adoption.


---

# Agent Instructions: 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:

```
GET https://docs.sudochat.app/sudo-whitepaper/overview/publish-your-docs-15.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.