Help Center

Thank you for listing your rig with Mining Rig Rentals.

If a rental is not functioning as expected, the first step is to determine whether the issue originates from your rig or from the renter’s pool configuration.

1. Verify your rig is online and healthy

Confirm that your mining hardware is powered on, operating normally, and actively attempting to connect to Mining Rig Rentals. Even if your miner reports that the pool is offline, it should continue attempting to connect so that we can detect the rig’s availability.

Because Mining Rig Rentals connects your rig directly to the renter’s pool, a renter’s pool outage will also appear as a lost connection on your end. If there is no active pool connection, the session is closed automatically. Once the renter corrects their pool configuration, your rig should reconnect normally.

Also verify that your hardware is not throttling or shutting down due to temperature or other local hardware issues.

2. Consider renter pool and difficulty issues

A renter’s pool may appear online but still be unable to provide valid work. Common issues include internal pool errors or an incorrect work difficulty that is too high or too low for your hardware.

You should configure the Suggested Difficulty in your rig settings. This provides guidance for renters and establishes a clear reference point. If the renter’s pool is issuing work outside a reasonable range—generally more than ±50% from what your device can handle—you should notify the renter that their pool difficulty configuration is likely incorrect.

In some cases, a renter’s pool selection may result in slightly reduced hashrate due to pool-side behavior. To mitigate this, Mining Rig Rentals applies a small hashrate adjustment to help ensure rig owners are treated fairly.

3. Refunds and responsibility

You will not be penalized, receive a reduced RPI score, or be charged a refund for issues caused by a renter’s pool configuration, pool availability, or difficulty settings.

If you suspect a pool-related issue, we recommend leaving a message for the renter using the Communications tab to inform them of the problem.

If a renter opens a support ticket requesting a refund, we will explain that the issue originates from their pool configuration and guide them toward correcting it.

If you are ever charged a refund that you believe is incorrect, simply open a support ticket and request a review. While we continuously work to provide a reliable platform, we are always willing to reassess cases to ensure a fair outcome for all parties.

Thank you for using Mining Rig Rentals.

Responsibility for hashrate issues depends on a limited and clearly defined set of conditions while your rig is rented.

When you are not responsible

If your rig is online, properly configured, and free of hardware or software faults that would prevent normal operation, then hashrate problems are most likely caused by the renter’s pool configuration or pool-side issues.

In these cases, you are never responsible for reduced hashrate resulting from:

• Renter pool outages or instability

• Incorrect pool difficulty settings

• Pool-side errors or internal pool issues

• Poor pool performance or inefficiencies

If you suspect the issue originates from the renter, review your miner console for pool-related errors and verify the renter’s pool status. You should notify the renter using the Communications tab within the rental interface and attempt to resolve the issue cooperatively.

If the issue cannot be resolved, you may either:

• Open a support ticket and request that Mining Rig Rentals staff cancel the remaining rental time, or

• Allow the rental to continue despite the issue

In all such cases, you are paid for the elapsed rental time during which your rig remained online and properly configured.

When you may be responsible

You may be held responsible for hashrate problems if the issue is caused by your rig, including but not limited to:

• The rig being offline or intermittently disconnecting

• Incorrect hashrate, algorithm, or configuration settings

• Hardware failures, overheating, or throttling

• Software or firmware misconfiguration on the miner

In these situations, Mining Rig Rentals may issue a prorated refund to the renter to account for reduced or unavailable hashrate.

In summary, as long as your rig is online, correctly configured, and functioning as expected, you are not responsible for hashrate issues caused by the renter or their pool.

If your rig does not appear in the marketplace, it is typically due to one or more of the following conditions:

1. Rig status is not set to Available
   Verify that your rig’s status is set to Available. Only rigs marked as available are eligible to appear in the marketplace and accept rentals.

2. Rig is not online or not connected to MRR
   Your rig must be in an Online state, which means your miner is actively connected to Mining Rig Rentals using the correct rig credentials. If the rig was recently active but is currently offline, use the List Offline Rigs option to help locate it.

3. Minimum price requirements not met
   We enforce basic quality controls on all listings. The minimum price for a 3-hour rental must be at least 0.00000100 (100 satoshis) in the selected payment currency. Rigs priced below this threshold will not be listed.

4. No payment currency enabled
   At least one payment currency must be enabled for your rig. If no payment currency is selected, the rig cannot be rented and will not appear in the marketplace.

5. Pricing configuration incomplete
   Ensure your minimum rental price is properly set in the rig’s Price Configuration screen. Missing or invalid pricing settings will prevent the rig from being listed.

6. Rig has not been online long enough
   Newly connected rigs must remain online for a minimum of 20 consecutive minutes before being listed. This requirement helps protect renters by filtering out rigs that frequently connect and disconnect.

If you have verified all of the above and your rig still does not appear in the marketplace, please contact Mining Rig Rentals support for further review.

There is a difference between a nominal hash rate shown in the manual of your mining device and an effective hash rate shown in our system.

Hash rate is the number of hashes generated per second. 
You will mostly observe the hash rate of your mining device in our statistics graphs. 

There is a difference between a nominal hash rate shown in the manual of your mining device and an effective hash rate shown in our system. It is important for you to understand the difference between these two.

Nominal Hash Rate
The nominal hash rate of 1 Gh/s means that your device is capable of generating 1 billion hashes per second - no matter if they match any criteria.

Effective Hash Rate
The effective hash rate is a hash rate calculated from hashes submitted by your device to your pool. Only a small portion of generated hashes by your devices get sent. They must fit certain criteria assigned by the pool (see: Shares).

Most of the times, the effective hash rate will be somewhat lower than the nominal hash rate.

Your effective hash rate depends on the luck of your mining device and the quality (stability) of your connection to the pool server. If you have experienced connection issues, then your effective hash rate will be lower than the nominal hash rate in that period of time.

Occasionally, you can be more lucky and find more valid hashes than usual. That is what gives you a slightly higher effective hash rate.

Share - Proof of Work

Share is a unit which pool uses for computing mining work.

When a miner connects to the pool it receives computational task to be solved - it computes hash values with certain properties (they must be lower than the limit derived from difficulty). Hashes satisfying the requirements are sent back to the pool and are used as a proof of miner's work. The quantity of miner's work is registered in units called shares. If a hash (proof of work) with difficulty XX is submitted by a miner then XX shares is counted by the pool.

To put it as simple as it could be:

1 share = 1 proof of work on difficulty 1
5 shares = 1 proof of work on difficulty 5 (or 5 proofs of work on difficulty 1)
100 shares = 10 proofs of work on difficulty 10 (you can see the pattern)

My mining rig isn't connecting to MiningRigRentals.com's server!

Please allow up to 2-3 minutes for your connection to complete and begin reporting.
Please double check the configuration suggestions, it's possible you are using the wrong rig client name or password. If you use the wrong rig client name "worker name" your ip may be blocked, as we re-use port identification and its common for annother users rig to have not been reconfigured and connecting to your rigs port. We block such connection by ip address and it is determned by them sending the wrong login. You may be inadverntly triggering this, it can be cleared by clicking on the "Get my rig port" button on your rig connection page.

You need at least one working pool defined in MRR's rig detail page in order to connect to MRR's stratums.

Make sure you're not using a mining client that has the "reconnect fix" added (currently only special versions of cgminer). Also check your config file for this line: no-client-reconnect : true, This line needs to be set to false. (This applies to older software before 2017)

If your rig is rented out and loses it's connection and cannot reconnect, ask your renter to double check that they setup at least 2 pools. If they are only using one and that pool fails, there will be no failovers and the connection will be lost. With no available pools at MRR, your rig will failover to your local config in search of work.

We appreciate you listing your rig with MRR. Please note that we will never charge a refund or dock RPI score against your rig for issues stemming from a renter's pool or difficulty choices. We recommend leaving a message for the renter in the "Communications" tab notifying them that you suspect a pool issue.

I am getting an error or message as indicated by mining software that mentions SOCKET

This message is a normal message. Any severity to the message applies to the connection link between you and the remote connection, it does not apply to mining or your hardware.
This message indicates that the connection to the remote service endpoint was closed. It can be that your miner disconnected, or remote side has closed the connection.

Your miner may close the connection for a variety of reasons:

• A mining reset as requested by the pool in normal operation
• A hardware event initiated the disconnection
• Protocol incompatibilty

The remote side (our service endpoint) will issue a disconnect for a varirty of reasons:

• The pool being mined to (yours or renters) requested a connection reset.
• Our service changed pool configuration (at your request, or when renter changes their pools)
• Our service could not connect to your pool
• Protocol incompatibilty

In these cases your miner should be configued to reconnect as soon as possible, which is the default case 99.99% of the time.

My pool requires unique worker ids! Mining Rig Rentals will only send a single login for each mining device (called a worker thread) to your pool. 

If your pool requires that your mining login(otherwise known as a worker or username) be unique, and your MRR rig/rental has more then one worker connected, please read below.
Mining Rig Rentals proxy server otherwise sends a single worker login to your pool as default. This is set by you, or your renter when your rig is rented. Some pools require that this login be unique for all connections(or worker threads) from the mining devices that are connected to the MRR rig. For some pools this may cause problems with accounting, or you may want to individually track each thread.

We have a feature for you to aid in this. This information applies to both rig owners, and rig renters.

We have implemented several token parameters you can add to your pool login you can use to help.

• {#tnid}            Thread Number ID, use to individually identify a thread connection for this rig. If a rig has 5 connections, {#tnid} will be replaced with with either 1,2,3,4,5 depending on which thread connects. A rig that disconnects can get a different Thread Number ID.
• {#rnid}            Rental Number ID, the rental ID for the connection if rented. It is 0 if not rented (for rig owners pools)
• {#rgid}            Rig ID, the rig's ID as displayed in your rig or rental.
• {#wname}      Worker 'Slash' Name. New feature for our rig owners (only). You can uniquely identify your threads connected to your rig by adding a unique name by appending '/' to your MRR rig login. Example EXAMPLE.1234567/THIS_IS_YOUR_WNAME

Additional tokens:

• {#sidx}           Server Index, our servers have internal IDs, for example our us-east01 server is index is 3.
• {#ccid}           Connection Count ID, each time a rig connects, it get an ID number incremented ranges from 1, to 4294967295. It is reset if our server restarts and is per-server. Use with Server Index.
• {#ssid}           Server Startup ID, our servers maintain unique connection IDs across startups. For example, {#sidx}.{#ssid}.{#rgid}.{#ccid} Will always be unique.

​For most situations, {#rnid}-{#tnid} or {#rgid}-{#tnid} is sufficent for unique worker identification on your pool.

In your MRR Rig or Rental's control page, under Pool settings, in your workername entry in edit pool, add The desired Token(s) in the place in the line in which MRR proxy server should replace The Token(s) with the indicated number or information. These Tokens also work in the password and Eworker field where available.

Any questions, contact support.

A rental is listed as Not Paid when the renter did not have enough funds to complete the payment at the instant the rental started, or when some one else has rented your rig before the person who got the Not Paid message did.
This simply means, the renter was not charged for the rental, since it was invalid. There is no effect on your rigs performance, or RPI score for this. 
If the message was the result of two renters renting at the same time, only one will get the rental, and the rental which is valid, will continue unaffected, while the renter who lost out, will get the Not Paid message, they would have to try at another time.

Your rig will continue to hash at your pool unaffected by the Not paid status.

xnonce is a stratum command that allows miners to receive xnonce1 updates without having to reconnect.
This was developed after the stratum protocol was widely in use, so support for it is sporadic in miners and pools.

If your pool uses xnonce, and a rig has specified it has xnonce, then MRR will send the command, and it will work with the pool.
If your pool does not use xnonce, there is nothing to worry about with the additional command. 
If a rig has not specified it supports xnonce, you may inquire the rig owner to enable it if there is a rental; if you desire, though a rig owner may often not need to enable it normally or even have the miner or software support for it.

bfgminer supports the xnonce via software, and possibly cgminer versions.

This is done by appending #xnsub to the pool URL you are connecting to, this applies to rig owners only: To enable it with MRR, append #xnsub to the end of the proxy URL you are using. Note that renters or owners can not append this to the MRR pool interface.
stratum+tcp://eu-de01.miningrigrentals.com:3333/#skipcbcheck#xnsub Is an example. We also suggest #skipcbcheck if you are using bfgminer as well.

Note that xnonce is not required at MRR.

Direct payment arrangements between rig owners and renters are strongly discouraged.

Any payment made outside of the Mining Rig Rentals platform is not protected by our systems. If you extend a rental or provide additional time in anticipation of off-platform payment, we cannot credit time, funds, or reverse the transaction under any circumstances. You assume full responsibility for the outcome, including the risk that the renter may never send payment or may later dispute the agreement.

Off-platform payments also introduce significant security risks. Funds sent directly between parties may be misdirected, intercepted, stolen, or sent using compromised or fraudulent payment methods. In such cases, Mining Rig Rentals has no ability to investigate, recover funds, or provide mediation. These scenarios frequently result in permanent financial loss.

For security, compliance, and abuse-prevention reasons, direct payments are not permitted or facilitated through the rental communication interface. Attempts to coordinate private payments through platform messaging are discouraged and may be restricted.

If a renter requests a direct payment arrangement or an extension beyond the platform’s standard mechanisms, the correct course of action is to involve Mining Rig Rentals support. Open a support ticket describing the situation and have the renter do the same. This ensures the matter is handled in a controlled, auditable, and secure manner.

If you are unsure of the renter’s intent, legitimacy, or ability to pay, the safest option is to decline or ignore the request. Proceeding without platform safeguards exposes you to unnecessary financial, operational, and security risk.

You may delete an unwanted or unused rig at any time.

To do so, navigate to your My Rigs page, locate the rig you wish to remove, and click the red Delete button.

Deleting a rig marks it as inactive within our system. The rig record is retained internally for logging, auditing, and historical reference purposes; however, the rig will no longer be usable on the platform.

Once a rig is deleted, all connections between that rig and Mining Rig Rentals’ proxy infrastructure are permanently disabled. Any mining device still configured to connect using the deleted rig’s credentials will fail to connect.

Important:
You must remove the deleted rig from your miner’s configuration. Leaving a miner continuously attempting to connect to a deleted rig results in repeated failed connection attempts. We routinely observe extremely high connection rates—often exceeding 100,000 connection attempts per hour—from miners configured this way, which places unnecessary load on our systems.

Please ensure your miner configuration is updated promptly after deleting a rig.

A renter has no direct access to your mining hardware—ever.

Renters cannot log into your machine, cannot access your operating system, firmware, BIOS, or management interfaces, and cannot modify clock speeds, voltages, power limits, firmware, or any other hardware-level settings. Mining Rig Rentals does not provide, expose, or broker any form of remote control or administrative access to your equipment.

The only interaction a renter has with your rig is through pool configuration. When a rental is active, Mining Rig Rentals’ servers instruct your miner to temporarily connect to the renter’s specified mining pool, wallet address, and worker parameters. This is the sole mechanism that enables the renter to receive mining rewards from your hashrate during the paid rental period.

Key points of control and isolation:

• Hardware control remains entirely with the rig owner
  You retain full authority over firmware, tuning, overclocking, undervolting, fan profiles, and physical access at all times.

• No OS or network access is granted
  Renters cannot SSH, RDP, VNC, web-manage, or otherwise interact with your system beyond standard stratum pool connections.

• Pool changes are automated and temporary
  Once a rental ends, your rig automatically returns to your default pool configuration.

• MRR cannot alter your hardware configuration
  Mining Rig Rentals acts only as a coordination layer for pool assignment and rental enforcement. We do not change miner settings, clocks, or performance parameters.

In short, renting your rig is equivalent to allowing someone to temporarily direct where your hashrate is submitted, not allowing them access to the machine producing it. Your hardware remains isolated, secure, and fully under your control at all times.

No

If you set your rig to unavailable, it will not cancel any current rentals. Your rig set to unavailable simply means that your rig will not be listed for new rentals.

Mining Rig Rentals Official Policy on Hashrate Resale and Third-Party Rigs

Purpose

This policy governs the operation and expectations around listing mining rigs on the Mining Rig Rentals (MRR) platform that derive their hashrate from third-party sources, such as resale of compute power from external providers like NiceHash.

1. Definition of Resale Rigs

A Resale Rig is any rig listed on the MRR platform whose underlying hashrate is not directly controlled or hosted by the account owner but is instead sourced from another mining rig, service, or provider (e.g., NiceHash, external cloud providers, third-party hosting facilities where you do not have direct administrative control).

2. Permitted Use of Resale Rigs

We permit resale rigs only under the following conditions:

• You maintain reliable availability of the hashrate across the lease term.

• You accept and maintain a low fault tolerance—downtime, delivery failures, and delayed start times are not acceptable.

• You are transparent in your rig performance and promptly respond to performance issues or refund requests.

• You do not obfuscate the origin of the hashrate if asked by MRR staff in support investigations.

Failure to meet these expectations may result in your resale rigs being disabled without notice or blacklisted from future rentals.

3. Standards of Performance

Because resale rigs are statistically more likely to:

• Experience failures,

• Deliver poor quality hashrate,

• Generate outsized support overhead, and

• Erode renter trust in the platform,

We hold these rigs to a higher standard than traditional rigs hosted directly by users. Specifically:

• Uptime Expectations: The rig must be hashing for 100% of the lease duration, or a proportional refund will be issued at our discretion.

• Monitoring Gaps: If there is a gap in hash delivery or availability (as seen on our monitoring systems), we will assume non-performance unless you provide verifiable logs showing otherwise.

• Stale Shares / Rejections: Some rejection is acceptable; however, high rejection or invalid rate without correction or acknowledgment will be treated as poor rig quality.

4. Refund and Dispute Policy

Our platform operates on a hybrid pro-rated refund system for standard rigs, where renters pay only for hashrate successfully delivered to a properly configured rental. Our full refund policy is available at Refund Policy.
However for resale rigs on our platform they are fully pro-rated and renters pay only for hashrate successfully delivered regardless of renter configuration issues.

If a resale rig fails to deliver hashrate, stalls during startup, or exhibits poor stability:

• A partial or full refund will be issued automatically or upon review.

• Claims of partial hashing (e.g., intermittent delivery) do not override the renter’s right to refund based on effective delivery metrics.

• Repeated refund cases on your rigs will result in account review or rig removal.

You assume the operational risk of third-party service instability. Refunds will not be negotiated beyond our standard pro-rated calculation.

5. Misclassification and Enforcement

If a rig is found to be resale-based but listed without disclosure, or if you contest a refund under false pretenses:

• The rig will be suspended pending investigation.

• Repeated offenses will result in permanent rig or account bans.

If your rig is not a resale rig and was misflagged or treated as such, you must provide evidence of direct control, such as:

• Miner logs

• Local system metrics

• Rig access information (non-sensitive)

Once verified, we will adjust enforcement accordingly.

6. Policy Changes and Final Authority

This policy is subject to change as platform conditions evolve. Final decisions on refunds, rig classification, and enforcement are at the sole discretion of Mining Rig Rentals staff.