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

HUB Token Utility

PreviousEconomic ModelNextEconomic Actors & Reward Mechanics

Last updated 6 days ago

The HUB token is the backbone of economic coordination in the Hubic ecosystem. It powers every layer of the protocol — from compute and validation, to governance and revenue flows.


🔧 Primary Utility Domains:

Function
Mechanism

Inference Payments

Users pay in HUB or stablecoins (e.g. USDC); HUB gives discounts & priority

Validator/Executor Staking

Required stake to participate in task routing and proof generation

Performance-Based Rewards

Earn HUB based on uptime, accuracy, proof efficiency

Governance Rights

Vote on model inclusion, fee changes, RWA token settings, protocol upgrades

Premium Tiers / Subscriptions

Lock HUB for access to enterprise-grade throughput or APIs


🧠 RWA Context:

  • Tokenized Models & Agents: Can issue ERC-20s representing future yield. HUB is used to claim these yields or stake against their performance.

  • Collateral Layer: DAOs or institutional users may stake HUB to access or insure high-value RWA agents.

  • Programmable Revenue Distribution: Smart contracts auto-route HUB to token holders tied to usage proofs.

HUB is the native unit of value, trust, and access in a world where compute = cashflow.


🔹 Reward Mechanics

Hubic rewards three key roles: Model Owners, Executors, and Validators. Rewards are distributed per inference job, based on a zk-verified outcome.


💸 Standard Distribution (Per Inference Fee):

Recipient
Role
Share

Model Owner

Supplies the zk-model

60%

Executor

Runs inference + proof

20%

Verifier Node

Validates proof

20%


🧮 Example:

A user submits a job and pays 100 HUB.

→ 60 HUB → to model owner (or RWA token smart contract) → 20 HUB → to executor who performed zk-inference → 20 HUB → to verifier who validated the result on-chain


📈 Incentive Enhancements:

  • Reputation Bonuses: High-performing nodes earn HUB multipliers based on zk-verified score history.

  • Slash Conditions: Faulty proof submission = slashing of staked HUB.

  • Dynamic Fee Modifiers: Based on demand, reputation, and model performance metrics.


🌍 RWA Integration:

  • Tokenized Model Ownership: Revenue from the 60% model owner fee can be split among RWA token holders automatically.

  • Governable Fee Allocation: DAOs can propose and vote on changing model fees, reward splits, or adding dynamic fee logic.

  • Proof-Based ROI Tracking: RWA dashboards can track yield in real-time using verified inference logs.