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. Program Flow Overview

Rewards & Settlement

PreviousVerification PhaseNextOptional Extensions

Last updated 6 days ago

Once an inference is successfully verified on-chain, the Settlement Contract is triggered. It performs deterministic, on-chain payment distribution to all involved parties — model owner, executor, and verifier — using the original inference fee submitted by the user.

This step guarantees that only cryptographically proven computation is paid, forming the economic foundation of both Hubic and any tokenized RWA model.

💰 Default Distribution Breakdown (Per Inference):

Role
Share
Notes

Model Owner

60%

Can be a wallet or RWA token contract

Executor

20%

Paid for zk-inference and proof generation

Verifier

20%

Paid for validating the zk-proof on Ethereum

⚙️ Settlement Logic Flow:

  1. Verifier contract emits a VerifiedInference event.

  2. Settlement contract reads the associated payment data from the original request.

  3. It distributes the HUB (or USDC/ETH if multi-token enabled) to:

    • Registered model owner address

    • Executor wallet

    • Verifier node

  4. Emits InferenceSettled log with all payment receipts.

🧾 Example Payout (Job = 100 HUB):

  • 60 HUB → model owner (or RWA smart contract)

  • 20 HUB → executor

  • 20 HUB → verifier

All payments are atomic and final.

⛓ On-Chain Record:

Every settlement is stored immutably and indexed by:

  • request_id

  • model_hash

  • payer

  • timestamp

  • payout recipients + values

This ensures compatibility with reputation scoring, DAO transparency, and RWA audit/reporting layers.

🌍 RWA Integration:

  • Auto-Streaming to RWA Holders: Model owners can register an ERC-20 or ERC-721 payout contract that distributes revenue to token holders (e.g. via Superfluid or streaming vaults).

  • Performance-Linked Yield: RWA dashboards can show real-time yield generated by model usage and task volume.

  • Composable Revenue Sharing: Smart contracts can split model owner fees across DAOs, LPs, dev teams, or token holders.

Settlement turns AI into an income-generating asset — where math, not trust, guarantees payment.