Also, a few web interface bugs are being fixed now. (Weeks now display in order!
) 
Topic: [ANN] CoinLab Protected Pool - page 37. (Read 97702 times)
Monday Payouts have been sent!
Also, a few web interface bugs are being fixed now. (Weeks now display in order!)
Also, a few web interface bugs are being fixed now. (Weeks now display in order!
) Another thing which is not really clear to me: If doing HPC work and $/GH/s/day is below 2.5, will the HPC workunits be deducted from my loyalty points? Or do loyalty points only work together with bitcoin mining?
We may choose to overpay in some circumstances to incentivize certain behaviors: for example, high uptime or a bonus to all NVIDIA cards. We don't want to be restricted in our ability to give bonuses (and you should want us to be able to overpay without restriction), so any price above the price floor that we pay when you would have earned less than the price floor counts as redeeming a loyalty point.
Quote
If no, at which point is the $/GH/s/day calculated in your current model? In the first step, when calculating the "base value" (this would mean your "earnings protection" will kick in as soon as possible) or in the last step, after adding all bonuses (HPC bonus, AMD/NV bonus)?
Anytime the 100% PPS rate for Bitcoin mining is below $0.00012427 PPS, you'll redeem Loyalty Points and receive at least $0.00012427 PPS. Neither bonuses or fees are factored into this (we calculate at 100%, not 95%, and HPC or other bonuses do not factor in).
Quote
Oh, and another question: Will I always be mining bitcoins if there is no HPC work available? I don't know the market, but I could imagine a 5850/5870 (or think about cards like the 5770...) is unsuitable for most HPC tasks.
For the foreseeable future, yes. Our 'default' setting will always choose the work that earns our miners the most money, so if a 5850 is more valuable performing Bitcoin mining than HPC work, we'll have you mine Bitcoin. We will also have manual controls available for controlling which jobs you want your GPU to perform, if you want to manage this yourself.
Question for ya CL...
If BTC dropped below 2.5$/GH .. RIGHT NOW...
would you be willing to pay our garunteed rate at this point in time? Or .. how would that work..
If BTC dropped below 2.5$/GH .. RIGHT NOW...
would you be willing to pay our garunteed rate at this point in time? Or .. how would that work..
If mining earnings drop below $2.5 / GH/s / day right now, you'll start redeeming Loyalty Points now, earning the price floor ($0.00012427 PPS), with whatever miner you choose.
Our custom client will be out in about two weeks, and once its released, we'll probably give a few week grace period before we'll require it to redeem Loyalty Points.
question about loyalty points:
When we do redeem the points, how many shares do we have to submit per day to equal 1gh?
question about loyalty points:
When we do redeem the points, how many shares do we have to submit per day to equal 1gh?
You've got much bigger fish to fry than starting yet another pool. Keep it (your business model) clean and simple, we have enough pools with strange Byzantine rules (cough, BonusPool, cough). This thread is already getting filled with ZOMGPonziScam drama.
I agree, I should definitely not be giving added value to miners that isnt available to them from the other pools. Shame on me.
I would love to understand how you got to the byzantine part without thread crapping here so if you wish to elaborate on that feel free to pm or post in the bonuspool thread.
Oversensitive much Clipse? I'd love to post in your BonuScamPool thread, but you locked it a long time ago. Cute!
You sure have done a good job "giving added value to miners that isnt available to them from the other pools."
Hey, maybe you can sell CoinLab your PenaltyPool software. It has decent stats and you don't seem to be using it!
ah, so we are fucked till that comes out then.... =/
If it ever comes out... lol
If it ever comes out... lol
See OP: "Loyalty Point credits can only be redeemed through our custom mining client."
Question for ya CL...
If BTC dropped below 2.5$/GH .. RIGHT NOW...
would you be willing to pay our garunteed rate at this point in time? Or .. how would that work..
If BTC dropped below 2.5$/GH .. RIGHT NOW...
would you be willing to pay our garunteed rate at this point in time? Or .. how would that work..
Any news on how you will pay out on Nvidia compared to AMD/ATI hardware? As NV is dead slow when mining bitcoins but better for most HPC work, will there be some kind of compensation?
I'm thinking about replacing my two 580 GTX in my desktop computer with something (much) less power hungry. Unless you have a model where it makes sense to use such video cards, then I'll keep them.
(...)I'm thinking about replacing my two 580 GTX in my desktop computer with something (much) less power hungry. Unless you have a model where it makes sense to use such video cards, then I'll keep them.
Eventually we want to make a market, so bonus rates will be set based on supply and demand. We'd love for miners to be able to set, "My power costs X. I'm willing to do commercial HPC work for 1.3 X. I'm willing to do Academic work units for as low as 1.05 X. If no work at that rate is available, mine Bitcoins. If mining Bitcoins would earn less than 1.05 X, sleep." Then, our software will figure out which jobs to do based on your ruleset, and automatically switch between them for you to maximize profit.
(...)
If no, at which point is the $/GH/s/day calculated in your current model? In the first step, when calculating the "base value" (this would mean your "earnings protection" will kick in as soon as possible) or in the last step, after adding all bonuses (HPC bonus, AMD/NV bonus)?
Oh, and another question: Will I always be mining bitcoins if there is no HPC work available? I don't know the market, but I could imagine a 5850/5870 (or think about cards like the 5770...) is unsuitable for most HPC tasks.
Something is happening at the main site, for the first time I can see a fairly approximation of my hasrate. It always used to be a bit lower (like others reported)
The announcement is there for some time but only now I see some results.
Do you guys see it?
Edit: Aaaaaand it's gone.
The announcement is there for some time but only now I see some results.
Do you guys see it?
Edit: Aaaaaand it's gone.
Just a heads up, pool hashrate has jumped up a bit today .
We're putting up another frontend now, but you may notice a bit of latency for the next hourish.
Thanks for helping us grow!
. We're putting up another frontend now, but you may notice a bit of latency for the next hourish.
Thanks for helping us grow!
I'm not sure if what i'm experiencing is a problem. But the estimated hashrate from your pool is really low for me.
I'm getting 7% lower hash rate than what it should be. For example, Its 700Mh/s less with 10Gh/s than mining at other pool. Is it the estimated hashrate the 95% of my total contributed hashrate? Do the number of shares i'm seeing before or after the 5% fee ?
Also do you have more details in stats in the working?
where do i check my points?
its the weekend, so i dont think they are around:
All very good questions.
hashrate does report low, but shares are submitted normally. if you use cgminer, have some backup pools and you will get about 2000 bleeding shares for every about every 60k (see my test about share submissions)
We need stat porn really bad, but they are concentrating on the backend mostly.
points are equal to shares submitted.
Just a heads up, pool hashrate has jumped up a bit today .
We're putting up another frontend now, but you may notice a bit of latency for the next hourish.
Thanks for helping us grow!
. We're putting up another frontend now, but you may notice a bit of latency for the next hourish.
Thanks for helping us grow!
I'm not sure if what i'm experiencing is a problem. But the estimated hashrate from your pool is really low for me.
I'm getting 7% lower hash rate than what it should be. For example, Its 700Mh/s less with 10Gh/s than mining at other pool. Is it the estimated hashrate the 95% of my total contributed hashrate? Do the number of shares i'm seeing before or after the 5% fee ?
Also do you have more details in stats in the working?
where do i check my points?
Just a heads up, pool hashrate has jumped up a bit today .
We're putting up another frontend now, but you may notice a bit of latency for the next hourish.
Thanks for helping us grow!
. We're putting up another frontend now, but you may notice a bit of latency for the next hourish.
Thanks for helping us grow!
Why you using such an outdated version of cgminer?
2 reasons.
1. i tried 2.7.? and it was not stable on my windows with bfl's rig
2. all my linux rigs are linuxcoin, and upgrading to clovis's bins are problematic, i have to use kano's linux bins.
point being, i have extremely good uptime. i have not been below 50gigs unless i had a power outage for many months.
Why you using such an outdated version of cgminer?
I have found that cgminer 2.7.6 is very stable and is better able to keep rigs full of work. I would recommend to anyone to upgrade to 2.7.6 if you are using cgminer. I have done this for my entire farm and have seen good improvements.
+1 ( also 2.7.6 works great doing 99.90%@btcguild pool day in day out with xubuntu12.4)
Totals *,***.** MH/s shares 3247443 (99.90%)
Why you using such an outdated version of cgminer?
I have found that cgminer 2.7.6 is very stable and is better able to keep rigs full of work. I would recommend to anyone to upgrade to 2.7.6 if you are using cgminer. I have done this for my entire farm and have seen good improvements.
Never touch a running system... ? 
Why you using such an outdated version of cgminer?
coinlab vs ozcoin pool test with identical rigs
test ran ~24.3 hours
miner9 shares submitted to coinlab:
miner10 shares submitted to ozco:
because i was using screen and ssh, the cgminer summary scrolled up where i could not copy it. sorry, i have to assume the other accepted shares went to my other pools, or even to my solo backup. (btw, i have found 3 blocks this year(2 for me, 1 for a pool) with bleeding shares like this)
test ran ~24.3 hours
miner9 shares submitted to coinlab:
miner10 shares submitted to ozco:
| rig | rig accepted | pool valid | pool invalid |
| miner9 | 58885 | 56,340 | ? |
| miner10 | 58628 | 58,436 | 78 |
because i was using screen and ssh, the cgminer summary scrolled up where i could not copy it. sorry, i have to assume the other accepted shares went to my other pools, or even to my solo backup. (btw, i have found 3 blocks this year(2 for me, 1 for a pool) with bleeding shares like this)
Code:
cgminer version 2.3.6 - Started: [October 10, 2012, 9:49 pm] Rig:miner9
miner9
(5s):2899.86 (avg): 2898.42 Mh/s | H: 115.25 Q:35227 A:58885 R:43 HW:0 E:?% U:40.12/m
TQ:? ST:93 SS:? DW:5817 NB:294 LW:194688 GF:18 RF:67
Connected to http://pool.coinlab.com:8332 with LP as user ?
Value:
GPU 0: 71.0C 2649RPM 41% 112 | 362.1/362.6Mh/s | 98% | 800Mhz 300Mhz 1.05V A:7334 R:8 HW:0 U:5.00/m I: 7
GPU 1: 72.5C 2649RPM 41% 114 | 362.2/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:7311 R:7 HW:0 U:4.98/m I: 7
GPU 2: 70.5C 3013RPM 48% 119 | 362.0/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:7385 R:8 HW:0 U:5.03/m I: 7
GPU 3: 68.0C 3013RPM 48% 116 | 362.2/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:7508 R:3 HW:0 U:5.12/m I: 7
GPU 4: 70.5C 2759RPM 42% 113 | 362.8/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:7199 R:2 HW:0 U:4.90/m I: 7
GPU 5: 69.5C 2759RPM 42% 112 | 362.8/362.3Mh/s | 98% | 800Mhz 300Mhz 1.05V A:7307 R:4 HW:0 U:4.98/m I: 7
GPU 6: 67.5C 3171RPM 50% 118 | 362.8/362.2Mh/s | 98% | 800Mhz 300Mhz 1.05V A:7455 R:7 HW:0 U:5.08/m I: 7
GPU 7: 70.5C 3171RPM 50% 121 | 363.1/362.2Mh/s | 99% | 800Mhz 300Mhz 1.05V A:7386 R:4 HW:0 U:5.03/m I: 7
Code:
cgminer version 2.3.6 - Started: [October 10, 2012, 9:49 pm] Rig:miner10
miner10
(5s):2904.87 (avg): 2906.91 Mh/s | H: 119.25 Q:38835 A:58628 R:317 HW:0 E:?% U:39.94/m
TQ:? ST:24 SS:? DW:6532 NB:296 LW:155663 GF:11 RF:5
Connected to http://us.ozco.in:8332 with LP as user ?
Value:
GPU 0: 71.0C 3143RPM 51% 122 | 363.8/363.6Mh/s | 99% | 800Mhz 300Mhz 1.05V A:7248 R:38 HW:0 U:4.94/m I: 7
GPU 1: 67.5C 3143RPM 51% 119 | 363.0/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:7423 R:47 HW:0 U:5.06/m I: 7
GPU 2: 70.5C 3043RPM 49% 120 | 363.7/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:7285 R:31 HW:0 U:4.96/m I: 7
GPU 3: 70.0C 3043RPM 49% 119 | 362.8/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:7217 R:30 HW:0 U:4.92/m I: 7
GPU 4: 69.5C 2978RPM 49% 119 | 363.0/363.4Mh/s | 99% | 800Mhz 300Mhz 1.05V A:7409 R:35 HW:0 U:5.05/m I: 7
GPU 5: 70.0C 2978RPM 49% 119 | 362.7/363.4Mh/s | 98% | 800Mhz 300Mhz 1.05V A:7416 R:43 HW:0 U:5.05/m I: 7
GPU 6: 71.0C 2904RPM 50% 121 | 363.2/363.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:7304 R:41 HW:0 U:4.98/m I: 7
GPU 7: 66.5C 2904RPM 50% 117 | 362.8/363.3Mh/s | 99% | 800Mhz 300Mhz 1.05V A:7326 R:52 HW:0 U:4.99/m I: 7
We had two major load spikes today; the first was at 12:46pm Pacific, something in our servers borked so we had major getwork latency, up to 10seconds per request for a little bit.
The second was at 2:38pm pacific. About the same load; we did better, latency was maxing at 3.3 seconds. We'll post here when we're ready for round three -- hopefully you all can hammer things a bit more!
The second was at 2:38pm pacific. About the same load; we did better, latency was maxing at 3.3 seconds. We'll post here when we're ready for round three -- hopefully you all can hammer things a bit more!
Jump to: