Gauss Docs
  • 🌐Getting Started
    • Welcome to Gauss
    • Whitepaper
      • Blockchain Providers Need to Do Better
        • Solving a Lack of Token Adoption
          • An Evolving Space With Untapped Potential
        • Security & Reliability
          • Curation & Vetting
            • Important Note For Brands
        • Token Creation
      • WHY BUILD WITH GAUSS?
      • Use Cases
        • Use Cases (Chart)
      • Roadmap
      • Technical Background and Blockchain Development
        • Why Another Blockchain?
        • Gauss 1.0: Built With Efficiency and a Strong Infrastructure to Launch Rapidly
        • Gauss 2.0: Added Functionality For a Better User Experiance
          • Noble Swap 2.0
          • NFTs in Gauss 2.0
          • Token Development Kit (TDK)
          • Gaming DAO
          • Omnipool
      • Token Economics
        • Gang Token Economics: Designed to Ensure Trust and Transparency
        • Token Locking Schedule
        • Reflections: Rewarding the Gauss Community
        • Charitable Allocations: Grants, Scholarships, & Financial Assistance
      • The Gauss Team
      • Important Definitions
      • DISCLAIMER
        • PURCHASER WARNING
        • PROMINENT STATEMENTS
        • FUTURE STATEMENTS
        • VALUE RISKS
        • NOT A SECURITY
    • How To Connect
      • Create Metamask Wallet
    • Links
  • ⚡Launching with Gauss
    • Benefits of Building with Gauss
      • Fostering an Environment for Success
      • Gauss Growth Grant Program
      • Gauss Liquidity Program
      • Ecosystem Integrity Fund
      • Client Referral Program
    • A Guide to Curation
      • Core Principles and Curation Guidelines
      • Curation Stages and Processing Fees
    • Building on Gauss
  • 🖥️Gauss Ecosystem
    • Gauss Chain
      • Polygon-Edge Overview
      • Architecture
      • Consensus
      • Client Modules
        • Blockchain
        • Minimal
        • Networking
        • State
        • TxPool
        • JSON RPC
        • Consensus
        • Storage
        • Types
        • Syncer
        • Sealer
        • Other Modules
      • Polygon-Edge Performance Reports
      • For Developers
        • Operate a Node
          • Local Install
          • Genesis Contract
          • Server Config
          • CLI Commands
          • Key Management
        • Run a Validator
          • Validator FAQ
        • Smart Contract Deployment Permissioning
        • Deploying Contracts
          • Remix
          • Truffle
          • Hardhat
          • Replit
    • Gauss Explorer
      • Features
      • Navigating the Explorer
        • Menus
        • Blocks
        • Transactions
      • Verifying a Smart Contract
        • Hardhat Plugin
        • Sourcify Plugin
        • OpenZeppelin Plugin
      • Interacting With Smart Contracts
      • Exporting Transactions
      • FAQ
      • For Developers
        • Gauss Explorer Dependencies
        • Deployment Guide
          • Smart Contract Verification
          • Cleaning an instance from the previous deployment
          • ENV Variables
          • Testing
        • APIs
          • Requests & Limits
          • GraphQL
          • ETH RPC
    • Noble Swap
      • Liquidity Boost Program
    • Tokens
    • Gauss NFTs
      • Ferro Cards
      • F.E.R.R.E.T. NFTs
    • Contests & Giveaways
    • Gauss Faucet
      • For Developers
    • Address List
  • 💡Additional Resources
    • Partnerships & Affiliates
    • Discord Channel
    • Contact Us
    • Learning Materials
      • Web3 Glossary
    • Media Kit
Powered by GitBook
On this page
  1. Getting Started
  2. Whitepaper
  3. Token Economics

Reflections: Rewarding the Gauss Community

PreviousToken Locking ScheduleNextCharitable Allocations: Grants, Scholarships, & Financial Assistance

Last updated 2 years ago

Many Web 3.0 projects use reflection (redistribution) mechanisms in their token economics. They are used almost exclusively for promotional reasons. Similarly, a number of projects use hyperinflation and token burning to generate hype. Gauss will incorporate a reflection system for several reasons. The first – and most important – is to reward our community as it grows. The second reason is to explore the reflection function and study the way it influences behavior in a live ecosystem. After two years, we will aggregate the data from observing the reflection mechanism and publish a paper to share our findings. Reflection minimizes volatility by incentivizing members of the Gauss Ecosystem to maintain a balance of GANG. The system places a higher weighted value for smaller holders, encouraging more people to participate in the ecosystem. To accomplish this, the reflection pool (r) is split into two parts and distributed based on individual holders’ wallet balances (x). This happens multiple times per day. One part of the reflection pool is disbursed directly proportional to x, relative to its portion of all x (c). The rest of the pool is dispersed based on the square of each wallet (y), relative to its portion of all y (s).

To illustrate, imagine an apple pie. Let’s say the pie has ten slices, and there are nine people at the table. Each person gets a slice – this represents their wallet. The remaining slice is the reflection pool. Each person’s slice of pie (x) is an arbitrarily different size, but taken together they would still represent nine of the ten slices (c). The tenth slice is cut in half. The first half is handed out according to how large each person’s first slice is; (x/c)*0.5r. The second half is distributed based on the square of each person’s first slice, adding more ‘weight’ to smaller slices; (y/s)*0.5r. We want to distribute the tenth slice (r) in a manner that provides a bit more pie to each person who has a smaller slice than they would receive if it were split proportionally to the size of their first slice. This way, when a new person joins the Gauss Ecosystem, they are incentivized with reflections even though they may not have significant holdings. Rewards are distributed more evenly, rather than simply accruing to whoever has the largest wallet.

🌐