[ANN] LEASERIG.NET - rent&hire Quark hashing power!

[ebliever]

You can ignore it, if the pools are ok. I am sending these mails if something fails when trying to set proper pools.

So the email goes to both the renter and the rig owner? Any way to tell if the problem is on our (rig) end or something the renter is doing wrong?

In most cases is due to wrong pool (missing port or something like that). I have implemented additional checks and I don't permit setting pools with no ports anymore, but some people still have saved wrong preconfigured pools.

Second most case is failed result from cgminer - yes, cgminer can sometimes fail or truncate data.

Third reason could be slow response of cgminer when connecting to new pools and if the new pool isn't connected fast enough, old pool won't be removed and mail will be sent.

Thanks! I appreciate your responsiveness. I do have one more question: If a renter wants to rehire a rig, do they automatically get it at the same rate they originally hired it at? Or do they have to accept whatever current rate you have set? (Minus the discount we set for rehires, I guess.)

Reason I ask is that I had the bad timing to snag a Fill order at .00825 this morning, minutes before I saw a whole slew of rigs get hired up (presumably for Spaincoin mining) at much higher rates. Once I get off my current lease I'd like to join in the fun, so I'm just trying to figure if it is safe for me to allow rehiring or if I should disable it (presumably by setting it to allow rehires at "0" hours ahead of time.)

[salsamoves]

You can ignore it, if the pools are ok. I am sending these mails if something fails when trying to set proper pools.

So the email goes to both the renter and the rig owner? Any way to tell if the problem is on our (rig) end or something the renter is doing wrong?

In most cases is due to wrong pool (missing port or something like that). I have implemented additional checks and I don't permit setting pools with no ports anymore, but some people still have saved wrong preconfigured pools.

Second most case is failed result from cgminer - yes, cgminer can sometimes fail or truncate data.

Third reason could be slow response of cgminer when connecting to new pools and if the new pool isn't connected fast enough, old pool won't be removed and mail will be sent.

Thanks! I appreciate your responsiveness. I do have one more question: If a renter wants to rehire a rig, do they automatically get it at the same rate they originally hired it at? Or do they have to accept whatever current rate you have set? (Minus the discount we set for rehires, I guess.)

Reason I ask is that I had the bad timing to snag a Fill order at .00825 this morning, minutes before I saw a whole slew of rigs get hired up (presumably for Spaincoin mining) at much higher rates. Once I get off my current lease I'd like to join in the fun, so I'm just trying to figure if it is safe for me to allow rehiring or if I should disable it (presumably by setting it to allow rehires at "0" hours ahead of time.)

The rate is the current rate you have set less any discount. I vary mine to keep in line but give rehires a discount.

[ebliever]

Excellent! Thanks, that makes sense. 

[ebliever]

OK, I have a hopefully not stupid question. Here is a copy and paste of the last 20 rentals as of 9:27 CST:

Scrypt rental history
Started    Rated price
(BTC/MH/day)    Rent time
(hours)    Amount
(BTC)    Mining rig rented
Sat Mar 15 03:24:41 CET 2014   0.00987778   72   0.08890000   DeltaVelorum (Scrypt 3.00 MH/s)
Sat Mar 15 03:22:15 CET 2014   0.01013675   72   0.05930000   Whiskey (Scrypt 1.95 MH/s)
Sat Mar 15 03:21:41 CET 2014   0.01125000   6   0.00540000   websystems2 (Scrypt 1.92 MH/s)
Sat Mar 15 03:40:27 CET 2014 (rehired)   0.01376170   1   0.00107800   Dexters1 (Scrypt 1.88 MH/s)
Sat Mar 15 02:58:41 CET 2014   0.01200000   6   0.00390000   scrypt007 (Scrypt 1.30 MH/s)
Sat Mar 15 02:58:07 CET 2014   0.01013333   12   0.00380000   ponsex01 (Scrypt 0.75 MH/s)
Sat Mar 15 02:48:15 CET 2014   0.00992806   24   0.02760000   EZ6 (Scrypt 2.78 MH/s)
Sat Mar 15 02:45:40 CET 2014   0.00123457   24   0.01000000   Mercedes1 (Scrypt 8.10 MH/s)
Sat Mar 15 02:40:27 CET 2014   0.01404255   1   0.00110000   Dexters1 (Scrypt 1.88 MH/s)
Sat Mar 15 02:28:46 CET 2014   0.01136891   6   0.00490000   BeefyRigUno (Scrypt 1.72 MH/s)
Sat Mar 15 02:27:16 CET 2014   0.01200000   24   0.01620000   railzrig1 (Scrypt 1.35 MH/s)
Sat Mar 15 02:25:49 CET 2014   0.01144444   24   0.03090000   litecoin1 (Scrypt 2.70 MH/s)
Sat Mar 15 02:24:41 CET 2014   0.01093333   24   0.02460000   Bareket1 (Scrypt 2.25 MH/s)
Sat Mar 15 02:23:23 CET 2014   0.01000000   72   0.04950000   FARM0 (Scrypt 1.65 MH/s)
Sat Mar 15 02:22:25 CET 2014   0.01003390   12   0.01480000   MoneyMaker3 (Scrypt 2.95 MH/s)
Sat Mar 15 02:21:28 CET 2014   0.00968085   72   0.08190000   EZ5 (Scrypt 2.82 MH/s)
Sat Mar 15 02:20:22 CET 2014   0.00938462   24   0.01220000   RockSolid1 (Scrypt 1.30 MH/s)
Sat Mar 15 02:10:46 CET 2014   0.01022222   6   0.00690000   Janikmakac2 (Scrypt 2.70 MH/s)
Sat Mar 15 01:40:36 CET 2014   0.01133333   12   0.01020000   EURig01 (Scrypt 1.80 MH/s)
Sat Mar 15 01:33:17 CET 2014   0.01410612   1   0.00720000   InvactusRig2 (Scrypt 12.25 MH/s)
Weighted average price for last 20 rentals: 0.00884185

My question is, how can that be the average when only one value in the list above is below the average? (That one looks like an unfortunate typo on someone's part! I suppose it could pull the average way down.)

UPDATE: I did the math, and get an unweighted average of 0.010643623 from the list above. The one low value could not possibly be weighted enough to influence the result much.

[djeZo]

Sat Mar 15 02:45:40 CET 2014   0.00123457   24   0.01000000   Mercedes1 (Scrypt 8.10 MH/s)

If you consider following facts, the weighted price is correct. Rig was rented for 24h and it had speed of 8.1.

[ebliever]

Ahh! I forgot to weight Mhash speed, I was weighting only the duration.

[pianowarrior]

Hi djeZo,

Sorry if this has been answered before.

the lease rig site adds a ":80" to the end of my entered stratums. Is there a workaround beyond communicating with the owner of the rig?

Thanks much

-PW

[djeZo]

Hi djeZo,

Sorry if this has been answered before.

the lease rig site adds a ":80" to the end of my entered stratums. Is there a workaround beyond communicating with the owner of the rig?

Thanks much

-PW

It adds default port if you don't add your own. Most of the issues regarding pools were due to wrong port settings, so I am enforcing port number (default 80 if you don't specify your own). Check out which port your pool is using and enter it and then it will work just fine.

[ExD]

Rented several rigs, actual rate on some of them is lower than what they write in description, 0.43->~0.3 real, I've seen one spike to 0.43 on that rig, it was luck I guess. Annoying to pay money for nonexistent power, Leaserig should measure past performance, adjust to average and charge accordingly, instead of relying on what miners declare.

[tw0r]

Rented several rigs, actual rate on some of them is lower than what they write in description, 0.43->~0.3 real, I've seen one spike to 0.43 on that rig, it was luck I guess. Annoying to pay money for nonexistent power, Leaserig should measure past performance, adjust to average and charge accordingly, instead of relying on what miners declare.

Good idea.
But did you try to write this to your rig provider? He can for example repay you a third or extend your lease for a third of time...
Most of us are solid guys...maybe some dont.

[djeZo]

I think everyone can see if the speed of the rig is actually what they advertise - hell, you don't only see current speed, but speed for the past 24h.

Auto adjusting declared speed to average speed over some period could have big negative effects - speed can sometimes be low due to bad pools implied by customers.

[ebliever]

I would also caution that the speed shown on Leaserig is almost surely low, at least in my experience. I've seen (in the rapidly scrolling Proxy window on a low diff coin) a momentary disconnect/connect that doesn't even register on CGminer, but it causes a big spike to 0 on the Leaserig stats page. Likewise, shutting down the miner and restarting it, within 10 seconds, causes a 3-4 minute "outage" to show up on Leaserig. I've seen this sort of exaggeration consistently. I think the 24-hour graph doesn't show it as severely, but it is still there.

Somehow letting Leaserig calculate the hashing power of a rig sounds good to me in theory, but I'd want to be sure it is fair and can't be gamed somehow. At least right now renters can review the stats on a rig's performance before they rent. And like someone else said, just reach out to the rig owner if something goes wrong. They should be responsive to those types of things.

[ExD]

I think everyone can see if the speed of the rig is actually what they advertise - hell, you don't only see current speed, but speed for the past 24h.

Auto adjusting declared speed to average speed over some period could have big negative effects - speed can sometimes be low due to bad pools implied by customers.

Ok, I'll rent rigs with consistent rate then. I understand that it could be a bad idea, but misleading description is not something I want to see. Otherwise service is great so far.

I would also caution that the speed shown on Leaserig is almost surely low, at least in my experience. I've seen (in the rapidly scrolling Proxy window on a low diff coin) a momentary disconnect/connect that doesn't even register on CGminer, but it causes a big spike to 0 on the Leaserig stats page. Likewise, shutting down the miner and restarting it, within 10 seconds, causes a 3-4 minute "outage" to show up on Leaserig. I've seen this sort of exaggeration consistently. I think the 24-hour graph doesn't show it as severely, but it is still there.

Somehow letting Leaserig calculate the hashing power of a rig sounds good to me in theory, but I'd want to be sure it is fair and can't be gamed somehow. At least right now renters can review the stats on a rig's performance before they rent. And like someone else said, just reach out to the rig owner if something goes wrong. They should be responsive to those types of things.

There are some issues with the graph, catched too: pool reported no activity from miner for 5 minutes, on leaserig graph it was presented like down spike in hash rate from 3 to 2 Mh/s, I've seen several spikes like that with the duration 10, 20 minutes, 3 to 2Mhs, 3 to 1Mhs, I can interpret it differently, from cards misbehaving to rig went offline.

[mpdas108]

I think everyone can see if the speed of the rig is actually what they advertise - hell, you don't only see current speed, but speed for the past 24h.

Auto adjusting declared speed to average speed over some period could have big negative effects - speed can sometimes be low due to bad pools implied by customers.

Ok, I'll rent rigs with consistent rate then. I understand that it could be a bad idea, but misleading description is not something I want to see. Otherwise service is great so far.

I would also caution that the speed shown on Leaserig is almost surely low, at least in my experience. I've seen (in the rapidly scrolling Proxy window on a low diff coin) a momentary disconnect/connect that doesn't even register on CGminer, but it causes a big spike to 0 on the Leaserig stats page. Likewise, shutting down the miner and restarting it, within 10 seconds, causes a 3-4 minute "outage" to show up on Leaserig. I've seen this sort of exaggeration consistently. I think the 24-hour graph doesn't show it as severely, but it is still there.

Somehow letting Leaserig calculate the hashing power of a rig sounds good to me in theory, but I'd want to be sure it is fair and can't be gamed somehow. At least right now renters can review the stats on a rig's performance before they rent. And like someone else said, just reach out to the rig owner if something goes wrong. They should be responsive to those types of things.

There are some issues with the graph, catched too: pool reported no activity from miner for 5 minutes, on leaserig graph it was presented like down spike in hash rate from 3 to 2 Mh/s, I've seen several spikes like that with the duration 10, 20 minutes, 3 to 2Mhs, 3 to 1Mhs, I can interpret it differently, from cards misbehaving to rig went offline.

One important thing to note is, where are you looking to get a report of the hashrate for the rigs you rent. You should NOT be looking at the pool stats, as the reported rate on the pool doesn't not take into account rejects, discards, stales, etc. it only reports accepted submitted shares, so generally that amount fluctuates a lot. And as was noted before the LeaseRig stats can bill a little wonky some times, but generally are ok, many times my rigs show a lesser "24 average" than they actually hash at because of pool problems, down times, etc. Your best information is a 20 - 60 minutes report from LeaseRig.. That is my opinion on the matter.

[ExD]

I've contacted rig provider, cgminer shows constant 0.43 rate on his side, it might be some configuration issue with LRP, I've checked other rigs that use proxy, hash rate tends to fluctuate heavily on some of them, while remains consistent on others.

[djeZo]

If provider is using LRP with share calculated speed (default), then speed will fluctuate.

[byt411]

Can I suggest a feature? Can we have actual passwords for our accounts that we can set?

[ebliever]

Has anyone else who filled that current order for 0.00806 BTC/Mhash (was max 4 hours, now 3), received payment for it? I took it for 4 hours and the system accepted it normally and switched my rig over to it, but I never received payment, either in BTC or DOGE. That's the first time that has happened.

[bitlynx]

Clearly visible, that LeaseRig gives much better profit than multipools: http://leaserig.net/index.jsp?page=stats&t=0

You should really post a link to this graph on your main page (if it's there, I totally failed to see it.)

[Prominence]

I can't get solo mining to work.

I've been downloading the wallet, editing the .conf file
Using XXLcoin to test:

listen=1
daemon=1
server=1
rpcuser=xxx
rpcpassword=xxx
rpcport=50771
rpcallowip=*
rpcconnect=127.0.0.1
port=50772
addnode=209.208.111.233
addnode=92.234.241.91
addnode=195.138.68.2151
addnode=222.215.224.169
addnode=1.193.32.73
addnode=212.50.27.21

Pointed miner to: http://[my public address here]:50771

It's not a firewall issue, not connecting even with firewall disabled.
What am I doing wrong?