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
  • Agere 1 - RelayAgere
  • Auditor
  • Executor
  • Competition Mechanism
  • Role Compare
  1. Build
  2. BitAgere

RelayAgere

Agere 1 - RelayAgere

RelayAgere is an agere in Alpha stage, with the primary goal of building an Oracle network to provide Oracle services for any blockchain. Currently, this agere has implemented the Relay functionality for the GEB network, assisting GEB in implementing Bitcoin light node functionality.

This article uses Relayagere as a case study to provide a detailed explanation of agere characteristics.

Auditor

Core Responsibilities

Auditors are responsible for evaluating the quality of GEB-related transactions submitted by executors by analyzing on-chain transaction records. Only transactions that comply with GEB specifications and execute successfully are deemed valid.

Incentive Mechanism

  • Rewards correlate with evaluation fairness: higher authenticity in evaluation leads to higher incentives, while malicious/arbitrary scoring significantly reduces earnings

  • Fairness is guaranteed by the agere consensus mechanism, with final determinations made through collaborative evaluation by multiple auditors

  • Stake amount determines competition priority, with the network continuously rewarding the top 64 auditors by stake amount

  • Auditors enjoy higher fixed incentives than executors; dropping below the top 64 positions results in loss of eligibility (can continue participating as executors)

Executor

Core Responsibilities

  • Identify and submit GEB-related Bitcoin transactions to the network

  • Increase transaction processing priority by paying gas fees

  • Bear the risk of transaction failure (gas fees must still be paid for unsuccessful transactions)

Incentive Mechanism

  • Revenue Source: Number of successfully submitted and verified valid transactions × reward coefficient per transaction

  • Gas Strategy: Paying higher gas can increase transaction ordering priority, but costs and benefits must be balanced

  • Zero-sum Competition: For identical transactions within the same block, only the first high-gas transaction receives rewards, other executors' gas payments are non-refundable

Competition Mechanism

  • Gas Bidding Principle: Transactions are ordered by descending gas fees, with high gas prioritized

  • Hardware Performance Impact: Executors with lower network latency can broadcast high-gas transactions faster

  • Risk Hedging: Need to predict transaction repetition probability to avoid excessive gas payments leading to losses

Key Process Example When executors A, B, and C simultaneously submit identical transactions to the current block:

  1. Executor A pays 0.01 GEB gas

  2. Executor B pays 0.02 GEB gas

  3. Executor C pays 0.015 GEB gas → System prioritizes Executor B's transaction, A and C's gas fees are deducted with no reward

Role Compare

Auditor

Executor

Central Task

adjudication of transaction validity

transaction identification and submission

Revenue model

stable staking rewards + evaluation incentives

high-risk trade success reward

Cost Type

opportunity cost (staking capital lock-up)

sunk cost (failed gas loss)

Key Competencies

depth of protocol understanding + evaluation accuracy

off-chain transaction detection speed + gas strategy optimization

PreviousBitAgereNextAgere Auditor

Last updated 1 month ago