Welcome to our Help Center.

Our Help Center is designed to give you a place to get the information you need to be effective at using our site.

You can find information by browsing the sections and categories on the left hand dropdown menu (top if you have a very small screen)

We appreciate any feedback regarding the design of the help center, or new bits of information to add, including tutorials; You can open a ticket with us at any time.



We appreciate you listing your rig with MRR.

Sometimes your rental may have an issue. The first task is to determine if your rig has the issue, check your hardware to make sure that it is powered on and connected to MRR's servers, even if your hardware complains that the pool is offline. Note that if the renters pool is offline, so is your rig's connection to MRR, since we connect you directly to the renters pool! If there is no pool connection we close the connection. Your rig should keep connecting to tell us that your rig is online, and should the renter fix their pool settings. One other thing to check is your miner's temperature, make sure its not overheating.

There can be issues with their pool even though it is online, such as internal issues at their pool, or work difficulty may be too low or too high for your rig to be able to work. You should set your Suggested Difficulty in your rig settings, for both your and the renters reference. If you notice that their work difficulty is outside of a reasonable range for your device +/- 50% then notify your renter that there is an issue with their difficulty settings at their pool. In some cases, a renters pool choise may result in slightly reduced hashrate. To combat this we provide a slight hashrate boost to ensure that your rig is being treated fairly. 

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.

Should your renter open a ticket requesting a refund, we will express to them that there is a problem with their pool and guide them to correcting the issue.
If you are ever charged a refund against a rental you do not agree with, simply open a ticket and request our review. While we continuously work to provide the most reliable service we can, we will always remain prepared to consider another review to insure everyone's satisfaction.

Thank you for using MRR!

Socket Error is a common message in most mining software. It means that the pool has issued a disconnection unexpectedly. This can occur if your pool, or your renters pool while rented issues a disconnection or is having other issues, or is offline.

If you are not rented, you should review that your rig is displaying hashrate on MRR and at your pool, if there is no hashrate, your pool may be offline or not working. We suggest you add at least three backup pools to your configuration on our site.

If your rig is rented and you are seeing this error, you should inform your renter that there may be an issue. If there is no hashrate displayed on MRR for your rig that means there is indeed an issue at their pool and they should fix it as soon as possible, and add backup pools.

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)

We kill connections to MRR servers when there are no available pool choices to mine at. Thus we recommend a similar localized pool setting your config file:
1. Closest MRR server
2. 2nd Closest MRR server
3. Your favorite pool (not MRR server)

This gives you the greatest amount of redundancy (you can add as many or all of our servers like this). Also, if the renter's pool ultimately fails, your rig will fail over to pool #3 (your favorite pool) and begin hashing on your behalf. This is done intentionally to provide you with no downtime in the event you choose to compensate your renter.  Our refund system accurately tracks and calculates shares if it becomes necessary.

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.

Should your renter open a ticket requesting a refund, we will express to them that there is a problem with their pool and guide them to correcting the issue.

If you are ever charged a refund against a rental you do not agree with, simply open a ticket and request our review. While we continuously work to provide the most reliable service we can, we will always remain prepared to consider another review to ensure everyone's satisfaction.

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.


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.

The "mismatched block contents" message is 100% common among various versions of BFGminer. 
It's simply a print out display and does not effect hashrate. Most pools do not support the sending of block contents, and the request by BFGMiner for this information is ignored, which results in the message. 
The message can safely be ignored without any negative effect.

"Block contents" option by BFGminer is strictly an option for pools to tell the miner all the transactions on the network being included in that block and that can be 0-10MB of data sent each minute per connection. This can overload pools and this is why most do not support this, further: bfgminer is the only one that requests that data, against the standard of other mining software.

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.

My renter wants to pay me directly for any reason or wants to pay for extended time,

We don't recommend this. Once you extend the renter's time we cannot credit the time or funds back to your account. If you choose to do this, you must assume the risk that the renter may never send the additional funds. The time extension is meant to allow compensation for rig down time.
We also don't allow direct payments via the rental Communication interface for security reasons. Consider having MiningRigRentals support to do any such exchanges. Open a ticket with us, and have the renter do the same explaining the reason or what is going on.

Regardless, it's best to ignore requests in which the renter says they are going to pay you if you are unsure.


If you do not know what RPI is, please read our Faq about RPI Here.

In general, rentals in which there are issues relating to the operation of the rig may cause a reduction in your rigs RPI. Potential reductions are determined during the review process.
We review a rental in several ways, a renter makes a ticket request due to some issue with your rig. We also review all underperforming rentals after they end.

During the review process, issues relating to the operation of your rig would be the cause of any RPI reduction, these include being offline, incorrect advertised hash rate vs what is seen on a consistent period.
The purpose of the RPI system is to give the renter a way of determining how successful rentals with your rig have been in the recent past. The more rentals you have that are successful, the better your rating.

You can view your rigs rental history to view any rentals in which there was a negative RPI impact. These would show up highlighted as red, though rentals that are still in the review process are still counted as good until it could be determined there was an issue with your rig. If you are unsure of the reason behind any reduction of your RPI, please list any recent rentals in which this occurred, and open a ticket with support so that we can investigate and inform you of the reason. As well, we are open to re-reviews for any RPI related issues within a two week period, as important data may be pruned from our system.

In order to improve your RPI, you should investigate the cause of the reduced average hash rate during your rentals. Again, you may ask us as to the reason behind the reduction. In most cases, we are understanding regarding unforeseen offline events, let us know what occurred and we may take off any negative RPI mark. If the cause is the hash rate, please adjust your advertised hash rate to match what your recent rentals in which there were no renter pool issues. If your rig is consistently having rentals at lower hash rates and even at your own pool, we may intervene and adjust your hash rate to match so that renters do not get low hash.

You may delete an unwanted or unused rig at any time. To do this, navigate to your "My Rigs" page.
Locate the rig you want to delete and click on the red delete button.

This marks the rig as deleted in our system. It remains for logging information, however,
Please note that once you delete the rig, all connections to our proxy for that rig will be disabled.

This means you should remove this rig from your miners configuration.
Please do not leave a miner to endless try to connect to a deleted rig, we observe 100,000 connections an hour from individuals with deleted rigs, this causes undue stress on our systems.

The client has no access to your machine at all. Everything is done through a pool interface. No one, not even MRR itself, can change any settings or clocking of your hardware.

The only thing that can change is the pool being mined, MRR's servers tell your rig to connect to your renters pool when you are rented, as this allows renters to mine at their pool with your rig once they have paid.


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.

If your pool requires that your mining login(otherwise known as a worker or username) be unique, and your MRR rig has more then one worker you have 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 your mining devices that you connected to your MRR rig.

We have a feature for you to aid in this.

Locate your mining devices config files or interface. Each mining device you are connecting to your single MRR Rig should be edited to follow the below description.
In your mining device config for your MRR pool connection, edit the password variable, or password line entry to be as of the following format: x{workerid=#}  The text should be entered as shown.
The x is default password, can be omitted or changed. The Part between {} are parameters for MRR proxy server. The # should be replaced by you with a numerical integer greater or equal to and less than 2000000000. A value of any other may cause issues. Each of your mining devices should get a unique number, write these down for reference, or include the number in place of x to display on your MRR Rig's workers display.

In order to use this feature, as mentioned, your mining devices connected to your MRR rig, known as worker threads, should now have a unique integer assigned to it by your config changes. In your MRR Rig's control page, under Pool settings, in your workername entry in edit pool, add {#} in the place in the line in which MRR proxy server should replace {#} with your workerid integer you assigned to it.

Any questions, contact support.