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

Why create a new protocol here?

TL;DR: A protocol brings the following fundamental benefits:

  1. Bootstrap network effects to maximize innovation

  2. Properly aligned interests

  3. Significantly reduce development & service costs for all developers.

A protocol brings the most value when more developers build on top of it, creating a network effect which benefits all network participants.

From a technical perspective, when considering on-chain data retrieval and the use cases built on top of it, many technical components can be standardized due to the uniform formats of underlying on-chain data. Therefore, it makes the most sense to create a protocol network that addresses these demands which also evolves over time, benefiting the entire ecosystem. Traditionally, building decentralized indexing protocol often involves performance compromises. However, Hemera Protocol's Account-Centric Indexing architecture makes it feasible to develop such a protocol without sacrificing performance.

From a business perspective, opting to make Hemera an open protocol presents the most logical choice for several reasons:

  1. Alignment of ecosystem interests: Hemera Protocol enables the support of valuable proprietary intellectual properties, mitigating the risks associated with Web2 models where enterprises monopolize these assets and profit solely from their corporate networks. This approach ensures that Hemera Protocol can maximize its value from inception。

  2. Significant cost reduction for all protocol users:

    • Reduce development costs: standardize the account-level data retrieval and provide it as a protocol, removing the needs for Dapp developers to build everything from scratch in house.

    • Reduce the service costs: the protocol distributes the cost-intensive indexing workload across the Hemera Network, which encompasses participants such as miners, developers, and individual users, ensuring computational coverage across all geographical locations.

PreviousWhat's next for account-centric indexing?NextThe Hemera Network

Last updated 8 months ago

👋