Token Flow Diagram
Last updated
Last updated
This section illustrates the economic pathway of the HUB token during a typical AI inference lifecycle. All payments, validations, and distributions are tightly coupled with zk-proof verification and on-chain enforcement.
π§ Flow Summary (Per 100 HUB Job):
All HUB token transfers are executed automatically by smart contracts once a zk-proof is validated on-chain. If the proof is invalid or incomplete, no payout occurs, and staked parties may be slashed.
π On-Chain Settlement Process:
Verifier submits proof + validation metadata
zkRegistry checks:
Is the model registered?
Does the proof match the model hash?
Was the inference properly routed?
Settlement contract triggers payouts:
Funds are sent atomically from escrow.
Usage history is updated for scoring/royalty tracking.
Events emitted for dashboard / RWA sync.
β οΈ Failsafe Mechanisms:
Invalid proof
No payout, potential slashing
Delayed executor
Penalty applied or job reassigned
Unregistered model
Job rejected, refund issued to user
π RWA Considerations:
Royalty Streams: Model owner payout can be redirected to RWA token contracts, distributing yield to token holders.
Auditability: Every inference and reward is linked to an event + zk-proof β usable in dashboards, reporting, and compliance.
Trustless Execution: Because every payment is proof-gated, RWA structures inherit the same integrity guarantees.
Hubic transforms payment logic from βreputation-basedβ to βproof-enforcedβ β ideal for powering tokenized, revenue-yielding AI assets on Ethereum.