Topic: [ANN] LeaseRig.net Rent & Hire Scrypt(Jane/Nfactor)/SHA3/SHA256/X11 HashPower! - page 49. (Read 125849 times)

Bolded text please. It kind of sucks having to convert my LTC and DOGE to BTC after a 72hr lease and the prices are no where near where they were before.

Thanks for the response miavator, but you didn't answer my concern. You basically said, "once that renter with the bad pool goes away, your hash will go back up... eventually."

I'm still being penalized for the action of a renter. So I need to then run my own pool for 24 hours to recover my green color and star, all the while losing out on lease income.

Perhaps you should take the self-declaration of hash speed out all together from the site. What value does it offer if you're just going to judge the rig against actual hash anyway? Just show actual hash speed, or the 24 hour average with no comparison to the declared speed.

Also, there should be some mechanism in place so that if the renter fails to use an appropriate pool, the rig owner is not penalized. If the pool they entered is hashing below the 24 hour average, then they are rated poorly or the variance is tolerated from a reporting perspective.

And, I sometimes move my rigs from scrypt to scrypt-n, which has a significantly lower hash. When I do that, I should not be penalized for the drop in hash vs the 24 hour average.

Damn typos - I meant "range" 

In my case the rage is between 2.3 mildly irritateds/day and 42 hopping mads/sec. But that's this legacy lrp and pool logic for you.

Things aren't perfect now, but they are getting soo much better.

+1

In the past few days there hasn't been a single day without my rig being rented. Question is, where do you get the 24-hour average with my pools then? Additionally I have currently three rigs connected via LRP and speed reports ALWAYS fluctuate a little - in my case the range is roughly between 4.8 to 5.1 MH/s. The more rigs you conntect via LRP the greater the fluctuations will be.

I do see the point introducing this but at the moment is is just not finished and does not reflect the real status of my rig.

EDIT: Misleading typo corrected. 

Ive been watching the rentals, and it seems that people don't seem to mind if the rig is hashing lower than listed. As they are being rented out fast also..

Hi Guys

Im running LRP on a dedicated machine with 7 miners connecting directly to the machines ip address.

I want to record the correct hashing speed and read all the info. I have setup listen port    leaserigproxy.exe 3333 address 7777 .

I keep getting the error below.

WARNING: cgminer API (192.168.1.133:7777) Closing connection - is IP allowed?

How is this corrected.?  All the other replies advise to change the -API allow to the local address, but as you see above, the proxy software is on a dedicated machine.

So when do you plan to implement having it based on 24hr average, as my listed hashrate is under my 24hr average, but my hashrate fluctuates slightly, so if you refresh the page one minute it may show 3-4% below listed, hence an underperforming mark, then the next minute if you refresh it will show 3-4% above listed, and there is a green good status.. overall average is above listed..

This is a bit disturbing.. please implement the 24 hr average checking ASAP, otherwise people will loose business over nothing..

Thanks for this.  I understand the methodology better, and i now think that's a fair way to determine the hashrate.   it benefits the site's reputation to have an "all green" board. 

let me know if there's a way to log my LRP activity to help.

That's what I said.   About the formatting.

The survey on the site right now shows that an exchange API is needed to accept multiple currencies while giving providers the ability to select how to receive payments.   Using an API we would not take a fee for the exchange as the actual exchange would have a fee built in.   

Honestly adding the highlighting and warning was not an easy decision as it clutters everything and detracts from the site.   It was only decided after finding that close to or over the 50% of all rigs on the site performed lower on the providers pools than their declared speed.   (Originally we were going to take away declared speed and use a rolling 24 hour average.  This would have made providers rig speeds dependent on customer pools and really would have made bad pools reflect on providers)  The current system is designed to show a more accurate depiction of rated speeds without taking into account bad customer pools. 

Are the amber color and the icon really needed? Shouldn't just the amber highlight suffice as notice enough?

Aesthetically, it looks cluttered. The LRP and */! icon should be right justified, or in a separate column on the far left in front of 'Provider'. For that matter, most text is left justified, and should be centered. 'Available! Hire' Should just read 'Hire' in larger font. Obviously, it's available.

To alleviate payment type headaches, perhaps you should consider something like the 'multipool.us' approach; Allow people to pay in multiple types, but offer people the option to either keep the payment in the coin it was paid in, or Leaserig will convert it to BTC for a small fee and pay it out that way. Since you are pushing the hourly payment approach, that puts you squarely in the middle of the transaction already. In for a satoshi, in for a BTC, right?  

Also, I have historically under rated my rig by 1-2%. It's nice to finally see some kind of differentiation to providers that consistently over rate themselves.

Thank You.

I'll have to test that one with some of my test rigs and let you know.  Right now:

riazg   CanadianThunder Miner is available and performing optimally!   1.00   0.01440000 accepts dogecoin accepts litecoin   147   99.99%   Hash. 1.01 MH/s

EDIT: This is the correct behavior of the filter.   The rigs page rounds the amounts to 2 decimals while the filter uses the actual speed.  If I declare a rig to be .619 and it's speed is .62 it shows green.  If I declare it .62 and it's speed is .619 it shows underperforming.  In both cases the main page would display .62 & .62.  The filter is for rigs performing < declared rate so if they are truly == to declared rate they show green.   You always lose at least 1 khash when the rig is rented due to pool swaps.

See above.

The underperform notice is based on your pool, your hardware, your hashrate.   Your LRP issue is a first and is being looked at by several people.   

Right now, we are using current hash rate.  So once your rig gets out of a lease and is relisted as rentable it will be based on YOUR pools.   The above is not an issue.

Once the legacy pool logic is rebuilt and the pool test queue put in place the speed rating will be based on a rolling average.   This does improve the site.  Almost half of the rigs left for rent do not perform at their advertised rate.

Put that in a ticket, I think there should be a MM for rigs instead of disable.

Something is not right... I get the (!) and my rig is declared as 1Mhash and it is doing 1MHash right now (As seen on the same line below)...

riazg   CanadianThunder Caution: Rig operating under declared speed!   1.00   0.01440000 accepts dogecoin accepts litecoin   147   99.99%   Hash. 1.00 MH/s   In 1 hours and 19 minutes

Is it possible to have a +/- 0.05 tolerance?

I also have this concern.  I list my machines living in north america, but i occasionally get people that will mine halfway across the globe in germany, poland, or UK.  pings are higher, and i do notice more stale shares when the pools are farther away.

I have also noticed that places like IPOminer pool have low difficulty as they specialise in initial mining, and this can create more rejects becuase the blocks are flying so fast.

some switching pools prefer to have "no-submit-stale" : false,, and i have mine set to true, which works for the majority of pools, but may result in lower rates for pools that accept stale shares.   If i set to false, there no way to guarantee the backup pool will not consider stale shares as rejects.  

I've also mined some fixed-difficulty pools that exhibit high flux in accepted hashes that only even out after a few days.  if someone is renting 72hours that's not a problem, but the hashrate will never be correct if someone goes fixed-diff for a short lease (e.g. 6 or 12 hours)

I occasionally get the following message from the LRP:  "WARNING Speed buffer filled.  Speed reporting may be incorrect.", so i am concerned that leaserig may not be recording the same hashrate experienced at the pool.  one of my rigs is doing this right now, and this is with a full restart of LRP and sgminer:



I try my best to give the people that lease my equipment a good mining experience, and i underrate my rigs.  However, i've seen LRP hashrate inaccurate when compared to my sgminer outputs.  I compensate any reduction in performance by extending the lease.  I do everything i can to hook the renter up, but that's not reflected in a thumbs up, thumbs down system.   

I can appreciate the intention:  some people do inflate their hashrates and this must add up to an annoying number of feedback problems and helpdesk tickets.  however, when someone clicks on the "hire" button of an underperforming rig, the disclaimer "Are you sure you want to hire an Under Performing Rig?" is a real disincentive to rent.  i understand the problems the business is trying to address, but this seems like a harsh way to do it.  

So if I have a renter that uses a bad pool, and my hash rate suffers, that's my fault? I should be rated as underperforming for the action of a renter?

My concern is real. I have this now, despite trying to contact the renter with info on how to select pools for better performance.

So how does this improve the accuracy of the info on the site? It just muddies it in a different way.