Hi,
Like the look of p2pool..
I understand that p2pool is DOS resistant and HOP proof but can some one explain how it manages to mitigate the 51% attack ?
Is it because the sharechain it uses is so much faster that you would need 90% (or more..) of the hashrate to overrun that chain ?
So basically IF everyone was using p2pool we would only be vulnerable to a 90% attack ?
?
Like the look of p2pool..
I understand that p2pool is DOS resistant and HOP proof but can some one explain how it manages to mitigate the 51% attack ?
Is it because the sharechain it uses is so much faster that you would need 90% (or more..) of the hashrate to overrun that chain ?
So basically IF everyone was using p2pool we would only be vulnerable to a 90% attack ?
?
p2pool is kind of immune to the 51% attack problem because p2pool doesn't decide what goes in a block (what work to serve), individual users do. Since centralized pools choose what work gets sent to miners, a nefarious pool operator can pull off a 51% attack. p2pool is "dumb" and blindly assigns work based on whatever bitcoind serves it, so there is no centralized way of p2pool coordinating a 51% attack.
