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

Optional Extensions

PreviousRewards & SettlementNextKey Takeaways

Last updated 7 days ago

Hubic supports several modular extensions that enhance its usability in complex, privacy-sensitive, or DAO-regulated environments.

These are optional features that sit on top of the core zkML + economic pipeline and can be programmatically enabled via smart contracts.

🔐 1. Private Inference

For enterprise or regulated data workloads, Hubic supports confidential inference workflows:

  • Encrypted inputs/outputs stored via IPFS or Arweave.

  • zk-proofs still generated — but output hashes can be masked or gated.

  • Fully verifiable by DAO or regulatory contracts with privileged access.

Use case: Insurance firms, private credit scoring, proprietary model deployments.

📦 2. Batch & Subscription Jobs

Enable users or applications to prepay for multiple inference tasks in bulk:

  • Reduce per-call gas fees via aggregation.

  • Useful for high-frequency protocols (trading bots, validators, off-chain oracles).

  • Scheduled or interval-based batch execution.

Use case: L2 zk-Rollup verifications, DeFi rebalancing strategies.

🏛 3. DAO-Gated Inference

Only DAO-approved users or contracts may access specific models:

  • DAO can control who uses an inference pipeline.

  • Access NFTs or DAO whitelist gating mechanisms supported.

  • Voting can dynamically enable/disable model usage.

Use case: DAO-controlled RWA credit models or governance advisory bots.

🌍 RWA Enhancements:

Feature
Value for RWA Ecosystem

Gated Model Access

RWA products with regulated licensing or usage quotas

Private Revenue Tracing

Masked but auditable earnings streams

Prepaid Access Passes

RWA token-based API licensing or utility access

These extensions turn Hubic from a protocol into a platform — giving DAOs, enterprises, and tokenized asset managers programmable control over how AI is used, monetized, and governed.