271
General Discussion / Re: Worst Case Scenario Contingency Planning
« on: August 05, 2014, 07:18:38 pm »It has been pointed out that the weakest part of DPOS is that once someone controls 51 delegates they can never be fired unless they consent because they could filter any transaction that votes for someone other than themselves. There are several ways to gain control of 51 delegates:
1) SWAT team all over the world
2) Blackmail delegates
3) Buy up the stake.
In any of these events the current crop of delegates needs to be purged. In the case where they bought up the stake then any balances voting for the attackers also need to be purged.
I think that it should be possible to pre-plan for this scenario by shipping every wallet with an emergency backup-fork switch. At any time users can simply go into advanced and enter a block number that they would like to "hard fork" and a list of misbehaving delegates for which balances should be purged.
We can then provide a URL scheme that entirely documents the hard-fork and developers / community members can simply share the URL. All of the honest nodes automatically switch to the new fork without anyone having to distribute new binaries.
There might be some confusion about which URL to follow, but in most cases the attack should be very clear and the solution equally clear. The social consensus will form and the chain can continue. After all failure to agree is agreeing to fail.
Would only the transactions of the attacker get purged?
And what would happen to the balances that get purged?
And if someone would get tricked in voting for the attacker, their balance would also be purged?