# Sudo

![](/files/7oFxOk4KXwNmcxdpkqhI)

> **Sudo Messenger is a Web3-native communication layer that combines secure chat, wallet actions, communities, AI assistance, and on-chain coordination.**

Sudo is designed for the moments where messaging and Web3 activity overlap: a trader sends a payment in context, a community gates access through a contract, a creator grows through channels and QR links, a team discusses governance proposals, or a user asks an AI assistant to explain wallet activity.

## What makes Sudo different

Most messaging apps are built around conversations. Most wallets are built around transactions. Sudo connects both models so social context, identity, assets, and safety controls can live in the same product experience.

## Product pillars

| Pillar                | What it unlocks                                                                                            | Why it matters                                                                          |
| --------------------- | ---------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------- |
| **Messaging first**   | DMs, groups, channels, media, calls, reactions, stories, invites, QR sharing.                              | Users start with familiar daily communication instead of a complex wallet dashboard.    |
| **Wallet native**     | Built-in wallet, chat payments, swaps, transaction cards, escrow, multisig, token locks, approvals review. | Financial actions become easier to understand because they happen in context.           |
| **Community powered** | Public/private groups, channels, discussion groups, creator surfaces, affiliate hooks, live streaming.     | Web3 projects need distribution, retention, and moderation, not only token mechanics.   |
| **Trust centered**    | E2EE payloads, verification QR, app/chat locks, disappearing messages, blocked users, privacy controls.    | Messaging and wallet actions require confidence before users can rely on the app daily. |
| **AI assisted**       | AI Explorer, transaction bot, watcher bot, approvals bot, My Tokens bot, My Locks bot.                     | AI reduces friction around complex wallet data, alerts, approvals, and token state.     |

## Recommended reading path

1. Start with [What is Sudo?](/overview/what-is-sudo.md) for the product narrative.
2. Read [Product at a glance](/overview/product-at-a-glance.md) for feature scale and category breakdown.
3. Use [User journeys](/overview/user-journeys.md) to understand common workflows.
4. Deep dive into [Chat](/chat/chat.md), [Social](/social/social.md), [Web3](/web3/web3.md), [Privacy](/privacy-and-trust/privacy.md), and [AI](/ai-and-bots/ai.md).
5. Use [Feature inventory](/reference/feature-inventory.md), [FAQ](/reference/faq.md), and [Glossary](/reference/glossary.md) as references.

## Design direction

The intended GitBook experience is black, gold, sharp, and premium. Use a dark GitBook theme with a gold accent close to `#F0B90B`.


---

# 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://docx.sudochat.app/sudo.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.