Node Types and Roles
In a traditional cloud architecture, compute coordination is centralized through closed scheduling systems and proprietary infrastructure. In contrast, StarMiner distributes intelligence, execution, and governance across a diverse network of node types, each fulfilling a critical role in the decentralized operation of the system.
This multi-node structure enables StarMiner to scale globally, handle workload diversity, and maintain decentralized control without compromising on performance, accuracy, or economic fairness.
1. Compute Provider Nodes
Role: Supply GPU compute power to the network.
These are the backbone of StarMiner’s infrastructure. Operated by individuals, organizations, or repurposed mining farms, these nodes contribute GPU resources and execute assigned workloads such as:
AI training and inference
3D rendering
Scientific simulation
High-throughput data processing
Key Attributes:
Registered and verified on-chain
Benchmarked for GPU type, memory, performance, and reliability
Rewarded in AGPU based on throughput, task accuracy, and uptime
Eligible for bonus tiers based on energy efficiency and regional availability
Hardware Examples: NVIDIA A100, H100, 3090, 4090, RTX-class GPUs
2. Validator Nodes
Role: Ensure task integrity and enforce protocol correctness.
Validator nodes do not execute jobs themselves, but instead:
Confirm the correctness of task results via probabilistic or redundant checks
Maintain consensus over network-wide compute performance
Score compute nodes based on performance, failure rates, and SLA breaches
Propose penalties for underperformance or malicious behavior
Incentives: Earn AGPU or AMAX for consistent validation, uptime, and governance participation. Validators may be slashed if they validate incorrect or manipulated data.
This ensures a trust-minimized compute pipeline, where output is independently verified before settlement.
3. Service Requester Nodes (Client Nodes)
Role: Submit computational tasks and consume GPU services.
These nodes are the interface point for developers, enterprises, and researchers. They:
Submit jobs via SDK/API/GUIs
Define job parameters: task type, budget, GPU spec, latency sensitivity
Lock AGPU tokens to pay for service
Monitor job completion and retrieve results
Client Roles Can Include:
AI developers requesting model training
Web3 apps integrating compute into dApps
Enterprises seeking decentralized GPU power as a cloud alternative
Requesters are billed in AGPU based on actual usage and tier selection. Priority access may be unlocked via AGPU staking or task bonding.
4. Oracle Nodes
Role: Feed verified external data into the compute protocol.
Oracles ensure that off-chain signals can influence job routing, node scoring, and pricing logic. They provide:
Real-time energy cost data (for green compute incentives)
Regional GPU availability
Weather or latency data (for edge computing jobs)
External compute demand signals (e.g., public model releases)
Why They Matter: StarMiner’s pricing engine and task-routing algorithms rely on accurate external data. Oracles prevent internal myopia and enable dynamic responses to market realities.
5. Governance and Coordination Nodes
Role: Propose and validate protocol changes, treasury decisions, and strategic upgrades.
These may overlap with validator nodes or run as separate actors holding AMAX governance tokens. They:
Initiate and vote on proposals (e.g., incentive curve changes, emissions rates)
Coordinate funding for infrastructure grants or R&D programs
Elect technical stewards and initiate version upgrades
These nodes turn the StarMiner network into a living system — one capable of evolving, adapting, and funding its own roadmap.
Role Interactions and Interdependencies
The decentralized nature of StarMiner requires all node types to operate in coordination, creating a self-sustaining cycle:
Compute providers earn AGPU for executing tasks.
Validators confirm performance and ensure accountability.
Requesters pay AGPU and receive reliable compute services.
Oracles feed market data to keep pricing and routing optimal.
Governance nodes ensure long-term system coherence.
This model ensures no single node class can dominate or distort the network decentralization is not just a technical feature, but a governance safeguard and economic necessity.
Summary
StarMiner’s node roles are modular yet interdependent, forming a globally scalable compute mesh that is:
Self-validating
Market-driven
Programmable
Decentralized at every layer
Each node contributes to the whole whether through computation, validation, coordination, or external signaling. This architecture transforms idle infrastructure into a global public utility for AI-era computation.
Last updated