Ctrlk
For the complete documentation index, see llms.txt. This page is also available as Markdown.

Mining Workflow Overview

Proofs in HashCloud are deterministic and cryptographically verifiable.

{
  "wallet": "0x5063...",
  "gpuId": "GPU-041ae03...",
  "gpuName": "NVIDIA GTX 1650",
  "matrixSize": 512,
  "elapsed": 4.85,
  "resultHash": "a1b2c3d4...",
  "timestamp": 1735130000
}

Each proof includes: Wallet: Identifies the miner. GPU ID & Name: Ensures UUID-based validation. Matrix Size: Defines compute difficulty. Elapsed Time: Used to derive performance. Hash: Ensures deterministic verification.

HashCloud redefines the traditional mining cycle by replacing probabilistic hash guessing with deterministic GPU computation. Instead of competing in a lottery like Proof-of-Work, miners perform a guaranteed sequence of verifiable compute tasks. This ensures that performance not luck or ASIC dominance determines reward outcomes.

The network issues computation challenges to miners, each tied to their GPU identity and time window, ensuring fairness and preventing precomputation exploits. Miners compute the matrix results, generate a hash, and submit a lightweight proof to the verification engine.

The mining flow is designed so that every stage from challenge generation to reward distribution maintains transparency, reproducibility, and resistance to manipulation. Because workloads are deterministic, the network can independently recompute the challenge to confirm correctness without requiring the miner to upload large matrices. This makes the system extremely bandwidth-efficient and scalable across everyday consumer GPUs.

Workflow Diagram

Challenge Issued   ↓ GPU Performs Deterministic Matrix Computation   ↓ Output Matrix → Hashed → Proof Generated   ↓ Proof Submitted to Network   ↓ Network Verifies Computation   ↓ Performance Scored + Rewards Distributed

Deterministic Matrix Computation

At the heart of HashCloud is the use of deterministic linear algebra workloads. These tasks are chosen because GPUs naturally excel at matrix operations, providing perfect alignment between hardware capability and protocol requirements.

Each miner receives a unique matrix pair derived from a cryptographic seed combining wallet address, GPU UUID, and timestamp. This ensures that challenges cannot be copied, predicted, or precomputed.

Because matrices differ by miner, time window, and hardware identity, the protocol achieves strong resistance to spoofed submissions or fraudulent compute outsourcing.

Cryptographic Proof Submission

Miners do not submit raw matrix outputs. Instead, they create a compact hashed proof that includes metadata such as elapsed time and matrix size.

The verification engine reconstructs the challenge and recomputes the expected hash. If the values match, the proof is validated.

This ensures: ✅ low bandwidth usage ✅ protection from cheating or synthetic compute ✅ scalable participation across many hardware types

Proof Flow Diagram

Matrix Output → Hash Function → Proof Packet   ↓ Network Regenerates Challenge   ↓ Network Recomputes Expected Hash   ↓ Hash Match? → Yes → Valid Proof        → No → Rejected Submission

Performance Scoring & Reward Allocation

HashCloud allocates rewards using a transparent scoring model based on matrix size and computation time. Larger matrices increase difficulty, while faster completion times represent higher GPU performance.

This avoids unpredictable PoW-style variance and ensures every miner receives a reward proportional to their actual computational contribution. VIP staking multipliers increase point earnings but never inflate token emission, keeping economic integrity intact.

✅14-Day Reward Distribution + Community Voting

14-Day Mining Reward Distribution Cycle

HashCloud distributes mining rewards using a fixed 14-day epoch cycle:

  • All valid proofs submitted within the 14-day window accumulate compute points.

  • At the end of the epoch, each miner’s total contribution is calculated.

  • Rewards are released proportionally based on accumulated points.

  • After payout, the epoch resets and the next 14-day cycle begins.

This model ensures predictable payouts, stable economics, and fair competition across different GPU tiers.

Community Voting / Team or Partnership Decision on Reward Token

Before each 14-day epoch begins, the reward token for the upcoming cycle is determined through one of two governance paths:

✅ 1. Community Voting

The community miners, stakers, or token holders votes on:

  • Which token will be used for reward distribution

  • Seasonal or promotional reward choices

  • Partner token events or bonus cycles

Voting can occur through:

  • Governance dashboard

  • Snapshot-style off-chain voting

  • Integrated polls (Discord, Telegram, Website)

This ensures decentralized influence over reward economics.

✅ 2. Team / Partnership Decision

When strategic flexibility is needed, the reward token may be selected by:

  • The VIP Amplify core team

  • Strategic partnerships

  • Ecosystem collaborations

  • Market-driven initiatives

This ensures HashCloud can adapt reward tokens aligned with partnerships, liquidity opportunities, and long-term sustainability.

Both governance paths ensure the protocol remains adaptive, community-aligned, and strategically flexible.

Last updated