DevCommunity · Community protocol

Rewards Policy & How It Works

This document explains, in plain terms, how DevCommunity allocates its budget, ranks members, and calculates commissions — with concrete examples for each part, checked against the exact logic running in the smart contracts.

1Introduction

2How to join

3Budget allocation

4How the matrix tree is arranged

You F1 #1 F1 #2 branch 3 (only if needed) branch 1 — still open branch 2 — own F1 only branch 1 — still open branch 2 — own F1 only F1 #3 (your referral)
F1 #3 has no direct slot left under You (both branches taken), so it fills the earliest still-open branch-1 slot in the downline — here, under F1 #1. Branch 3 (dashed) only opens when no branch-1 slot is open anywhere within ~15 levels.
Filled only by that person's own F1 Open — can receive someone overflowing down Never receives overflow Opens only when truly needed

5Level and Generation — two different concepts

6Matrix commission

7Matching commission

8Income cap (Cap Max Out)

9Buying & selling DCT

10TWAP protection price

11Strategic partners

12Building new projects

13Encrypted mailbox

14Changing wallets