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

Registry & System Architecture

PreviousRWA IntegrationNextSovereign AI Agents (On-chain AI Logic Executors)

Last updated 6 days ago

Hubic’s protocol architecture is centered on verifiable AI execution, designed to run seamlessly on Ethereum's smart contract layer and its modular scaling ecosystem (L2s, sidechains and storage layers).

At its core, the system links zk-model registries, proof verifiers, AI agents and payment logic into a trust-minimized, fully auditable flow — enabling the tokenization of AI as productive assets (RWAs).

🧱 Core Components:

Component
Description

zkRegistry

On-chain registry of zk-compatible models with usage metadata.

Agent Accounts

Smart-contract-controlled agents that execute logic based on zk-inference.

Proof Submission Layer

Off-chain submitters of zk-proofs tied to AI tasks.

Ethereum Verifier Contracts

Validate proofs, track outputs, trigger economic logic.

⚙️ Design Goals:

  • Ethereum-native: Built for Solidity + EVM, deployable on L1 and L2.

  • RWA-enabled: Every AI inference can become a yield event tied to tokenized assets.

  • Composable: Easily integrates with DeFi protocols, DAO tooling and RWA dashboards.

  • Transparent: Full auditability of execution, proof submission and payout history.

🔁 System Flow Summary:

User/DAO → zkRegistry → Inference Node → zk-Proof → Ethereum Verifier Contract → Logs + Rewards

Each module is designed to enforce zero-trust AI execution, ensuring that any downstream logic (governance, trading, licensing, staking) is backed by verified computation.