Glossary

🧠 Core Concepts

OpNode

A decentralized GPU compute protocol delivering high-performance, on-demand infrastructure for AI/ML, scientific computing, rendering, and data processing.
OpNode leverages distributed nodes and a token-incentivized economy to provide trustless, scalable, and cost-efficient compute.

Cloudverse

OpNode’s decentralized Cloud-as-a-Service layer, enabling users to launch, scale, monitor, and pay for GPU jobs across a global network of providers — entirely on-chain.

Cloud Payments

The billing backbone of Cloudverse, enabling pay-as-you-go or prepaid usage with $OPNODE, stablecoins, or fiat (coming soon).
Smart contracts manage cost tracking, escrow, refunds, and job auditing transparently.

Cloud Wallet

A non-custodial smart contract wallet tied to a user’s crypto wallet.
Holds compute credits ($OPNODE, USDC, etc.) and powers on-chain GPU metering and payments.

Job Container

Every workload runs inside a secure, containerized environment (e.g., Docker), ensuring isolation, reproducibility, and fast deployment.
Supports pre-built or custom environments.

🪙 Token Economy

$OPNODE

The native utility and governance token of the OpNode ecosystem.
Used for:

• Job payments

• Staking rewards

• Governance participation

• Provider incentives

Can be used directly for compute or staked for benefits (discounts, priority, and yield).

Staking

Both users and node operators can stake $OPNODE to:

• Access discounts

• Earn rewards

• Boost trust scores and job priority
  Staking aligns long-term incentives across the ecosystem.

Revenue Sharing

• 12% of Cloudverse revenue is redistributed to $OPNODE stakers weekly.

• Creates passive yield for token holders securing and providing liquidity to the network.

Tokenomics

💡 Compute Infrastructure

GPU Node

Independent compute providers contributing GPUs (e.g. RTX 3090, A100) to execute workloads.
Nodes earn rewards based on performance, uptime, and usage.

Job Marketplace

An open compute exchange where:

• Users submit jobs

• GPU nodes bid or claim workloads
  Pricing is dynamic, influenced by hardware type, demand, and node reputation.

Smart Metering

On-chain tracking of compute time, bandwidth, and resource usage per job — ensuring accurate billing and verifiable proof-of-compute.

Refund Mechanism

If a job ends early or fails, unused credits are automatically refunded to the user’s Cloud Wallet — guaranteeing fairness and cost efficiency.

Job Receipt

Every job generates an immutable on-chain record including:

• Job ID

• Input hash

• Output hash

• Runtime logs

• Payment details

• Node address

Stored on IPFS/Filecoin for transparency and verification.

🛠 Developer & User Tools

Job CLI

A command-line interface for developers to launch, monitor, and retrieve GPU jobs — ideal for batch processing, automation, and scripting.

Templates

Pre-configured environments (e.g., PyTorch, TensorFlow, Jupyter) for zero-setup launches.
Supports deployment from GitHub or Docker.

Monitoring Dashboard

A web UI providing:

• Real-time job monitoring

• Cloud Wallet balance tracking

• GPU usage, logs, and receipts

• Staking interface for $OPNODE and reward claims

REST API (Coming Soon)

Programmatic access for:

• Job submission

• Balance checks

• Logs and receipts

• Payment automation

Enables integration with SaaS products, MLOps pipelines, and developer tools.

📍 Governance & Ecosystem

OpNode DAO

The decentralized governance body managing:

• Protocol upgrades

• Fee structures

• Token emissions

• Strategic partnerships

$OPNODE stakers gain voting rights and proposal access.

Provider Reputation System

GPU nodes earn trust scores based on:

• Job success rate

• Runtime consistency

• Latency and uptime

• User feedback

High-reputation nodes gain premium job access and higher payout tiers.

🗓️ Roadmap

🔒 Security & Trust

Smart Contracts

Every payment, job submission, and staking action is enforced by audited smart contracts — ensuring safety, immutability, and fairness.

Slashing Mechanism

Nodes that fail, go offline, or submit invalid results face automatic slashing of staked $OPNODE and potential delisting.

Audit Trails

Each job generates a verifiable audit record, stored on IPFS/Filecoin, containing input/output hashes and performance logs — guaranteeing full transparency and traceability.