Hemera Doc
  • 👋Welcome
    • Introduction
    • Quick Start
    • Account Centric Indexing Protocol
      • What is Account-Centric Indexing?
      • Why "account-centric" indexing?
      • The advantages of Account-Centric Indexing
      • What's next for account-centric indexing?
      • Why create a new protocol here?
      • The Hemera Network
        • Network Roles
        • Indexers
        • Validators
        • Proprietary models & knowledge
        • Proprietary data and labels
        • Smart Contracts
        • Key roadmap items
        • Supported blockchains
      • Example Hemera use cases
        • SocialScan Explorers
        • Anti-sybil UML algorithm
        • Ethereum long term DA
        • EVM chain history preservation
        • Ecosystem AI Agents
        • User-defined AI Agents
  • 👩‍💻Developer Resources
    • Smart Contract Developers
    • EVM-compatible chains
      • Blockchain explorers
      • SocialScan explorer API doc
      • Ecosystem AI Agents
    • Dapp developers
    • User-defined Agent creators
    • AVS Operator
  • 🖥️Hemera Indexer
    • Introduction
    • Installation
      • Prerequisites
      • Install & Run
      • Export Result
    • Configurations
    • Benchmark
    • Data Class
      • Raw Data Tables
        • Blocks
        • Transactions
        • Logs
        • Traces
      • Generated Tables
        • Contract Internal Transactions
        • ERC20 Token Transfers
        • Tokens
        • ERC20 Token Holders
        • ERC721 Token Transfers
        • ERC721 Token Holders
        • ERC1155 Token Transfers
        • ERC1155 Token Holders
        • Address Coin Balances
        • Address Token Balances
        • Address Current Token Balances
        • Daily Wallet Address Stats
        • Contracts
      • Other Tables
        • Inscriptions
        • Bridges
          • L1 to L2 Transactions
          • L2 to L1 Transactions
          • Optimistic Rollup Data Availability Batches
          • Optimistic Rollup State Batches
    • Use Cases
      • UniSwap V3
        • Data Class
        • Trigger and Function
        • Run & Query
      • ENS
        • Data Class
        • Trigger and Function
        • Run & Query
      • OpenSea
        • Data Class
        • Trigger and Function
        • Run & Query
      • Deposit to L2
        • Data Class
        • Trigger and Function
        • Run & Query
      • User Profile
  • UDFs - User Defined Functions
    • Introduction
    • Components of UDFs
    • Building User Defined Functions(UDF)
    • Testing and Running UDF
    • Troubleshooting and Support
    • Supported UDFs
    • FAQs
  • 😄About us
    • The story behind building Hemera
    • Partners & Backers
    • Partnership inquiries
    • Hemera Powered Explorers
    • Active Developer Hackathons
    • Developer Contribution
  • Documentation feedback
Powered by GitBook
On this page
  1. Welcome
  2. Account Centric Indexing Protocol
  3. The Hemera Network

Indexers

Indexers are the foundational node operators providing account-centric indexing capabilities to the network. Indexers earn $DAY token rewards in the following ways:

  1. Data accessibility: indexers keep the indexed data available to requests at all time, and as such earn rewards for maintaining accessibility given SLA requirements. To join the network as indexers, $DAY tokens are staked to secure the network, and subject to slashing if serving malicious or incorrect data to applications, or if SLA conditions aren't met.

  2. Query rewards: by serving queries requests from validators, indexers earn token rewards for the work.

  3. Indexing bonus: network consumers create demands for sought-after data sets, indexers earn one-time bonus for providing indexing services to meet such demands.

Indexers play a crucial role in providing data accessibility within the account-centric indexing network. Their evolution occurs in three phases, with later stages offering more fine-grained indexing capabilities to address needs of network consumers.

In the first phase of the Hemera network, indexers will assist in establishing data coverage for prominent chains that are in demand by consumers. They will be allocated indexing tasks based on geographically locations and network latency to ensure that Hemera can provide global network coverage and data accessibility.

In future phases of indexer releases, indexer operators can configure the node to:

1. optimize indexing earnings by assigning tasks based on network demands;

2. configure wallets-of-interests and chains to cover, catering to Dapp developers who prioritize their own data needs over earnings.

PreviousNetwork RolesNextValidators

Last updated 6 months ago

👋