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

Proprietary models & knowledge

AI scientists and domain experts can contribute to Hemera Network through attributable proprietary models and knowledges

Proprietary models & knowledge are artifacts that generate on-chain intelligence for the Hemera network consumers. They are intellectual properties (IPs) in the form of machine learning algorithms, AI models, heuristic rules, or domain expertise in general that serves a certain intelligence needs. These IPs are closed source, encrypted, and operated within a trusted execution environment (TEE). Ownership is attributed to contributors' designated wallet addresses for collecting token rewards. Contributors earn rewards in the following form:

  1. One-time bounty rewards: for each interested problem or issues raised by the Hemera community, a one-time incentive in the form of $DAY tokens is provided to incentivize the research and development of proprietary models and knowledge. Initially, incentives are likely to be provided from the Hemera treasury in a form similar to ecosystem grants. As the network matures, incentives may also come from the wider Web3 community. This could involve community members proposing interesting problems to be solved by the Hemera community, with rewards offered for successfully addressing these challenges.

  2. Continued usage revenue share: each artifact on Hemera protocol are paid to use, as such accumulating revenues in the form of $DAY tokens. Owners of the artifacts earn a predefined percentage of the tokens.

See below artifacts examples built on top of the Hemera protocol.

User-defined AI agents:

Using tools provided by SocialScan Agent Store, individual traders can define and customize agents that showcase their proprietary asset tracking and trading strategies. End users can pay $DAY tokens to access these agents. The agent creator can earn the $DAY tokens paid by users, with a small hairbut charged by the Hemera treasury to compensate indexers and validators for providing data access.

PreviousValidatorsNextProprietary data and labels
👋