Anyone Docs
  • 🔷The Documentation For Anyone
    • About
    • FAQ
  • 🔷Relay Setup
    • Get Started
    • Installation and Usage
      • Setting Your Environment
        • Virtualization on Windows
        • Virtualization on macOS
        • Install Ubuntu Server 22.04
        • Server management with SSH in Windows and macOS
      • Install Anon on Linux
      • Install Anon using the apt repository
      • Update Anon and accept terms and conditions
      • Install Anon in Docker
      • Configure SOCKS5 Proxy for Anyone
      • Install Anyone Exit Relay
    • Troubleshooting Common Issues
      • Diagnosing CGNAT and Public IPv4
      • Confirm ORPort Reachability
    • Firewall and Network Configurations
      • Router Port Forwarding
      • Install and Configure Firewall
    • Advanced Configuration and Troubleshooting
      • Configure IPv4 and IPv6
      • DoS mitigation parameters
    • Relay Operator Standards
    • Exit Relay Guidelines
  • 🔷Hardware Setup
    • Setup Guide
    • Description and Specifications
    • Relay Control Panel
      • Home
      • Network Settings
      • Relay Settings
      • Relay Family
      • Proxy Settings BETA
      • Change Password
      • Logs
      • Update
    • Update (Using USB)
    • Update to WEB 3.2.0 (Using UI)
    • Troubleshooting and additional configuration
      • Router Port Forwarding
      • Diagnosing CGNAT and Public IPv4
    • Router Setup
  • 🔷Security and Privacy
    • VPS Hardening
  • 🔷Rewards Dashboard
    • Registering to the Rewards Program
    • Accessing the Rewards Dashboard
    • Using the Rewards Dashboard
    • Rewards Status
  • 🔷Anyone SDK
    • NPM SDK
      • Install NPM Package
      • Run as Library
        • Anon
        • AnonSocksClient
        • AnonControlClient
      • Run from CLI
      • Tutorials
        • Hello Anon World I
        • Hello Anon World II
        • Circuit Control I
        • Circuit Control II
    • Native SDK
      • Anyone Client Releases
      • MAN - Anon Manual
      • Tutorials
        • Anyone Services I
        • Anyone Services II
    • iOS SDK [Beta]
      • Manual Install - CocoaPods
  • 🔷Connect to Anyone
    • Connecting to Linux
      • [Beta] One-Click Linux Setup
    • Connecting to macOS
      • macOS with NPM
      • [Beta] One-Click macOS Setup
    • Connecting to Windows
      • [Beta] One-Click Windows Setup
    • Individual Applications with Anyone
    • Connect Through Hardware
  • 🔷Tokenomics
    • Introduction
    • Token Distribution
      • Token Outflow
      • Other Tokens
    • Relay Rewards
      • Lock Requirement
      • Lock Adjustments
      • Reward Multipliers
    • Additional Roles
      • Authorities and Staking
      • Governance Voting
    • Premium Circuits
      • Premium Circuits
      • Premium Circuits: Metrics
    • Summary
      • Value Accrual Summary
      • Rewards Case Study
    • Appendix
      • M Derivation
      • Risk Equation Derivation
  • 🔷Resources
    • Community and Customer Support
    • Links
    • Token
    • Whitepaper
    • Roadmap
    • API
      • REST
      • [Future] GraphQL
Powered by GitBook
On this page

Was this helpful?

  1. Tokenomics
  2. Token Distribution

Token Outflow

Central to the Anyone ecosystem is the distribution layer that uses $ANYONE as an incentive for relays contributing their bandwidth and computing power. To bootstrap the network, a base-reward pool of 10,000,000 tokens (10% of the total supply) is allocated to a reward pool that pays tokens out perpetually. The pool is perpetual because only a fixed percentage of the remaining tokens will be distributed each period.

The pool operates on an epoch basis, where each epoch has a fixed number of rewards per day. In turn, the epoch reward is always determined by the outstanding number of tokens in the reward pool. For example:

  1. The pool starts with 10,000,000 tokens.

  2. The epoch daily reward is set at 0.100% of the pool’s tokens. This means that each day, for the first epoch, the pool will distribute 10,000 tokens.

  3. The epoch duration is 15 days, so on day 15, 150,000 tokens have been distributed.

  4. Epoch Two starts. The tokens in the pool are now 9,850,000. The Epoch reward is still 0.100%. This works out to 9,850 tokens per day for the next 15 days.

The 0.100% number is picked as targeting an annual inflation rate of circulating supply of around 3.5% in the first year and gradually reducing it from there on. This gives the pool a half-life (the time it takes for 50% of the remaining tokens in the pool to be depleted) of 693 days or 46 epochs.

Token Allocation

A key change to the reward tokenomics is the division of the reward pool into three: relay rewards, hardware rewards and validator/staking rewards, in the following ratio:

70% of reward pool (7,000,000 tokens) for all relays 20% of reward pool (2,000,000 tokens) for designated hardware relays 10% of reward pool (1,000,000 tokens) for authority roles

The first two reward pools will go live at the same time, at the commencement of autonomous mainnet rewards. Once the network begins to decentralize, with the ability for holders to run bandwidth authorities, the authority pool will begin to emit to those operators and their delegated stakers.

The authority role pool will emit with the decentralization of those roles and introduction of delegated staking. When emitted, all pools will emit with the same logic (0.100% of the pool quantity emitted daily).

Bootstrapping these pools with the 10% of supply allows the network and applications built on top of it to scale and gain users. The relatively low costs of operating relays compared to other mining allows the emission rate to remain low. Nevertheless, the incentive system is built to accommodate a more circulatory ecosystem, with pools boosted by incoming revenue, as explained in future chapters.

PreviousToken DistributionNextOther Tokens

Last updated 8 months ago

Was this helpful?

🔷