Zangelbert is right. centralization is not going to occur.
Except it already has occurred. Anyone who hacks BTCGuild's systems or coerces its operator can happily reverse transactions that have reached six confirmations with a 21% success rate. 2 confirmations with a 53% success rate.
This is a direct result of the consolidation of hashpower which wouldn't exist absent it. It violates the security assumptions of the system.
and in other security systems suggests its not.
please elaborate on what you mean. this is too vague.
We don't iterate MD5 more when its security assumptions were broken, we replace it.
please provide some form of statistical evidence to support your claims.
See above.
We also have only about ~3000 stable inbound connection listening full nodes on the network according to the DNS seed crawlers.
well, i am. i run a solo mining operation and quite frankly, i find my efficiency to be much greater than running on the pools. i believe this is b/c i slavishly tend to my miners and fine tune them to my own specifications and performance measures. i have literally no down time in comparison to the pools which as you say are constantly being ddos or down for one reason or another. i constantly hear ppl complaining about their yields. well, they should solo mine. they'd be better off and we'd be more decentralized.
We agree here (amazing) and I've had a similar experience to you. I am currently mining on P2Pool and I am a substantial fraction of its hashrate, not because I care for the variance reduction, but because I support P2pool and want miners who do not want the high variance of solo mining to have options which don't require delegating their mining authority over to centralized pools.
another thing you're failing to account for is human motivation for a cause. motivation to be a part of a new system that puts control of a form of money into the hands of the ppl. this is another reason i solo mine; b/c i know its the right thing to do for decentralization and i would do it at a loss if i had to.
I have talked to easily a thousand people about Bitcoin. Hundreds of miners. I am a moderator in the mining subforum here. It is my experience that your views are highly unrepresentative— not unique, but I could basically count the number of similar views I've heard on one hand if I exclude the developers who only have a few GH/s of toy mining. If I thought your views were common I wouldn't be concerned.
i don't think you mine. if you did, you'd be amazed at cgminer. there are various modes built into the software that will allow instant shifting to backup pools just in case something goes wrong in the primary pool.
Funny, responding to a pool behaving maliciously is not among those "modes". Luke's bfgminer stuff actually will detect a number of cases of bad pool behavior (like attempting to fork a chain it had previously mined on) and switch away. Con is completely uninterested in merging that or any comparable feature.
I'm curious what poolserver daemon you run.
I cannot think of a single feature in cgminer which is associated more with network health than short term hasher income.
The failover functionality also unfortunately means that if you compromise one large pool you can DDOS the others in order to drive the hashrate up on your compromised pool.
bottom line is individual miners are vicious; they will switch pools at the first sign of trouble and won't tolerate any BS from the pool. operators better behave themselves or they will lose there participants quickly. they have no control over them.
This is objectively false. For example, when P2SH went active on the network, 50BTC was asleep at the switch and for over a month almost every block they mined was orphaned. They lost no hashrate during this time and today are the second largest public pool.
BTCguild, before they went PPS, went through a months long period of "bad luck" which had one in a zillion chance of actually occurring based on chance. The cause was never explained. Today its the largest pool.
Some popular "gui" mining software botches its failover and has hundreds of gigahash of wrong usernames and passwords show up on other pools when their primary fails. It goes unfixed for months/years. When a major pool goes down there is an observable loss in network hashrate, in spite of the really fantastic failover abilities in miner software— as you note, the pools are unreliable, and the miner software has great failover, and people don't avail themselves of it.
Pirate (and friends) ran an operation which was paying people to run their mining through them while concurrently running his ponzi operation and paid astronomic PPS rates as high as 150% PPS at times. He gave conflicting explanations of how the hashpower was being used, none of which could possibly have paid for those PPS rates. He
claimed to have a near majority of hashpower flowing through his systems at one point, the SEC reports over 23,000 BTC mined by his operation. Several other parties have also run large pay to hash operations and received large amounts of hashpower.
If a pool starts doing something evil will miners switch away from it — on the timescale of days, sure. Hours? No. I don't believe anyone can say with confidence that a day-scale malicious reorg event would be survivable.
Some of the most popular mining pools have been hacked over and over and over again, three and four times. Their reputation is fine. A large portion of hashers do not know or care.
you're very wrong here. as i said above, you wouldn't understand the mentality of a miner unless you're doing it or take pride in it.
What am I wrong about? BTCguild— months of 40% returns. #1 public pool. 50BTC, ~1 month of mostly orphaned blocks due to misconfiguration, second largest public pool. Slush, hacked multiple times thousands of btc stolen, third largest public pool. Together they are a simple majority of the hashpower.
P2Pool plus solo mining (assuming we exclude the large mining corporations like asicminer) are _no more_ than about 4.3% of the total hashpower, and probably less. The position you are expressing is, sadly, a demonstrably minority one.
he also understood the concept of bringing along the entire community early on as demonstrated by his magnanimity in the hard fork last Spring. he, being around high 40% of the network at the time, knew that he could not afford to leave merchants in the 0.7 fork. he would lose by winning. by winning, i mean mining all those extra blocks while on the 0.8 fork that had been created. we all know what happened. he backed off, gave up 25 block rewards mined on 0.8 for a loss, and returned to 0.7 to rejoin the merchants.
As someone who was deeply involved in the recovery of that event I can't say I agree with your characterization of the situation at all. A tiny minority of nodes had rapidly deployed new Bitcoin software, if not for the tremendous consolidation in hashpower— making that tiny minority have a large supermajority hashpower, the fork would have resolved naturally. The miners who's blocks were orphaned in the change were paid for their loss.
i keep 5-6 full nodes operational just to support the network.
You keep saying things that make me wish I could duplicate you, which is a very odd feeling because I have fairly low respect for you outside of your support for the network.
Still, I don't think that we can dispute that your experiences are unrepresentative: Solo mining is a tiny fraction of the hashpower.
we went thru this fear with gpu's and we are now going thru it with asic's. the outcome will be the same. self correction.
At one point we had something like 20,000 stable reachable full nodes. At one point I knew a dozen people who solo mined. You are not talking to some newbie here who is repeating the same old uninformed concerns, I never complained that gpus or asics themselves were a centralization problem.
BC.i webwallet users out number all time downloads of the reference software by a significant multiple. There are so many different ways that the Bitcoin economy and network has more single-point-of-failure risk than it did in the past now— and only a few ways that it appears to have less (more working client software, and viable exchanges are things I'd call out as having improved).
I am not saying that Bitcoin is doomed or that things will not improved. If I believed that I wouldn't waste my time working on it or discussing it with you here. But I think we need to frank and clear about the risks and concerns we have with the system if any correction is to happen prior to a devastating event which we may or may not survive.