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. Registry & System Architecture

Proof-of-Weights (PoW2)

PreviousLiquid Strategy Engine (LSE)NextGovernance System

Last updated 6 days ago

PoW2 is Hubic’s decentralized reputation and scoring system β€” a mechanism that ensures inference nodes, AI agents and validators are evaluated fairly and verifiably. All scoring logic is encapsulated in zk-circuits and the results are submitted on-chain via Ethereum smart contracts.

This creates a zero-trust reputation layer, critical for routing tasks, adjusting payouts and powering RWA revenue models.


πŸ” Flow:

Validator or Scorer β†’ Local Evaluation via zk-circuit β†’ zk-Proof + Score β†’ Ethereum Verifier β†’ Reputation Update

πŸ“¦ WeightSubmission Struct:

struct WeightSubmission {
  address validator;
  bytes32 proof_hash;
  bytes32 scores_hash;
  bytes32 circuit_id;
  uint64 timestamp;
  string feedback_uri;
}

Each submission includes a zk-proof that the scoring circuit was executed correctly over a set of subjects (e.g., executors, models, agents).


πŸ” Security Benefits:

Feature
Description

zk-Proof of Scoring

Proves that logic was executed fairly β€” prevents copy/fraud.

Validator Binding

Ties logic to validator address, avoiding reused calculations.

Auditable Results

All scores can be externally verified by dApps or DAOs.


🌍 RWA Relevance:

β¦Ώ Score-Linked Revenue Distribution: Only high-performing models or agents (proven via zk-scoring) receive royalty shares.

β¦Ώ Yield Optimization: Investment DAOs can allocate capital to top-rated strategies or AI assets.

β¦Ώ Reputation-Drive Pricing: Higher reputation models may demand premium inference fees β€” creating market-based pricing for AI-based RWAs.

Scoring is no longer subjective β€” it’s verifiable, transparent and tied directly to income.


This makes PoW2 a key enforcement layer for any economic system where AI models or agents act as tokenized revenue engines. Without PoW2, the RWA yield pipeline would lack accountability.