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

Market Thickness

PreviousCommunity MembersNextInitial Distribution Protocol

Last updated 1 year ago

To get the market thickness required, there needs to be a certain number of committed customers. However, for customers to commit, they need to be assured that there are a suitable number of high-quality feed providers providing data, and enough node runners to secure the system. Therefore, Metaoracle needs to consider how early adopters in the node runner and feed provider space will be incentivized.

Another key aspect to consider is that the number of node runners and feed providers servicing the system should inherently grow as the number of customers and uses grows, and this should be an automated process.

🧑‍🏫
💠