Metaoracle Whitepaper
  • ☄️Metaoracle
  • Overview
    • 🎯Our Vision
      • 1️⃣Design Considerations
    • 🧑‍🏫Market Design
      • 🌀Ecosystem Participants
        • 1️⃣Consumers
        • 2️⃣Feed Providers
        • 3️⃣Node Runners
        • 4️⃣Community Members
      • 💠Market Thickness
        • 1️⃣Initial Distribution Protocol
        • 2️⃣Partnerships
    • 🛠️Mechanism Design
    • 🗳️Governance
    • 🔰Protocol Design
    • 🛡️Protocol Security
    • 🔮Ease of Use
  • General Informaion
    • 🪙$METAO Tokenomics
    • 📈Return to Investment/Stake
    • ⚙️Architecture
    • 📝Legal disclaimer
    • 🔍Privacy policy
  • Our Socials
    • Website
    • Telegram
    • X Twitter
Powered by GitBook
On this page
  1. Overview
  2. Market Design

Ecosystem Participants

Ecosystem Participants - Metaoracle

PreviousMarket DesignNextConsumers

Last updated 1 year ago

To start, it's critical to comprehend the anticipated participants, as well as their potential actions and participation incentives. This will enable us to design the Metaoracle economy to encourage group actions that maximize the benefit for all participants.

Customers

These are the end users of Metaoracle. They would either be calling data feeds, or sending computations to the node network.

Feed Providers

Data providers are institutions that distribute data, or third parties that subscribe to an endpoint to deliver data.

Node Runners/Validators

Node Runners are the individuals who use their computing power to run Metaoracle’s node software.

Community Members

'Community members' is a broad definition, and can include anyone who holds even 100 MERAO tokens.

🧑‍🏫
🌀