GEB Docs
  • Quick Start
  • GEB Consensus
    • Mother Consensus
    • Sub Consensus(Agere)
  • Learn
    • BitAgere Guide
      • Auditor Reference Concepts
      • Executor Reference Concepts
  • Build
    • Validator
      • Wasm Operation
      • L-BTC Validator Operation
    • BitAgere
      • RelayAgere
      • Agere Auditor
      • Agere Executor
  • Use
    • Wasm Wallet
    • Earn $GEB
      • Stake L-BTC
        • What is L-BTC?
        • Download and Run LND Desk
        • Config LND
        • Node Asset Management
          • Open Channel(Get L-BTC)
          • L-BTC ⇌ BTC (on GEB chain)
        • Stake L-BTC Earn $GEB
      • Stake GEB on Agere
    • Earn $BTC
      • Claim and Other Operations
      • Transfer BTC to EVM
    • Bridge
      • Official Bridge
        • BEVM Mainnet
        • BEVM Canary
      • Third-Party Bridge
        • BEVM Mainnet
          • Swap from EVM to BEVM Mainnet
        • BEVM Canary
          • Swap from EVM to BEVM Canary
          • Other assets
            • Bridge PCX from BEVM Canary to Chainx
      • Transfer(EVM<-->Wasm)
  • EVM Development
    • Fee Calculation
      • GEB Mainnet
      • BEVM Canary
    • Smart Contract
      • Write a Contract
        • Set Up the Metamask Configuration
        • Deploy Smart Contract on GEB Signet
        • Deploy Smart Contract on BEVM Canary
      • Foundry
        • Deploy and verify contract by Foundry
      • Contract Verification (BlockScout)
      • ThirdWeb
    • Integrations
      • Oracle
        • Supra
        • DIA
      • Indexer
        • SubQuery
      • Account Abstraction
        • Particle Network
    • Libraries
      • ethereum-list/chains
      • Wagmi
      • Multicall3
    • Canonical contracts
    • Finality
  • Tokenomics
  • The Journy of GEB
  • Audit Reports
  • Community
Powered by GitBook
On this page
  • Creation and Basic Rules
  • Role Division Within Agere Particpants
  • Internal Elimination Rules
  • Agere Registration Restrictions
  • Incentive Mechanism
  • Reward Distribution Process
  1. Build

BitAgere

The BitAgere network introduces an innovative agere governance system that balances decentralization with efficient management through clearly defined roles, rules, and reward mechanisms. Let's examine how this system operates in detail.

Creation and Basic Rules

  • Creator Role: The agere creator (Owner) is responsible for setting objectives, establishing governance rules, and providing necessary technical resources (such as running programs, code repositories, and technical documentation).

  • Immunity Period: Newly registered ageres enjoy a 7-day protection period during which they are immune from elimination.

  • Elimination Rules:

    • Agere total is limited to 64, when a new agere registers, the lowest-scoring agere will be deregistered.

    • If multiple ageres tie for the lowest score, the earliest registered agere will be deregistered.

Role Division Within Agere Particpants

  • Auditors:

    • Auditors are responsible for scoring agere operations, with a maximum capacity of 64.

    • Auditors are selected through stake-based ranking;

    • Auditors falling out of the top 64 in stake will be eliminated.

    • Eliminated auditors can continue participating as executors.

    • Auditors must register as delegate representatives to accept user stakes.

  • Executors:

    • Executors provide computational resources and other contributions, serving as the agere's execution entities.

    • New executors enjoy a 7-day protection period, ensuring they won't be immediately eliminated.

Internal Elimination Rules

Agere participants are eliminated through pruning scores, which are positively correlated with received incentives - lower incentives result in lower scores. The process identifies participants with the lowest pruning scores outside the protection period for elimination. In case of tied lowest scores, the earliest registered participant is eliminated. If all participants are in the immunity period, the immune participant with the lowest pruning score is eliminated. In case of tied lowest scores among immune participants, the earliest registered immune participant is eliminated. If registration times are also tied, the immune participant with the lower ID is eliminated.

Agere Registration Restrictions

Agere Quantity Limits:

  • BitAgere network supports a maximum of 64 ageres.

  • When the agere limit is reached, newly registered ageres will replace the lowest-scoring agere.

Participant Limits:

  • Each agere allows a maximum of 256 participants.

Registration Requirements:

  • Agere registrants must provide detailed operational objectives, rule explanations, and necessary technical resources.

  • Auditors must complete required staking.

Incentive Mechanism

Reward Model

  • Agere Creator Rewards: Directly receives a fixed proportion of agere rewards

  • Auditor Rewards: Auditors receive rewards based on how closely their scoring aligns with network consensus.

  • Executors Rewards: Executors' rewards are directly affected by their task completion quality and auditor scoring.

Reward Distribution Process

  1. Weight Upload:

    • Each auditor maintains a weight vector representing their evaluation of all operators' performance.

    • Auditors periodically upload weight vectors to the chain (every 100 blocks).

  2. Weight Matrix Formation:

    • System integrates all auditor scoring vectors to generate a network-wide weight matrix used for reward calculations.

  3. Reward Calculation:

    • System calculates each participant's reward proportion by combining weight matrix and stake amounts.

    • Reward distribution cycle (Tempo) completes every 360 blocks.

  4. Reward Distribution:

    • Rewards are automatically distributed on-chain, directly injected into participants' stakes, requiring manual collection via wallet.

    • If there are regular stakers, remaining rewards after auditor portions are redistributed based on stake ratios.

PreviousL-BTC Validator OperationNextRelayAgere

Last updated 2 months ago