Community mining benchmarks

Measure it. Make it reproducible.

Record your CPU, software, settings and measured power alongside raw miner output. Help other miners understand what a result actually represents.

Be the first to contribute a measured result

No reviewed hardware benchmarks have been published yet. The Linux walkthrough is an illustration, not a hardware comparison. Reports without a wall-power measurement can be submitted, but will be labelled “power not measured” and excluded from efficiency comparisons.

No email app? Send the completed template and logs to hello@scashnetwork.com. Nothing is submitted or published automatically.

Use a repeatable test

  1. Record the machine. Give the full CPU model, cores/threads, memory configuration, OS version and whether this is native, WSL or a virtual machine. Record cooling and any CPU power limits or tuning.
  2. Record the software. Save the miner version, release URL, binary SHA-256 and exact command with credentials removed. Include thread count, large pages, affinity and AES settings, even when using defaults.
  3. Warm up and repeat. Close unrelated workloads. Use a five-minute warm-up, then three identical runs. Choose a nonce count large enough for each measured run to last at least ten minutes; a short demo run is not a stable benchmark. Keep the same count and settings across all three runs and save the complete output, including initialization.
  4. Measure power at the wall. Record the meter model, five-minute idle average and the average during the measured mining interval. Keep peripherals consistent. Report total system watts separately from CPU sensor watts. Leave unavailable readings as “not measured”.
  5. Share the evidence. Report total H/s for all three runs and their median, measurement duration and CPU temperature. Attach logs and any meter photographs with personal information removed. Pool tests need accepted/rejected counts and must be labelled separately from offline benchmarks.

Capture the miner output

This short command checks that the miner works. Increase --nonces for the measured runs above. The count is per thread. Linux/macOS:

./minerd --version
./minerd --benchmark --nonces=5000 -t 2 2>&1 | tee scash-run-1.txt

Windows PowerShell:

.\minerd.exe --version
.\minerd.exe --benchmark --nonces=5000 -t 2 2>&1 | Tee-Object -FilePath scash-run-1.txt

Source: miner benchmark options

Calculate electricity from your readings

Enter whole-computer wall watts, hours of use per day and your price per kWh. Costs use your chosen currency. This estimates electricity only; it does not estimate rewards or profit.

Enter all three values to calculate. Placeholder numbers are examples, not measurements.

Total energy = mining wall watts × hours ÷ 1,000. Additional energy above idle = (mining watts − idle watts) × hours ÷ 1,000. Label which one you report. Compare H/s per watt only when power is measured over the same interval and with the same measurement scope.

Screenshots are supporting evidence

You can email screenshots or a short screen recording with your report. Show the miner version, full settings and the complete run summary. For power, include a clear meter photograph and explain how the average was measured. Screenshots can be edited, and a momentary meter reading is not an interval average; neither proves a result alone.

How published reports will be labelled
LabelMeaning
Community-reportedA contributor supplied the result. Maintainers checked the required fields, arithmetic and evidence for consistency; they have not repeated the measurement.
Independently reproducedA different named tester repeated the documented procedure on comparable hardware. Both reports, configurations, differences and measurement limits are linked. Hashrate and wall power are assessed separately.

Unclear or implausible reports stay unpublished while we ask for logs or a repeat run. For a disputed result, a reviewer may supply a fresh reference code to show in a new recording alongside the setup and measurements. This helps establish that evidence is new; it is not proof against manipulation.

What happens after submission

Scash Developers review the report for missing fields, consistent units and supporting evidence, and may request another run. Publication includes your chosen public name, test date, settings, measurement method and evidence. Tell us what you consent to publish; keep private keys, wallet files, RPC credentials and personal contact details out of public logs. Review is not independent laboratory certification.

Start with the beginner walkthrough →

Updated · About this website and corrections