Before listing a rig for rent, you should test it through Mining Rig Rentals to confirm that it connects correctly, submits accepted shares, reports stable hashrate, and performs at the level you plan to advertise.

A rig should not be listed based only on miner startup output or a short local test. Renters expect the rig to deliver usable mining work through Mining Rig Rentals, not just show hashrate in the miner console.

Testing before listing helps prevent failed rentals, renter complaints, refund disputes, and unnecessary support reviews.

How to Test a Rig Before Listing It

Testing confirms that your rig is ready to accept rentals and mine reliably through Mining Rig Rentals.

A proper test should verify:

• the rig connects to Mining Rig Rentals,
• the miner receives work,
• shares are accepted by the pool,
• rejected or stale shares are low,
• the rig reaches stable hashrate,
• the advertised hashrate is accurate,
• all workers remain connected,
• the rig survives normal operating conditions.

The goal is not just to prove that the miner starts. The goal is to prove that the rig can deliver stable rented hashrate.

1. Confirm the rig is configured correctly

Before testing, review the rig setup carefully.

Check that:

• the rig is listed under the correct algorithm,
• the advertised hashrate is realistic,
• the correct miner software is installed,
• the rig is using stable clocks and power settings,
• all intended devices are detected,
• the rig’s pool failover settings are correct,
• your Mining Rig Rentals connection details are entered correctly,
• the rig is not using old or incorrect pool information.

Do not assume a previous configuration is still valid after changing algorithms, miner software, firmware, drivers, or hardware.

2. Use a known working pool

Test with a pool that you know supports the algorithm your rig is listed under.

The test pool should be stable, reachable from your rig, and configured correctly for the coin or algorithm being mined.

Verify the pool’s required format for:

• pool URL,
• port,
• wallet or username,
• worker name,
• password field,
• algorithm or coin-specific options,
• TLS or non-TLS connection.

Some pools require special password parameters, fixed difficulty settings, coin symbols, or mining modes. If the pool connection format is wrong, the miner may connect but still fail to submit valid accepted shares.

3. Connect through Mining Rig Rentals

The rig should be tested through Mining Rig Rentals, not only by connecting the miner directly to a pool.

A direct-to-pool test can prove that your miner works, but it does not fully prove that your Mining Rig Rentals setup is correct.

When testing through Mining Rig Rentals, confirm that:

• the rig appears online,
• workers are connected,
• pool connection status is normal,
• shares are being submitted,
• accepted shares are increasing,
• rejected and stale shares are low,
• Mining Rig Rentals hashrate reporting begins to stabilize.

If the rig only works when connected directly to a pool but not through Mining Rig Rentals, review your rig configuration before listing it.

4. Let the test run long enough

Do not judge the rig from the first few minutes of mining.

Short tests can be misleading because hashrate reporting depends on accepted shares over time. Some algorithms, high-difficulty pools, or lower-hashrate rigs may need more time before the reported hashrate becomes meaningful.

Let the rig run long enough to confirm stable behavior.

During the test, watch for:

• miner restarts,
• worker disconnects,
• rejected shares,
• stale shares,
• hardware errors,
• temperature changes,
• throttling,
• pool reconnects,
• unstable hashrate,
• devices dropping out.

A rig that looks stable for two minutes may still fail after it warms up or after difficulty adjusts.

5. Check accepted, rejected, and stale shares

Accepted shares are the most important sign that the rig is doing useful work.

A miner may display hashrate locally even when the pool is rejecting some or all of the submitted shares. Local miner hashrate alone is not enough.

Review:

If rejected or stale shares are frequent, fix the issue before listing the rig.

6. Compare miner, pool, and Mining Rig Rentals hashrate

Different systems may show different hashrate values because they calculate hashrate differently.

You should compare:

• miner-reported hashrate,
• pool-side hashrate,
• Mining Rig Rentals reported hashrate,
• individual worker hashrate,
• average hashrate over time.

The miner’s local hashrate is useful, but it is not the only value that matters. Renters care about the usable hashrate delivered through the rental connection.

If your miner shows high hashrate but the pool or Mining Rig Rentals reports much lower accepted performance, investigate before listing.

7. Verify every worker

If your rig uses multiple workers, confirm each worker is stable.

Check that every worker:

• connects normally,
• submits accepted shares,
• has expected hashrate,
• uses the correct algorithm,
• stays connected,
• does not produce excessive rejects or stales,
• does not restart repeatedly.

Do not include unstable or intermittent workers in the advertised hashrate.

A single failing worker can cause the entire rig listing to underperform.

8. Confirm temperature and power stability

A rig may pass a short test while cold but fail after it reaches normal operating temperature.

During testing, monitor:

• GPU or ASIC temperatures,
• hotspot temperatures where available,
• memory temperatures where available,
• fan speeds,
• power draw,
• PSU load,
• ASIC board/chip status,
• throttling,
• thermal shutdowns,
• voltage instability.

If the rig becomes unstable after warming up, reduce clocks, improve cooling, or repair the hardware before listing it.

Do not list a rig that depends on unstable overclocking to reach its advertised hashrate.

9. Check miner logs

Miner logs often show problems before they become obvious in the web interface.

Look for:

• authorization failures,
• connection timeouts,
• socket errors,
• rejected shares,
• stale shares,
• duplicate shares,
• low difficulty shares,
• hardware errors,
• device resets,
• watchdog restarts,
• pool failovers,
• driver errors,
• algorithm mismatch warnings.

Save logs if you are troubleshooting a problem or preparing to contact support.

10. Set an accurate advertised hashrate

After the rig has been tested, set the advertised hashrate based on stable average performance.

Do not advertise:

• the highest short-term spike,
• a miner startup burst,
• a best-case screenshot,
• performance from a different algorithm,
• performance from a direct-to-pool test only,
• hashrate from unstable overclock settings.

Advertise what the rig can reliably deliver through Mining Rig Rentals.

If the rig normally averages 1.00 GH/s but briefly reaches 1.10 GH/s, advertise around 1.00 GH/s, not 1.10 GH/s.

11. Set an appropriate Suggested Difficulty

If the rig setup includes a Suggested Difficulty field, set it based on the stable share difficulty observed while the rig is mining normally.

Suggested Difficulty refers to share difficulty, not network difficulty.

If the pool uses variable difficulty, wait for the pool to adjust to a stable value before choosing the setting.

A reasonable Suggested Difficulty can help produce cleaner hashrate reporting and reduce confusing short-term swings.

12. Test after every major change

Re-test the rig whenever you make a meaningful change.

Re-test after changing:

• hardware,
• algorithm,
• miner software,
• firmware,
• GPU drivers,
• ASIC firmware,
• overclock settings,
• power limits,
• pool configuration,
• network routing,
• operating system,
• Mining Rig Rentals rig settings.

A rig that was stable before a change may not remain stable afterward.

Pre-listing checklist

Before making the rig available for rent, confirm the following:

If any required item fails, do not list the rig until the problem is fixed.

Common problems found during testing

The miner connects but no shares are accepted

Possible causes include:

• wrong algorithm,
• wrong pool port,
• incorrect wallet or username format,
• pool password parameters are missing,
• unsupported coin variant,
• pool difficulty mismatch,
• miner software incompatibility.

Review the pool’s connection instructions and verify that the rig is listed under the correct algorithm.

The miner shows hashrate but Mining Rig Rentals reports low hashrate

Possible causes include:

• high share difficulty,
• too few accepted shares,
• rejected or stale shares,
• unstable workers,
• pool-side reporting delay,
• miner-reported hashrate not matching accepted share performance.

Let the test run longer and compare accepted shares across the miner, pool, and Mining Rig Rentals.

Hashrate drops after several minutes

Possible causes include:

• thermal throttling,
• unstable overclock,
• power limit issues,
• PSU overload,
• miner dev fee periods,
• hardware errors,
• driver instability,
• watchdog restarts.

Check temperatures, power draw, and miner logs.

One worker keeps disconnecting

Possible causes include:

• unstable device,
• bad riser or cable,
• weak power connection,
• driver crash,
• network interruption,
• miner configuration issue,
• failing ASIC hashboard.

Fix or remove the unstable worker before listing the rig.

When to contact support

Contact Mining Rig Rentals support if the rig works correctly when connected directly to a pool but does not work correctly through Mining Rig Rentals.

When contacting support, include:

• rig name or ID,
• algorithm,
• miner software and version,
• pool URL and port,
• test time,
• screenshots or logs,
• accepted/rejected/stale share counts,
• whether the issue happens on multiple pools,
• whether the miner works when connected directly to the pool.

Clear information helps support identify whether the issue is rig-side, pool-side, network-side, or platform-side.

Summary

Testing a rig before listing it protects both the rig owner and the renter.

A proper test confirms that the rig connects through Mining Rig Rentals, submits accepted shares, maintains stable hashrate, and performs at the level being advertised.

Do not list a rig based only on a short miner console test. List it only after it has proven stable under real operating conditions.