Waiting for BTCmon update 
That's the reason for the change.
It should be ready soon.
Topic: [1050 TH] BitMinter.com [1% PPLNS,Pays TxFees +MergedMining,Stratum,GBT,vardiff] - page 275. (Read 837122 times)
October 20, 2012, 07:06:34 AM
That's the reason for the change.
It should be ready soon.
October 20, 2012, 06:50:55 AM
Quick website update.
Now you can use /api/users in addition to /api/users/USERNAME to retrieve your stats.
I think including the username in the URL is more RESTful, but this simplified URL makes it easier for 3rd party apps to add BitMinter support.
Now you can use /api/users in addition to /api/users/USERNAME to retrieve your stats.
I think including the username in the URL is more RESTful, but this simplified URL makes it easier for 3rd party apps to add BitMinter support.
Waiting for BTCmon update
October 20, 2012, 06:39:11 AM
Quick website update.
Now you can use /api/users in addition to /api/users/USERNAME to retrieve your stats.
I think including the username in the URL is more RESTful, but this simplified URL makes it easier for 3rd party apps to add BitMinter support.
Now you can use /api/users in addition to /api/users/USERNAME to retrieve your stats.
I think including the username in the URL is more RESTful, but this simplified URL makes it easier for 3rd party apps to add BitMinter support.
October 19, 2012, 01:52:29 PM
Gotta love HashPower's terms and conditions.
1. We do not accept responsibility for anything.
2. WARNING: Use at your own risk.
3. You must agree to 1 and 2.
1. We do not accept responsibility for anything.
2. WARNING: Use at your own risk.
3. You must agree to 1 and 2.
October 19, 2012, 01:06:20 PM
I did a lease yesterday that made a profit, roughly 1BTC and got 0.26BTC ish more than usual for 5 blocks
But it is totally a gamble, as I could have been unlucky and only 1 or 2 blocks generated in the 10 hour period.
I doubt I'll do it again, I'm a bit tighter with my money these days, gambling never ends well with me I'm just not that lucky
But it is totally a gamble, as I could have been unlucky and only 1 or 2 blocks generated in the 10 hour period.
I doubt I'll do it again, I'm a bit tighter with my money these days, gambling never ends well with me I'm just not that lucky
October 19, 2012, 12:29:56 PM
Absolutely.. Running a lease on hashpower is still a risk. I ran a short one a few days ago and solved a longish block for the pool while it ran, but I had not completed a shift with that power yet so ended up not earning anything on that block. After that we had a rather unlucky streak, so my investment in the lease was pretty much a total loss.
Ive tried a few small leases so far (never had a GPUMax account) and dont understand how anyone can come out ahead. I understand its a type of gamble but I dont understand the idea I guess.
October 19, 2012, 12:25:25 PM
Absolutely.. Running a lease on hashpower is still a risk. I ran a short one a few days ago and solved a longish block for the pool while it ran, but I had not completed a shift with that power yet so ended up not earning anything on that block. After that we had a rather unlucky streak, so my investment in the lease was pretty much a total loss.
October 19, 2012, 12:15:52 PM
My point was to say that the only affect it will have on each person is: It will decrease variance.
Yep. Some miners like seeing more blocks come in, while others don't like seeing their "pay per block" go down. But the way it really affects each miner is to reduce variance.
October 19, 2012, 09:37:49 AM
Anyway, I hope we can find something more useful to discuss today.
I'm not sure I do.
No news is good news. Just humming away with no problems.
October 19, 2012, 09:35:38 AM
But the way it really affects each miner is to reduce variance.
And if we didn't care about that we would all be solo mining. October 19, 2012, 09:32:09 AM
My point was to say that the only affect it will have on each person is: It will decrease variance.
Yep. Some miners like seeing more blocks come in, while others don't like seeing their "pay per block" go down. But the way it really affects each miner is to reduce variance.
October 19, 2012, 09:27:49 AM
kano is more right.
Not really. Because he said "no" to higher hashrate increasing the odds of finding blocks. That's clearly incorrect. Higher hashrate does increase your chance of finding blocks. Otherwise I'd be CPU mining right now.
But the end result of the increased hashrate is lower variance, that is true.
Anyway, I hope we can find something more useful to discuss today.
Yes the pool will expect to find more blocks due to the higher hash rate, but no one gains from that.
My point was to say that the only affect it will have on each person is: It will decrease variance.
Anything else is - well - pretty much irrelevant
October 19, 2012, 09:21:16 AM
kano is more right.
Not really. Because he said "no" to higher hashrate increasing the odds of finding blocks. That's clearly incorrect. Higher hashrate does increase your chance of finding blocks. Otherwise I'd be CPU mining right now.
But the end result of the increased hashrate is lower variance, that is true.
Anyway, I hope we can find something more useful to discuss today.
October 19, 2012, 09:13:22 AM
Looks like someone has leased a very large amount of shares from HashPower! Not complaining though as it increases our odds of more blocks
No, it just reduces variance.Yes, less variance.
Yes, better odds for more blocks per time.
Yes, less payout per share / work unit performed.
However, incrementally closer to PPS payouts but with transaction fees included in the payouts.
I see it as a net gain. (So long as the rejection rate stays low with the higher traffic.)
kano is more right.
October 19, 2012, 09:05:27 AM
Looks like someone has leased a very large amount of shares from HashPower! Not complaining though as it increases our odds of more blocks
No, it just reduces variance.Yes, less variance.
Yes, better odds for more blocks per time.
Yes, less payout per share / work unit performed.
However, incrementally closer to PPS payouts but with transaction fees included in the payouts.
I see it as a net gain. (So long as the rejection rate stays low with the higher traffic.)
October 19, 2012, 08:49:30 AM
Looks like someone has leased a very large amount of shares from HashPower! Not complaining though as it increases our odds of more blocks
No, it just reduces variance. October 19, 2012, 08:33:59 AM
Looks like someone has leased a very large amount of shares from HashPower! Not complaining though as it increases our odds of more blocks
October 18, 2012, 12:16:27 AM
@DrHaribo I have an idea for the status window on site. Is their a chance to implement current round how many blocks required to build etc and shares etc mined and how many are remaining to be done for that round and maybe some more real time status to show your percentages within the pool at what input you are giving towards to total pool like efforts and added to pool in current round etc
and some status like next round starting in and then counts down going of the rate of work been done currently by all members in pool ?
and some status like next round starting in and then counts down going of the rate of work been done currently by all members in pool ?
It already shows how many shares are mined. That's the "accepted" and "rejected" numbers. If you are logged in there will also be accepted and rejected numbers showing how much you did in the current round. Your efforts and total pool efforts would be the hashrate?
We can't show how much remains of the current round in work or time. Every proof of work is like a lottery ticket. We don't know how many more tickets we need before we find a winning one. It could take 1 second or 100 years to finish the round. So the CDF value will never reach 100%. In the livestats it will stop at 99.99% but in reality of course it will get more and more nines.
October 17, 2012, 05:49:13 PM
Weird, cgminer is still saying that rollntime is disabled even though my efficiency is at 577%.
https://i.imgur.com/EyMUZ.png
That shows the info regarding the last getwork receivedhttps://i.imgur.com/EyMUZ.png
So either there's a bug/thread run condition in my 'set flag for report' code or the pool's not always saying that for every getwork
If in the VERY unlikely event it is a thread run issue - then it should be extreeeeeeeeeemly rare and a refresh should certainly show it correctly
However stats reporting is certainly not a reason to lock access in critical sections of the code to resolve such rare problems.
The docs about 'stats' when I added it, say something to that effect
October 17, 2012, 04:31:01 PM
The only alternative that I am aware of..
Jump to: