Hubic.ai
  • Hubic AI
  • EMBARK UPON
    • Introduction
      • Proof-of-Inference (PoI)
      • Proof-of-Weights (PoWg)
      • Why Hubic?
      • Main Actors and Their Roles
      • Architecture Overview
      • Use Case Examples
      • Hubic AI Hub – Model Registry
      • RWA Integration
    • Registry & System Architecture
      • Sovereign AI Agents (On-chain AI Logic Executors)
      • Liquid Strategy Engine (LSE)
      • Proof-of-Weights (PoW2)
      • Governance System
      • Hubic Intelligence Hub (Expanded)
      • Visual System Map
    • Economic Model
      • HUB Token Utility
      • Economic Actors & Reward Mechanics
      • Token Flow Diagram
      • Long-Term Sustainability
      • Optional Enterprise Layer
      • Security & Reputation Systems
      • Summary Table
      • Future Expansion Points
      • Final Notes
    • Program Flow Overview
      • Model Registration (One-Time)
      • Inference Request (User Job)
      • Execution Phase (Off-Chain)
      • Verification Phase
      • Rewards & Settlement
      • Optional Extensions
      • Key Takeaways
    • Real-World Use Case Example
      • Introduction
      • Problem Statement
      • System Actors
      • End-to-End Flow: DAO Delegation Automation
      • Benefits to DAO Operations
      • Extensions & Advanced Use
  • Hubic Economic Engine
    • Tokenomics
    • Roadmap
  • Links
    • Website
    • Twitter
    • Telegram
    • GitHub
Powered by GitBook
On this page
  1. EMBARK UPON
  2. Economic Model

Economic Actors & Reward Mechanics

PreviousHUB Token UtilityNextToken Flow Diagram

Last updated 7 days ago

Hubic’s decentralized economy is structured around three primary roles, each contributing to the zk-compute pipeline and earning HUB based on verified outputs:

👤 1. Model Owners

Role: Register zk-compatible AI models to the on-chain registry. They define pricing and receive a share of all inference fees generated by their models.

💸 Revenue Model:

  • Set a flat or dynamic price per inference call.

  • Earn a default 60% share of every valid task using their model.

  • Can tokenize model ownership as ERC-20/NFT to distribute income.

🌍 RWA Integration:

  • Tokenized ownership: Revenue is streamed to token holders.

  • DAO-managed models: Governance over fee structure, model updates, and upgrade rights.

⚙️ 2. Executors (zk-Inference Nodes)

Role: Run the model’s zk-circuit off-chain and generate a proof.

🧾 Participation Requirements:

  • Stake HUB to enter execution pools.

  • Meet proof latency and compactness constraints.

💰 Compensation:

  • Earn 20% of inference fee per job.

  • Bonus tiers for proof efficiency, model diversity, and low error rates.

📈 Enhancements:

  • Performance history boosts future routing priority.

  • zk-signed benchmarks can be published for discoverability.

✅ 3. Verifiers (Validation Nodes / Contracts)

Role: Confirm the integrity of each proof and enforce correctness.

🔍 Responsibilities:

  • Load model hash and verification key from the registry.

  • Match proof → input → model → output.

  • Trigger payment or slashing.

💰 Rewards:

  • Receive 20% of inference fee per successful verification.

  • Long-term bonuses based on uptime and audit performance.

⚠️ Slashing Conditions:

Misbehavior
Penalty Applied

Accepting invalid proof

Slashing of staked HUB

Collusion with executor

Slash + blacklisting

Missed validation SLA

Loss of role + reward cut

⚖️ Revenue Split Summary (Per Inference Job):

Actor
Share (%)
Paid In
Notes

Model Owner

60%

HUB

Can be auto-routed to RWA holders

Executor Node

20%

HUB

zk-proof generation

Verifier Node

20%

HUB

On-chain proof validation

This system ensures that all compute work, validation, and model ownership is financially accountable, proof-enforced, and natively composable with RWA tokens and Ethereum protocols.