How to Test a NerdQaxe at Home for 30 Days

A NerdQaxe 30-day test turns a new compact miner into measured evidence. The test begins only after safe commissioning and uses one supported stock configuration. It records wall energy, pool accepted hashrate, rejects, temperatures, restarts, Wi-Fi stability, sound and household impact. The result can show whether the unit meets a learning, solo-mining or low-power operating objective without pretending that one month predicts future Bitcoin income.

Define the purpose and pass criteria

Reassess NerdQaxe 30-day test whenever network conditions, firmware, tariffs or official guidance changes.

Choose one primary objective: learning about open ASIC hardware, contributing real SHA-256 work, running a solo-mining experiment or testing compact heat and noise. Do not set ‘find a Bitcoin block’ as a 30-day acceptance condition.

Write measurable criteria for safe power, maximum normal chip temperature under the seller’s guidance, stable fan, accepted hashrate range, reject threshold, restart count and Wi-Fi availability.

State the domestic constraints: occupied-room noise, surface temperature, placement, router policy and acceptable energy budget. The device can work technically while failing the household objective.

Record who may change frequency, voltage, firmware, pool and payout. Freeze those values during the baseline unless safety requires intervention.

Capture the day-zero baseline

Inspect with power disconnected, then start at a supported stock profile. Record local and pool readings only after the miner reaches stable temperature and share difficulty settles.

Save seller or project specifications as dated references. Community tuning screenshots are not the acceptance range for the supplied unit.

Measure wall power and energy

Use a suitable plug-in meter or installed meter without exposing live conductors. Record watts after thermal stabilisation and cumulative kWh for the full period.

Daily energy can be cross-checked by multiplying average kilowatts by hours, but the cumulative meter captures restarts and changing duty more accurately. Note meter resets and power cuts.

Inspect supply and connector temperature safely. Discolouration, looseness, repeated resets or excessive heat requires shutdown and investigation, not a higher voltage setting.

Value energy at the actual tariff period, including time-of-use rates where applicable. Keep the cost separate from mining revenue so the technical test remains understandable.

Track accepted work and pool records

Record local hashrate for hardware diagnosis and pool accepted hashrate for delivered work. Use the same time zone and observation window.

Short pool estimates move with random share arrival. Compare daily figures for alerts and 7-day or 30-day accepted averages for performance. Allow the pool’s variable share difficulty to settle after reconnects.

Separate stale, duplicate, invalid and authorisation rejects. A high reject rate can come from Wi-Fi, pool region, firmware, tuning or configuration and needs the correct fault path.

Reconcile pool credit after the stated method and threshold. The absence of a payout can reflect a minimum balance rather than missing accepted work.

Log heat, cooling and household impact

Record room, intake and reported chip temperatures at the same time each day and during the warmest ordinary condition. Note fan speed, dust and any airflow obstruction.

Do not cover the miner or stop the fan to reduce sound. If an enclosure is tested, retest temperatures and power and use safe non-combustible materials with adequate airflow.

Measure sound at the desk, occupied room and sleeping or neighbour-sensitive location relevant to the household. A phone app can compare changes but is not a calibrated legal assessment.

Record whether heat was useful, unwanted or caused additional ventilation energy. A winter benefit should not be projected unchanged into summer.

Use a fixed weekly review

• Day 1: confirm power, cooling, network, pool and payout identity.
• Day 7: compare accepted rate, energy, rejects and restarts with the baseline.
• Day 14: inspect dust, connector condition, fan and household impact.
• Day 21: test approved pool or network failover without changing tuning.
• Day 28: freeze final meter and pool exports.
• Day 30: calculate accepted efficiency, uptime and complete energy cost.
• Document every exception and exclude only clearly evidenced external downtime.
• Do not extend the test merely to hide a failed criterion without recording the failure.

Interpret the result

Calculate accepted efficiency using average measured watts divided by accepted GH/s or the correct unit. Do not mix a local peak with a month of energy.

A pass for learning may require stable operation and useful telemetry rather than positive cash return. A pass for a specific energy budget requires cumulative kWh to meet the written limit.

No solo block in 30 days is normal and says little about whether the device worked correctly. Accepted shares are the evidence that it performed valid contributed work.

Classify the outcome as pass, conditional pass with one remedy, or fail. Assign cooling, power, network, firmware or seller action and a retest window where appropriate.

Frequently asked questions

Why test for 30 days?

It covers more temperature, network and pool variation than a short demonstration while remaining practical; it does not predict future profitability.

Should tuning be included?

Not in the stock baseline. Run tuning later as a separate controlled experiment.

Which hashrate should I use?

Use pool accepted work for delivered performance and local hashrate for diagnosis, aligned to the same period.

Is no block a failed test?

No. Solo block discovery is extraordinarily unlikely at compact hashrate and is not a sensible acceptance criterion.

How should power cost be calculated?

Use cumulative measured kWh and the actual tariff for each period, adding any related equipment where material.

What requires stopping the test?

Stop for unsafe power or heat, fan failure, damaged parts, uncontrolled firmware or payout changes and obtain appropriate help.

Conclusion

A NerdQaxe 30-day test succeeds when it produces a reproducible operating record, not when luck produces a block. Freeze stock settings, align wall energy with accepted pool work and include temperature, noise, network and household evidence. The final pass should match the device’s declared purpose and record any remedy before continued use. Retain the full daily log rather than only the 30-day average. An average can hide one high-temperature afternoon, repeated overnight reconnects or a power event. The exception record is often more valuable than the headline figure when deciding whether the home location and supplied assembly are dependable.

Next steps

Use The Mining Shop UK home-mining and profitability resources to compare the measured result with the original objective.