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

Program Flow Overview

PreviousFinal NotesNextModel Registration (One-Time)

Last updated 6 days ago

This section describes the complete lifecycle of an AI inference within the Hubic Protocol — from model registration to zk-proof execution, verification, and reward distribution — all coordinated by Ethereum smart contracts.

This modular pipeline ensures:

  • Fully verifiable execution logic (via zk-proofs)

  • Transparent, slashing-secured task delegation

  • Native support for RWA tokenization and revenue distribution

🧬 Core Flow Diagram:

scssCopyEdit[Model Dev] → zkRegistry → [User Input] → Inference Request
     ↓                               ↓
[Executor Node] — zk-Proof —> Verifier Contract (Ethereum)
     ↓                               ↓
[Settlement Contract] → Rewards + Logs
     ↓
[RWA Smart Contracts] → Tokenized Yield Flow (optional)

🔗 Components Covered:

  1. Model Registration (One-Time): Upload and register zk-compatible models.

  2. Inference Request (User Job): Users trigger tasks using registered models.

  3. Execution Phase (Off-Chain): Executor runs circuit and generates zk-proof.

  4. Verification Phase: Proof is validated on-chain.

  5. Rewards & Settlement: Payment distribution via Ethereum smart contracts.

  6. Optional Extensions: Private inference, batch jobs, DAO gating.

  7. Key Takeaways: Summary of verifiability, automation, and RWA alignment.