# Mining & Messaging Reward Model

Sudo introduces Proof-of-Engagement Mining, a novel mechanism where every meaningful message becomes a tokenized interaction. This system transforms messaging activity into a measurable, on-chain contribution that generates SUDO token rewards. By tying rewards to verifiable engagement, Sudo creates a self-sustaining, anti-inflationary social mining economy.

\
**1. Messaging = Mining**

Every message sent by a verified Sudo user directly contributes to SUDO token mining.\
Rewards are calculated using multiple variables:

* Message Length & Quality: Longer, more meaningful messages are weighted higher.<br>
* Interaction Type: Direct Messages (DMs), group chats, and channel posts have different reward multipliers.<br>
* Proof-of-Use Verification: Anti-bot and anti-spam filters ensure all rewarded messages are encrypted, signed, and originate from authentic wallet activity.<br>

This ensures only genuine, user-driven interactions contribute to mining rewards.

#### 2. Daily Mining Pool Distribution

The daily reward pool is funded through SUDO token buybacks, creating a closed-loop reward system without inflation:

* Daily Reward Pool: Equivalent of 2 USDT worth of SUDO tokens (sourced from the hourly auto-buy allocation).<br>
* Per-User Cap: Maximum of 1 USDT worth of SUDO tokens per day.<br>
* Dynamic Difficulty: As user numbers grow, competition for rewards increases, and per-message rewards adjust automatically.<br>

#### 3. Anti-Spam Filters for Reward Eligibility

Sudo’s anti-spam framework ensures quality over quantity:

* Message Requirements:<br>
* * Minimum of 10 characters.<br>
  * No repetitive or low-entropy content (e.g., “aaa”).<br>
  * One reward per unique sender-receiver pair per message (no duplicate counting).<br>
* Bot Detection:<br>
* * Wallet activity and transaction patterns are analyzed.\ <br>
  * Message entropy and signature validation ensure originality.<br>
  * All messages are sent over Libsignal-encrypted transport, making spoofing or tampering impossible.<br>

#### 4. Reward Distribution Breakdown

The reward system uses weighted multipliers based on message type:

| Message Type   | Weight | Average Reward (SUDO) |
| -------------- | ------ | --------------------- |
| Direct Message | 1x     | 1                     |
| Group Message  | 1.2x   | 1.2                   |
| Channel Post   | 0.5x   | 0.5                   |

\
**Additional incentives:**

* Channel View Rewards: Readers can earn small rewards for engaging with channel content (engagement-based mining).
* Creator Earnings: Channel owners earn a small fee per 100 active readers, incentivizing high-quality content.<br>

#### 5. Monthly Cap & Leaderboard Incentives

To encourage sustained engagement without excessive emissions:

* Monthly Reward Cap: Maximum of 30 USDT worth of SUDO tokens per user.<br>
* Leaderboard Rewards: Top 100 monthly earners share an extra 1,000 USDT reward pool.<br>
* Gamified UI: Displays user rank, daily streaks, and performance stats to encourage healthy competition.<br>

#### 6. Reward Funding Mechanism

All mining rewards are funded entirely from the platform’s buy-and-burn model:

* Hourly allocation example: 10 USDT total buyback → 3 USDT to reward pool, 7 USDT burned.<br>
* No Token Inflation: SUDO is capped at 100 million tokens.<br>
* Rewards are Re-Circulated: Only pre-minted tokens enter circulation; no new tokens are minted.

<br>


---

# 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/vision-and-mission/mining-and-messaging-reward-model.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.
