Page 2 of 2

Re: Stratum protocol shortcoming (Attention lozschor)

Posted: Sat Jun 20, 2015 4:28 am
by rootdude
Mintsy doesn't allow rig owners to set static DIFF on the rigs we put up for rent there - so if there is a Titan behind that, I can tell you it is NOT a problem with prohashing. Mintsy is a very, very raw beta and the support there is NON-EXISTENT.

Do yourself a favor and use nicehash or miningrigrentals for your next rental so you have a better experience.

Re: Stratum protocol shortcoming (Attention lozschor)

Posted: Sat Jun 20, 2015 8:06 am
by RapidHash
loszhor wrote:
rootdude wrote:As a farm owner and a sometimes-rental-provider, keep this in mind. If the advertised hashrate of a rental is > 500MH, it's likely a conglomeration of multiple rigs all pointed to the same stratum on the rental site. The Titan is the top hashrate ASIC available - and a Titan, overclocked, with 6 cubes can theoretically surpass 450MH and approach 500MH. Anything more than that indicates more than one rig.

Virtually all of the rental providers siphon off hashes from rigs while they are in operation (I have suspected both BetaRigs and Mining Rig Rentals of doing this multiple times and have tested and determined that either they are stealing, or that the inefficiencies of their services are to blame). Either way, the only service that seems to have eliminated this is nicehash - the rig owners are only paid on valid hashes accepted by the pool, and the renters only pay for valids also. You can be assured that is you use nicehash for renting, that you will also get multiple rigs that are geographically disparate sending hashes.

The other reason why hashrates are so off, is that the renters (most of the time) don't know how to set DIFF for their mining rentals. If you are renting a big hashrate (like greater than 250MH) -- when you put in your pool info, you must either set them on a statically set stratum address from your chosen pool that is high enough to generate shares and not spam the pools. Many of the rig owners offering rentals state specifically in their descriptions what rig(s) you are renting and suggest DIFFs for your rental to get maximum effect. Renting without checking or asking for this info is bound to be frustrating for both the owner and renter. This reason is why I don't rent out my rigs anymore. The renters don't read nor do they pay attention to the DIFF requirements and complain endlessly about non-optimal hashrates... and the owner of the rig takes it up the butt when the site admins swoop in to offer the renter a refund, despite the fact that they paid no attention to the mining directions.
I am using Mintsy at the moment, my problem with them is that they refuse to tell me what is being specifically rented and will not give me any way of checking its status. I get no command lines or output or even a hardware outline so I can't even tell what I should input for the best settings. Prohashing is literally the only troubleshooting I have ever received. I am very disappointed with Mintsy's renting policies. I am not even allowed to set a failover pool if you can believe that.

I have a perfect solution for this problem. I have built miner rental platform where you rent real miners not the proxy. You get full control via our web interface, you can set pool strategy (failover and balance) and very detailed stats. I am a miner myself so the platform is built to be as easy as possible to use and give as much features as possible. We are in closed Beta at the moment and if anyone want to participate than please contact me on info@asicrunner.com and I will send you an invite.

Regards,
RapidHash

Re: Stratum protocol shortcoming (Attention lozschor)

Posted: Thu Jul 30, 2015 7:45 pm
by bizkut
I did succeed in getting my 10MH contract from mintsy to connect and hash today. Tried last night to no avail, contacted their support this morning, tried to point at prohashing again and it started working!

Re: Stratum protocol shortcoming (Attention lozschor)

Posted: Thu Jul 30, 2015 10:48 pm
by tucsondirect
I had this same problem