TRANSPARENCY & WARNINGS

Comprehensive Risk Disclosure

CoinMiners offers browser diagnostics, synthetic benchmarks, and manual economics scenarios. Repository source contains a Native RandomX development worker, but no signed public client or approved public pool is available. Browser mining is not enabled. Any compute workload you explicitly start uses your electricity and hardware resources. Please read these risks carefully.

1. Electricity Tariffs & Financial Losses

Running computing components at maximum utilization draws substantial electrical power from the wall socket. If your local utility electricity rate exceeds the break-even cost ($/kWh) of the active workload, you will lose money on every hour of operation. Always verify your actual marginal electricity rates—including seasonal tier bumps and delivery surcharges—before conducting sustained workloads.

2. Thermal Stress & Hardware Degradation

Continuous execution of intensive math algorithms increases operating temperatures of CPU cores, GPU dies, and VRAM chips. Inadequately cooled computers (particularly thin-and-light laptops or dusty chassis) may experience thermal throttling, cooling fan wear, or shortened component lifespans. CoinMiners does not guarantee that your equipment will withstand sustained full-load stresses without degradation.

3. Cryptocurrency Price & Difficulty Volatility

Cryptocurrency market prices fluctuate widely, and network mining difficulty continuously adjusts as global hashrate changes. A workload that is marginally profitable today can become unprofitable overnight if coin prices fall or mining difficulty rises.

4. Tax & Legal Responsibilities

In many jurisdictions (including the United States under IRS guidance), cryptocurrency earned through mining is considered taxable gross income at fair market value upon receipt. Users are solely responsible for keeping accurate transaction records and reporting digital asset gains, losses, and mining receipts to relevant taxing authorities.

5. Native Benchmark Resource Use

The standalone unsigned development benchmark performs full-memory RandomX CPU work and uses about 2.1 GiB of memory. The separate daemon worker uses one CPU thread in RandomX light-cache mode and requires local terminal confirmation after a session command; no real pool is configured by default. Stop the foreground daemon with Ctrl-C or use the session Stop action. Mock shares and client-reported H/s are not pool acceptance or income. Check cooling, available memory, power use, and the condition of your device before starting any compute workload.