You'd mentioned earlier in this thread that you had no plans to exceed that 50% mark...but that may now be happening regardless. My question is whether or not we would be protected (as a pool) from actually executing the >50% attack on the network ourselves by way of some sort of subversion.
Looks like I was wrong about 50%, I thought it was impossible to reach due to pools competition.
I'm open to your proposals on handling such situation (even though I still don't think we can reach it permanently), so we could be more transparent to miners. I'm sure that there IS a solution; the fact of being >50% doesn't means that something bad will happen.
One of the things I can do right now - I'm going to contact slush and get his phone number, so we could notify each other about pool problems.
To mitigate the possible problems deepbit currently runs on servers located in different jurisdictions and we (deepbit admins) reside in other two different jurisdictions, so pool is relatively protected.
Also I want to remind you something from
https://en.bitcoin.it/wiki/Attacks#Attacker_has_a_lot_of_computing_powerThe attacker can't:
- Reverse other people's transactions
- Prevent transactions from being sent at all (they'll show as 0/unconfirmed)
- Change the number of coins generated per block
- Create coins out of thin air
- Send coins that never belonged to him
