# Group & Channel Video Conferencing — Zoom-Style VCaaS Integration

Sudo introduces embedded video conferencing as a native feature within Groups and Channels, enabling creators, DAO communities, and dApp projects to host secure, Web3-authenticated meetings. Unlike traditional platforms such as Zoom or Google Meet, Sudo’s video conferencing is decentralized, wallet-based, and token-gated—giving communities full ownership of their communication spaces.<br>

#### 1. Key Features

Sudo’s video conferencing system integrates directly into group and channel environments, offering:

* Web3 Login: Only verified wallet holders can join video rooms, removing the need for email/password-based access.
* Group Owner Controls: Meeting hosts can start or end sessions, mute participants, and enable screen sharing.
* Token-Gated Meetings: Access can require holding a specific token or NFT, verified on-chain.
* Live Chat and Reactions: Real-time messaging and reactions during video calls for interactive participation.
* End-to-End Encryption (E2EE): Calls are secured using WebRTC standards for maximum privacy.
* Multi-Platform Support: Works on Android, iOS, and Web through WebRTC and native integrations.\ <br>

#### 2. Technical Stack

The system is built on a scalable, real-time media architecture optimized for Web3 authentication:

* Video Transport: WebRTC with both peer-to-peer and TURN relay options for connectivity across all networks.
* Identity Authentication: WalletConnect and Sign-In With Ethereum (SIWE) for decentralized login.
* Backend Signaling: Custom Node.js WebSocket server for connection management.
* Media Server: Mediasoup, Janus, or LiveKit for high-performance group calls and streaming scalability.
* UI/UX Layer: Flutter for mobile clients and React for the web interface.<br>

#### 3. Meeting Workflow

1. A user joins a group or channel via WalletConnect.
2. The group owner selects “Start Meeting” to initiate a video session.
3. The WebRTC handshake process begins to establish a secure connection.
4. The backend signaling server validates the meeting room and initializes peer connections.
5. An encrypted video/audio channel is established between participants.
6. If token-gated, an on-chain verification event is logged to confirm eligibility.\ <br>

#### 4. Security and Privacy

* No Centralized Login: Access is managed entirely through wallet signatures.
* On-Chain Access Control: Token or NFT ownership determines eligibility for closed meetings.
* Privacy by Default: No cloud recording unless explicitly enabled by the group admin.
* Ephemeral Links: Meeting links are dynamically generated with expiration to prevent unauthorized access.\ <br>

#### 5. Use Cases

The integrated video conferencing feature supports a variety of Web3-native community needs:

* DAO governance and strategy sessions.
* dApp project AMAs and community Q\&A events.
* Token-gated private meetings for holders or VIP members.
* Influencer-hosted live interviews and discussions.
* Onboarding workshops and community education sessions.<br>

#### 6. Monetization Opportunities

Sudo’s conferencing feature is directly tied to the SUDO token economy:

* Paid Room Access: Charge SUDO tokens or specific NFTs for meeting entry.
* Sponsored Rooms: Allow projects to pay for branded meeting environments.
* Call Credit Model: Provide free minutes each month, with additional usage billed in SUDO.
* Premium Tiers: Offer advanced features like recording, whiteboards, and large participant capacity for premium-paying groups.


---

# 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-18.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.