📈Tokenomics
💠 Token Structure Overview
Server Protocol operates using a dual-token model:
$SERVER – The main utility and economic token.
$BYTES – The participation and governance token, earned through staking.
💰 $SERVER – Main Token
Total Supply: 100,000,000,000 $SERVER (fixed, no inflation).
Decimals: 9
Use Cases:
Submitting proposals and voting (as fees)
Funding open-source grants
Incentivizing developer and community activity
Treasury accumulation and future governance
🧠 $BYTES – Governance & Participation Token
Supply: Dynamically minted through staking $SERVER
Decimals: 9
Use Cases:
Voting (1–10,000 $BYTES per vote)
Submitting proposals (1,000,000 $BYTES burned per proposal)
Reputation gain (drives vote weight)
Burn Mechanics: All $BYTES used are permanently burned
Dynamic Emission:
Base rate: 100 internal units/second/$SERVER staked = 0.0000001 $BYTES/second
1 $SERVER → ~0.00864 $BYTES/day
10,000 $SERVER → ~86.4 $BYTES/day (before penalty)
Penalty Over Time:
After 1 month of inactivity: emission decreases weekly
Week 1: -10%
Week 2: -20%
Week 3: -30%
Week 4: -40%
Week 5: -55%
Week 6: -70%,
Week 7: -85%,
Week 8+: -100%
📦 Token Distribution (for $SERVER)
Community & Grants
50%
50,000,000,000
Liquidity
25%
25,000,000,000
Team
15%
15,000,000,000
Staking
10%
10,000,000,000
⏳ Vesting for Team & Advisors
Cliff: 3 months
Vesting Period: 24 months linear
Start: At Mainnet launch
Mechanism: Handled on-chain for transparency and traceability
🔄 Treasury Reflows
All $SERVER used as platform fees (for proposals and voting) flows back into the Treasury Wallet, and from there can be:
Used for grant distribution
Allocated to ecosystem development
Reserved for strategic governance-based reallocations
Last updated