geeblock
  • Gee block
    • Summary
      • Problem Recognition and Solution
      • Technical Highlights
      • Impact on the Blockchain Industry
      • Ecosystem Evolution and Roadmap
      • Role of $GEE in the Network
      • Expectations for Network Value Growth
    • Market Challenge
      • Scalability Limitations
      • Fee burden
      • Lack of Real-World Applications
      • Security Concerns and Data Privacy
    • Attempts
      • Ethereum with Layer 2 Solutions
      • Solana’s High-Throughput Approach
      • Polkadot’s Interoperable Parachains
    • Gee Solution
      • Goals and Principles
      • Key Structural Properties
      • Overview of Document Structure
      • Nomenclature and System Identity
    • Page
    • Consensus mechanism
      • Background: Rethinking Consensus for Decentralized Systems
      • Gee Consensus: A Hybrid Model for Scalability and Security
      • How Gee Consensus Works
      • Ensuring Consistency and Security
      • Benefits of the Gee Consensus Engine
    • Triple-chain architecture
      • Contract Chain (C-Chain)
      • Platform Chain (P-Chain)
      • Resource Chain (X-Chain)
      • Gee L1
      • Key Advantages of Gee L1
      • Creating Gee L1
      • Compensation Model
      • Key Network Parameters
      • Delegation and Validator Weight Limitations
    • Virtual machine s1
      • What is a Virtual Machine in Blockchain?
      • Why Use a VM on Gee?
      • How Do VMs Work in Gee?
      • Types of VMs in the Gee Primary Network
      • VM Development on Gee: Key Technologies and Compatibility
    • Virtual machine s2
      • Smart Contract Platform
      • Benefits for Developers
      • Benefits for Users and Businesses
      • Expanding the Gee Ecosystem and Industry-Specific Applications
    • Bootstrapping
      • Step 1: Connecting to Seed Anchors
      • Step 2: Network and State Discovery
      • Step 3: Becoming a Validator
    • Roadmap
      • Initial Phase (2024-2025)
      • Expansion Phase (2026-2027)
      • Long-Term Vision (2028+)
    • $GEE
      • Core Utility of $GEE
      • Issuance and Distribution of $GEE
      • Incentive and Reward Structures
      • Foundation Policies on $GEE Management
      • Additional $GEE Operational Policies
      • Long-Term Vision and Sustainability
    • Expectiation for network value growth
      • Expansion of the Core Ecosystem
      • Development and Attraction of High-Value Applications
      • Expansion of Strategic Alliances and Partnerships
      • Strengthening and Supporting the Community
      • Additional Activities to Promote Sustainable Growth
      • Expectations for $GEE’s Long-Term Value Growth
    • Optimization and future growth
      • Optimization Issues
      • Future Growth Challenges
      • Strategic Initiatives for Future-Proofing and Growth
    • Disclaimers
Powered by GitBook
On this page
  1. Gee block
  2. Triple-chain architecture

Delegation and Validator Weight Limitations

PreviousKey Network ParametersNextVirtual machine s1

Last updated 5 months ago

To maintain balance and fairness in the network, Gee enforces delegation limits:

· Validator Max Weight: Limits the maximum GEE that can be delegated to a validator, defined by:

· Max Validator Weight Factor is set to 5, allowing delegations up to five times the validator’s initial stake.

Setting MaxValidatorWeightFactor to 1 effectively disables delegation by equating Max Weight with the validator’s own stake.

Uptime Requirement

Validators must maintain an uptime of 80% or higher to qualify for rewards, ensuring network reliability and rewarding consistent participation.

The Gee Primary Network compensates validators based on their staked GEE, staking duration, and the network’s current supply status. Validators earn higher rewards by staking for longer periods, which aligns their incentives with network stability. Delegation weight limits and uptime requirements further reinforce network balance, making Gee’s staking model both rewarding and sustainable for active validators.