Trongersoll
|
|
June 28, 2013, 01:07:49 AM |
|
man, i just saw the latest graph. my daily performance was real suckage today. even dragged my 7 day average way down.
|
|
|
|
bitzip
Newbie
Offline
Activity: 53
Merit: 0
|
|
June 28, 2013, 01:23:33 AM |
|
man, i just saw the latest graph. my daily performance was real suckage today. even dragged my 7 day average way down. Today sucked big time. The pool luck was very low. Hey I spent some bitcoin on mining hardware that I'd like to earn back. Everyone in the bitcoin mining community needs to stop mining for a few weeks, so I can earn my coins back. OK
|
|
|
|
RoboCoder
|
|
June 28, 2013, 03:55:22 AM |
|
Wow. 37 BTC block? 12 BTC in fees!! That was nice.
Somebody must have screwed up!
|
|
|
|
bspurloc
|
|
June 28, 2013, 03:56:12 AM |
|
man, i just saw the latest graph. my daily performance was real suckage today. even dragged my 7 day average way down. Today sucked big time. The pool luck was very low. Hey I spent some bitcoin on mining hardware that I'd like to earn back. Everyone in the bitcoin mining community needs to stop mining for a few weeks, so I can earn my coins back. OK that is waht syn floods are for derpa!
|
|
|
|
MinermanNC
Legendary
Offline
Activity: 2198
Merit: 1000
|
|
June 28, 2013, 03:56:42 AM |
|
man, i just saw the latest graph. my daily performance was real suckage today. even dragged my 7 day average way down. Today sucked big time. The pool luck was very low. Hey I spent some bitcoin on mining hardware that I'd like to earn back. Everyone in the bitcoin mining community needs to stop mining for a few weeks, so I can earn my coins back. OK I finally left my beloved Shush's pool a week ago, and moved on as planned and converted all my gpu miners to Litecoin. I only wish I had done it a month ago now. The earnings rate for me is almost 40% higher than were I was at in here just a little over a week ago. So now I sit and wait for my asics,,,, one day maybe, once they arrive I will be back at 45 g/hash, but even then I fear that will not be enough by the time I get em in? But like Arnold says "Ill be back" lol,,,,,
|
*BTC: 1DiR25SPo84sThzTATr27EZEQZLt6hv6tG
|
|
|
JoelKatz
Legendary
Offline
Activity: 1596
Merit: 1012
Democracy is vulnerable to a 51% attack.
|
|
June 28, 2013, 03:59:40 AM |
|
Maybe I'm missing something, but it seems that this payout strategy is obviously vulnerable to hopping.
If there's any time a miner can identify where he gets a higher payout than he would get solo mining, the pool is vulnerable to hopping. Obviously, the payouts can't always be better than solo mining. So if it's sometimes better, it must also sometimes be worse. If a miner can tell when it's better, he can mine only when it's better.
Say it's the very beginning of the round. If I mine a block before anyone else submits a share, I get the whole 25 BTC. So the payout at the very beginning of a round is as good as solo mining. And if I don't mine a block and someone else does very shortly after me, I get a non-zero payout. Thus mining at the beginning of a round is better than solo mining.
I must be missing something because this is pretty obvious.
|
I am an employee of Ripple. Follow me on Twitter @JoelKatz 1Joe1Katzci1rFcsr9HH7SLuHVnDy2aihZ BM-NBM3FRExVJSJJamV9ccgyWvQfratUHgN
|
|
|
|
5120-01-518-6126
Full Member
Offline
Activity: 174
Merit: 100
< My mining rig >
|
|
June 28, 2013, 04:58:41 AM |
|
Yeah, a 942 BTC transaction.
|
|
|
|
|
gourmet
|
|
June 28, 2013, 09:25:45 AM Last edit: June 28, 2013, 07:31:35 PM by gourmet |
|
I am curious about the large fluctuations in the total network hashrate. I mean 20,000 GH/s is the size of Slush's entire pool, how does that much compute power come and go so quickly? Its like someone with 40 BFL Mini Rigs is dropping in and out of the network.
Network hashrate is calculated from the count of blocks found, there's no other way to determine it. But block frequency varies according to the luck. As we can't determine current luck, we have to take it into account always being 100 %. Sure this is not true, and so we are observing variations in network hashrate that don't exist in fact. Certainly I don't want to say there aren't any variations. They are. But I can't tell how big they really are. Can someone go further and calculate the probable contribution of this effect to the total variation? - Miners' workers can tell their hashrate exactly.
- The pools calculate their hashrates from shares of difficulty 1 or more. With ASICs comming, there'll be more of "more", and the accuracy will go down. Well only absolutely, maybe, and the relative accuracy can be maintained, as the hashrate increases also.
- The whole network has no means to determine its total hashrate other than from the blocks found, as stated above. [edit:] With increasing difficulty, variations will increase and the accuracy will continue going down.
[edted after n0creativity's reply]: The pools get 2 32 less haashes from the miners than the miners themselves calculate. (Or even less, when client difficulty set to > 1.) But they don't obtain them equaly in time, rather with variable frequency according to the luck. The whole network only gets blocks of current difficulty from both pools and solo miners. (So currently it gets other 19M times less hashes than the pools do.) There's nothing like shares at the network level. Shares' only purpose is to enable reward distribution among pools' clients. And again, luck (variation) applies.
|
|
|
|
trasla
|
|
June 28, 2013, 10:47:59 AM |
|
Maybe I'm missing something, but it seems that this payout strategy is obviously vulnerable to hopping.
If there's any time a miner can identify where he gets a higher payout than he would get solo mining, the pool is vulnerable to hopping. Obviously, the payouts can't always be better than solo mining. So if it's sometimes better, it must also sometimes be worse. If a miner can tell when it's better, he can mine only when it's better.
Say it's the very beginning of the round. If I mine a block before anyone else submits a share, I get the whole 25 BTC. So the payout at the very beginning of a round is as good as solo mining. And if I don't mine a block and someone else does very shortly after me, I get a non-zero payout. Thus mining at the beginning of a round is better than solo mining.
I must be missing something because this is pretty obvious.
Mining at the beginning of a round is only better _if_ a block is found quick, because if not, the exponential rise of score per share submitted will make your early shares obsolete quite fast. If you could predict how long a round takes, you could just mine in the short ones. But switching to solo or another pool after a certain time in the round will very likely result in no reward (or a very very small) for the round, since shares submitted by others after you leave will get a much higher score for them. Besides, in your example, if someone else submits a share and you mine a block very shortly after, you only get part of it - thats not better than solo.
|
|
|
|
ibfr33k
Member
Offline
Activity: 75
Merit: 10
|
|
June 28, 2013, 12:32:54 PM |
|
243758 is not ours
|
I'm a noob just starting, all donations are welcome. 13DXKRXQncUnWAFtemSwNH7boRZfEfsg5a
|
|
|
n0creativity
Member
Offline
Activity: 65
Merit: 10
|
|
June 28, 2013, 04:05:22 PM |
|
I am curious about the large fluctuations in the total network hashrate. I mean 20,000 GH/s is the size of Slush's entire pool, how does that much compute power come and go so quickly? Its like someone with 40 BFL Mini Rigs is dropping in and out of the network.
Network hashrate is calculated from the count of blocks found, there's no other way to determine it. But block frequency varies according to the luck. As we can't determine current luck, we have to take it into account always being 100 %. Sure this is not true, and so we are observing variations in network hashrate that don't exist in fact. Certainly I don't want to say there aren't any variations. They are. But I can't tell how big they really are. Can someone go further and calculate the probable contribution of this effect to the total variation? Miners' workers can tell their hashrate exactly. The pools calculate their hashrates from shares of difficulty 1 or more. With ASICs comming, there'll be more of "more", and the accuracy will go down. Well only absolutely, maybe, and the relative accuracy can be maintained, as the hashrate increases also. The whole network has no means to determine its total hashrate other than from the blocks found, as stated above. [edit:] With increasing difficulty, variations will increase and the accuracy will continue going down. Thanks for the "Oh yeah.... DUH" moment, gourmet. Haha! That makes sense, I guess I thought the network as a whole was aware of every share submitted by miners regardless if they are solo or pool. Learn something new every day. I guess I need to read whitepaper from satoshi again... and pay more attention this time. Happy Friday to everyone, btw. And a shout out to all the Chicago Blackhawk fans on here (if any)! Lord Stanley's Cup has returned to its rightful place!
|
|
|
|
gourmet
|
|
June 28, 2013, 05:04:26 PM Last edit: June 28, 2013, 07:19:10 PM by gourmet |
|
Thanks for the "Oh yeah.... DUH" moment, gourmet. Haha! That makes sense, I guess I thought the network as a whole was aware of every share submitted by miners regardless if they are solo or pool. Learn something new every day. I guess I need to read whitepaper from satoshi again... and pay more attention this time. Happy Friday to everyone, btw. Thanks. I've just made some addition and formating to the original post, for even better understandability, I hope. Yeah, the link.
|
|
|
|
bspurloc
|
|
June 28, 2013, 06:38:08 PM |
|
243758 is not ours stinkers!
|
|
|
|
gbx
|
|
June 28, 2013, 08:06:22 PM |
|
this is not directed at any one person but in general to the @AMD 7870 posts above: I just recently upgraded my gaming rig to 7870 ghz edition (hit a 185$ deal on newegg ~2 weeks ago?) and i run it on win7 latest drivers and I get ~405 Mh/s average just using guiminer, which everyone loves to hate it seems, but it runs fine with latest drivers... so I am happy. I am more of a gamer than a miner tho, so my priorities are skewed.
for people who are more knowledgeable i am wondering: my gpu clock is set at 1100. what kind of Mh/s would I be getting if I did do a driver-downgrade and ran cgminer instead...? would it really be so much higher than the ~405Mh/s that i currently get with guiminer?
You should be able to squeeze more out of it. Check out cgminer and ditch guiminer. 1 http://stratum.bitcoin.cz:3333 74.0 c 99% 444.53 Mh/s 11751 / 27 0.23% 7800 Series 69% (2605) 1185 Mhz 1035 Mhz 1.25v
|
|
|
|
JoelKatz
Legendary
Offline
Activity: 1596
Merit: 1012
Democracy is vulnerable to a 51% attack.
|
|
June 29, 2013, 04:59:03 AM |
|
Mining at the beginning of a round is only better _if_ a block is found quick, because if not, the exponential rise of score per share submitted will make your early shares obsolete quite fast. No, that's not true. Mining at the beginning of a round is better no matter what. It's better because if you find a block before anyone else submits a share, you get the same reward as if you were solo mining and if a block is found shortly after you submit a share, you get a non-zero payout. Thus mining at the very beginning of a round is better than solo mining and clearly it cannot always be better than solo mining. All you must do to show that a pool is vulnerable to hopping is show that there is some point that an attacker can identify at which the expected return exceeds the expected return for solo mining. If I understand this payout method correctly, it has such a point -- before the first share is submitted in a round. If you could predict how long a round takes, you could just mine in the short ones. But switching to solo or another pool after a certain time in the round will very likely result in no reward (or a very very small) for the round, since shares submitted by others after you leave will get a much higher score for them. That's all true, but has nothing to do with anything. Sure, there are lots of ways one could hop pools that don't work. The question is whether there are any ways that do. Besides, in your example, if someone else submits a share and you mine a block very shortly after, you only get part of it - thats not better than solo. I agree. That's why the pool is vulnerable to hopping. There are good times to mine and worse times to mine. (Assuming I correctly understand how the pool pays out, which I hope I don't, since this is really an obvious flaw.)
|
I am an employee of Ripple. Follow me on Twitter @JoelKatz 1Joe1Katzci1rFcsr9HH7SLuHVnDy2aihZ BM-NBM3FRExVJSJJamV9ccgyWvQfratUHgN
|
|
|
trasla
|
|
June 29, 2013, 07:12:54 AM Last edit: June 29, 2013, 07:28:02 AM by trasla |
|
Okay, yeah, sure, if you manage to submit the first share, thats always good. But if somehow someone else just got some shares in on his own before your first share in the round reaches the server, your plan will not work any more. So you should tell me how to make sure no one calculates and submits a share faster than you, and then tell me how big the advantage of a single share with better average payout is. You would get one of those per round.
Even if the very first share you calculate after getting provided with work for the new round is a winning one - i bet there will ne other shares reported to the server when yours is verified, and with a high probability. So your average payout for submitting the winning share will be far below solo mining. Solo mining it will always be 25 + x, in the pool, if 10 other workers submitted their first difficulty 1 one share at the same, you get far less.
|
|
|
|
Tsunamirain
Full Member
Offline
Activity: 210
Merit: 100
Incakoin= Incagold
|
|
June 29, 2013, 07:34:55 AM |
|
Problems?
|
|
|
|
gourmet
|
|
June 29, 2013, 07:57:17 AM Last edit: June 29, 2013, 08:24:46 AM by gourmet |
|
Mining at the beginning of a round is better no matter what. It's better because if you find a block before anyone else submits a share, you get the same reward as if you were solo mining and if a block is found shortly after you submit a share, you get a non-zero payout. Thus mining at the very beginning of a round is better than solo mining and clearly it cannot always be better than solo mining. All you must do to show that a pool is vulnerable to hopping is show that there is some point that an attacker can identify at which the expected return exceeds the expected return for solo mining. If I understand this payout method correctly, it has such a point -- before the first share is submitted in a round. Besides, in your example, if someone else submits a share and you mine a block very shortly after, you only get part of it - thats not better than solo. I agree. That's why the pool is vulnerable to hopping. That's why it is not. Besides, in your example, if someone else submits a share and you mine a block very shortly after, you only get part of it - thats not better than solo.
That's the point. You have to take into account all possibilities. Consider the first two shares in the round, one of them being the block. - You 1st, block, other 2nd, no block
- You 1st, no block, other 2nd, block
- Other 1st, block, you 2nd, no block
- Other 1st, no block, you 2nd, block
When you find a block, your payout is worse than in solo, as you have to share your reward. When you don't find, you're better, you get some share on the reward. Together, it's like solo. You can't just select one of the possibilities and omit the others. They're all equaly (im)probable.
|
|
|
|
|