Mining Guide

SHA-256d proof-of-work basics and pool setup.

Algorithm

KuberCoin uses double-SHA-256 (SHA-256d) as its proof-of-work hash. The work target is encoded in each block header as a compact 4-byte representation of the maximum allowed hash value.

Difficulty retargets every 2,016 blocks, roughly every two weeks, using a clamped median-of-eleven timestamp window.

Hardware

• CPU. Practical only for testing on regtest networks.
• GPU. Effective during early bootstrap; outclassed by ASICs at scale.
• ASIC. Any Bitcoin-compatible SHA-256d ASIC works against KuberCoin without modification.

Solo vs. pool mining

Solo mining keeps reward control with the individual miner but produces variable income for small miners. Pool mining smooths reward variance at the cost of trust in the pool operator. Both modes use the same Stratum v1/v2 wire protocols supported by the reference node's getblocktemplate RPC.

Minimal pool configuration

# Example stratum proxy pointing at a local kuber-node
[upstream]
url = "stratum+tcp://pool.example.invalid:3333"
worker = "kuber1q….worker1"
password = "x"

[node]
rpc_url = "http://127.0.0.1:18080"
rpc_api_key = "set-in-config"

Reward schedule

Block subsidy starts at 50 KUBER and halves every 210,000 blocks. With a 600-second target interval, a halving occurs approximately every four years. Transaction fees accrue to the miner of the including block.

Energy disclosure

Proof-of-work consumes electricity proportional to network hashrate. Operators are encouraged to source renewable power and to publish the geographic location of large facilities. KuberCoin does not run a mining operation of its own.