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
  • Requirements
  • Delegated Locking
  • Lock Rationale and Goals

Was this helpful?

  1. Tokenomics
  2. Relay Rewards

Lock Requirement

Requirements

All relays, with the exception of the Anyone Router hardware, must lock tokens to register it’s relay fingerprint that registers for rewards.

Updated Requirements

  • Initial Staking Requirement: Operators must lock 100 $ANYONE tokens.

  • Lock-In Period: The tokens are locked for a minimum of 180 days and subsequently as long as the user still wishes to receive rewards.

  • Unstaking Period: Following the lock-in period, there is a 14-day unstaking period that users initiate when they wish to withdraw.

Note: Locking as a Network Requirement: The next set of Anyone client updates will see the relay lock requirement play a part in relay onboarding, creating a requirement for a relay to have a successful token lock to be used by clients. This allows the network stability created by the lock mechanism to extend to protect against adversaries who are not motivated by rewards.

Delegated Locking

To further lower the barrier to entry and encourage cooperation within the community, one token holder can lock $ANYONE on behalf of another user’s fingerprint. The user who locks is subject to the 180-day lock and 14-day unstaking period, but otherwise has full control over their tokens and is not at risk of slashing. Currently, there is no bonus for delegated locking, but a percentage upstream will be considered based on prevalence and user behaviour in testnet.

Lock Rationale and Goals

Scalability and Security: The adjustments to staking requirements and the delegated locking function aim to lower the barrier for new relay operators, promoting a more extensive and robust network. This strategy is intended to enhance the network's security and overall capacity by diversifying participation.

Incentive Alignment: The structured rewards and staking system are designed to align closely with operators' contributions to network health, encouraging high performance, reliability, and declaration of relay families.

Rationale for Lock-in and Unstaking Periods

  • Commitment to Network Integrity: The lock-in and unstaking periods, along with the reward structure, underscore the Anyone Network's commitment to long-term stability and operator investment in the ecosystem's success.

  • Network Stability and Reduced Volatility: By implementing a lock-in period and a structured unstaking process, the network ensures that it has a stable and committed base of relay operators. This stability is crucial for maintaining service reliability and network performance.

  • Minimizing Sudden Liquidity Shocks: The introduction of an unstaking period is strategically designed to prevent the immediate withdrawal of stakes, which could lead to sudden liquidity shocks in the network. This measured approach to unstaking ensures that the network can plan for and manage liquidity more effectively, avoiding potential disruptions that could arise from sudden large-scale withdrawals. This delay helps align the operators' financial incentives with the long-term health and success of the network.

PreviousRelay RewardsNextLock Adjustments

Last updated 8 months ago

Was this helpful?

🔷