# Protocol Mechanics Proof-of-Compute System ## High-Level Overview HashCloud’s mining process follows a predictable, verifiable, and performance-driven compute cycle. Instead of relying on probabilistic hashing or nonce-based mining, every miner executes a deterministic sequence of GPU computations linked to their hardware identity. This ensures fairness, eliminates luck-based variance, and makes mining more accessible to everyday GPU owners. #### **High-Level Flow Diagram** ``` Miner CLI → Challenge Fetch → GPU Compute → Proof Creation → Verification → Reward Distribution ``` *** ### **Extended Workflow Breakdown** #### **Step 1 — Miner Installs the** HashCloud **CLI** The mining process begins when the user installs the HashCloud command-line interface (CLI). The CLI serves as the miner’s gateway to the network, managing hardware detection, challenge retrieval, computation dispatch, proof creation, and communication with backend validators. The installation is lightweight and optimized for cross-platform use, enabling participation from Windows, macOS, and Linux systems without requiring specialized knowledge. *** #### **Step 2 — CLI Detects and Registers GPU Hardware** Upon initialization, the CLI automatically scans the system for compatible GPUs. Each detected GPU’s unique identifiers such as GPU UUID, VRAM size, compute capability, and memory bandwidth are securely registered. This registration process is critical for maintaining fairness, as it prevents miners from spoofing hardware or simulating devices. By binding compute challenges to GPU identities, the protocol ensures that all work is executed on real physical hardware. *** #### **Step 3 — Backend Assigns Deterministic Compute Challenge** Once hardware is registered, the miner requests a challenge from the backend. The network generates a deterministic matrix computation challenge using a cryptographic seed derived from: * the miner’s wallet address * GPU UUID * timestamp * challenge index This ensures every miner receives a unique task that cannot be predicted, duplicated, or precomputed. The difficulty of the matrix operation adjusts dynamically based on the miner’s performance tier, ensuring competitive fairness across a wide range of GPU models. *** #### **Step 4 — GPU Performs Matrix Computation** The miner’s GPU begins executing the assigned computation workload, consisting of deterministic linear algebra operations optimized for parallel processing. Unlike hashing puzzles, these workloads reflect real computational value and are structured so that every miner must complete the full task no shortcuts or brute-force randomness exist. The deterministic nature ensures identical inputs always produce identical outputs, enabling fast and trustless verification. *** #### **Step 5 — Results Are Hashed and Packaged Into a Proof** After the GPU completes the computation, the output matrix is transformed into a compact cryptographic hash. The proof includes: * matrix size * compute time * GPU identity metadata * output hash This proof is formatted into a lightweight submission package that preserves verifiability without requiring large data transfers. By compressing the computation into a hash, the system remains efficient for miners on low-bandwidth networks. *** #### **Step 6 — Proof Submission to Backend Validators** The CLI transmits the proof packet to the verification backend. Validators reconstruct the same deterministic matrices and recompute the expected output hash. If the miner’s hash matches the validator’s result, the proof is accepted as valid. Invalid or inconsistent submissions are automatically rejected, preventing fabricated workloads or fraudulent participation. *** #### **Step 7 — Backend Stores Performance Data** Once validated, performance data from the miner such as completion speed, challenge accuracy, GPU behavior, and consistency is stored in the backend’s telemetry system. This ensures miners are scored fairly based on their real computing output. Performance logs also allow the network to optimize difficulty levels, ensure fairness across heterogeneous hardware, and protect against exploit attempts. *** #### **Step 8 — Daily Reward Distribution Based on Relative Performance** At the end of each mining epoch, the system calculates total network compute output and determines each miner’s share relative to the total. Rewards are distributed daily, ensuring predictable emissions and long-term sustainability. High-performing GPUs earn proportionally more, while lower-end devices still receive fair rewards based on their contribution. VIP staking multipliers adjust the miner’s score but never mint extra tokens preserving economic integrity. *** ### **Mining Philosophy** HashCloud replaces the randomness of hash-based mining with deterministic compute tasks that deliver real value while preserving the core fairness of Proof-of-Work. Every miner competes based on genuine computational strength, not luck, ASIC monopolies, or capital advantage. This design realigns mining with decentralization, accessibility, and meaningful compute utility. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.hashcloud.sh/architecture-overview/protocol-mechanics-proof-of-compute-system.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.