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

Token Flow Diagram

PreviousEconomic Actors & Reward MechanicsNextLong-Term Sustainability

Last updated 6 days ago

This section illustrates the economic pathway of the HUB token during a typical AI inference lifecycle. All payments, validations, and distributions are tightly coupled with zk-proof verification and on-chain enforcement.


🧭 Flow Summary (Per 100 HUB Job):

      [User / dApp]
            β”‚
   Pays 100 HUB for zk-Inference
            β–Ό
 β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
 β”‚   Inference Engine  β”‚
 β”‚   + zkProof Gen     β”‚
 β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
          β”‚
          β–Ό
 β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
 β”‚ Verifier Contract   β”‚
 β”‚ + Proof Validation  β”‚
 β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
          β”‚
          β–Ό
 β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
 β”‚     Settlement Contract (Ethereum)        β”‚
 β”‚  β€’ Logs output + proof                     β”‚
 β”‚  β€’ Distributes payment based on outcome    β”‚
 β””β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜
          β–Ό
 β”Œβ”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”¬β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”
 β”‚  Model     β”‚ Executor   β”‚ Verifier   β”‚
 β”‚  Owner     β”‚ Node       β”‚ Node       β”‚
 β”‚ (or RWA)   β”‚            β”‚            β”‚
 β”‚  60 HUB    β”‚  20 HUB    β”‚  20 HUB    β”‚
 β””β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”΄β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”€β”˜

πŸ”Ή Settlement Logic

All HUB token transfers are executed automatically by smart contracts once a zk-proof is validated on-chain. If the proof is invalid or incomplete, no payout occurs, and staked parties may be slashed.


πŸ”„ On-Chain Settlement Process:

  1. Verifier submits proof + validation metadata

  2. zkRegistry checks:

    • Is the model registered?

    • Does the proof match the model hash?

    • Was the inference properly routed?

  3. Settlement contract triggers payouts:

    • Funds are sent atomically from escrow.

    • Usage history is updated for scoring/royalty tracking.

    • Events emitted for dashboard / RWA sync.


⚠️ Failsafe Mechanisms:

Case
Outcome

Invalid proof

No payout, potential slashing

Delayed executor

Penalty applied or job reassigned

Unregistered model

Job rejected, refund issued to user


🌍 RWA Considerations:

  • Royalty Streams: Model owner payout can be redirected to RWA token contracts, distributing yield to token holders.

  • Auditability: Every inference and reward is linked to an event + zk-proof β†’ usable in dashboards, reporting, and compliance.

  • Trustless Execution: Because every payment is proof-gated, RWA structures inherit the same integrity guarantees.

Hubic transforms payment logic from β€œreputation-based” to β€œproof-enforced” β€” ideal for powering tokenized, revenue-yielding AI assets on Ethereum.