Skip to content

Mining Models

Canonical

Purpose

Mining must be documented by model because different networks and products use different reward mechanisms, risks, costs, custody assumptions, and disclosures.

Model Types

  • Proof-of-Work mining: hardware performs computation to compete for network rewards.
  • Pool mining: miners contribute hashrate to a pool and receive rewards under pool rules.
  • Solo mining: miner attempts to mine blocks without a pool, with high reward variance.
  • Hosted mining: hardware is operated in a hosting facility or by a service provider.
  • Cloud-style mining access: user accesses mining capacity or a product without direct hardware custody; this is claim-sensitive.
  • Hashrate allocation: defined share of mining capacity allocated to treasury, users, or products if approved.
  • Validator operations: node validates consensus and may earn rewards under non-PoW networks.
  • Node infrastructure: nodes support network reliability or data access and may not earn rewards.
  • Educational mining simulation: Academy or dashboard simulation for learning.

Model Fields

Fields should include model ID, network, consensus or algorithm, reward source, infrastructure, custody, cost model, payout model, user-facing status, treasury impact, risk level, governance status, compliance status, and reporting requirement.

Status Labels

Statuses may include Research, Simulation, Internal Test, Pilot, Active Internal, Active User-Facing, Paused, Deprecated, and Prohibited.

Selection Criteria

Selection should consider network reliability, reward variability, hardware needs, energy or hosting cost, pool or validator counterparty risk, liquidity, compliance risk, treasury fit, disclosure complexity, monitoring availability, and security requirements.

Released as living documentation for the Axodus ecosystem.