0 Members and 1 Guest are viewing this topic.
Quote from: Rune on January 21, 2015, 12:33:52 pmAn immediate and effective solution to this issue is actually very simple. Malicious delegates will likely be delegates that don't produce blocks or produce blocks and steal 100% of the inflation. Both scenarios are by themselves quite unlikely and not actually that hurtful to BitShares, but most importantly they are easy to detect and it's possible to see what accounts control the stake that voted for them. To ensure the malicious stake doesn't continue ruining things a hard fork can be manually circulated among the community that permanently destroys all the stake that voted for the malicious delegates. BitShares would be back up and running normally quite quickly, and the only person who would really be hurt would be the attacker.Stealing is not objective. What about a dev that doesn't really work (effectively)?
An immediate and effective solution to this issue is actually very simple. Malicious delegates will likely be delegates that don't produce blocks or produce blocks and steal 100% of the inflation. Both scenarios are by themselves quite unlikely and not actually that hurtful to BitShares, but most importantly they are easy to detect and it's possible to see what accounts control the stake that voted for them. To ensure the malicious stake doesn't continue ruining things a hard fork can be manually circulated among the community that permanently destroys all the stake that voted for the malicious delegates. BitShares would be back up and running normally quite quickly, and the only person who would really be hurt would be the attacker.
I'm not sure how "vote as delegates recommend" works.
Vote as Delegates Recommended Some users publish a set of delegates (a slate) they recommend. Theses delegates fulfill certain criteria that are defined by the particular users. As an example: A user only recommends delegates whose real-world identities are known and verified. Another user recommends delegates that are trusted members of the bitsharestalk.org forum. And so on. If that user is a delegate and you vote for him with a wallet_transfer, you can also vote for all of his recommended delegates by choosing Vote as Delegates Recommended
Quote from: Rune on January 21, 2015, 12:33:52 pmAn immediate and effective solution to this issue is actually very simple. Malicious delegates will likely be delegates that don't produce blocks or produce blocks and steal 100% of the inflation. Both scenarios are by themselves quite unlikely and not actually that hurtful to BitShares, but most importantly they are easy to detect and it's possible to see what accounts control the stake that voted for them. To ensure the malicious stake doesn't continue ruining things a hard fork can be manually circulated among the community that permanently destroys all the stake that voted for the malicious delegates. BitShares would be back up and running normally quite quickly, and the only person who would really be hurt would be the attacker.Destroying all the stake is less than ideal. I don't think there is a way how to discriminate between votes really intended for the malicious delegate and votes selected with "vote random subset" and "vote as delegates recommend".I know it would be probably just a small portion of votes, but in principle it wouldn't be right.
a hard fork can be manually circulated among the community that permanently destroys all the stake that voted for the malicious delegates. BitShares would be back up and running normally quite quickly, and the only person who would really be hurt would be the attacker.
我想,你先有11%的股份再说吧。你拥有11%的股份,还希望垮掉,我觉得你的心态有问题、
Quote from: liondani on January 07, 2015, 12:31:29 pmQuote from: heyD on January 07, 2015, 10:27:27 amin fact, techically speaking at this moment you don't need 51% of stake to attack BTS, 16% are enough. if you have that much stake you can vote all of your 101 delegates in, which means you take full control of the whole dpos network since right now the delegate which gains most votes is only supported by less than 16% stake. when you do so, you can have all of your delegates disabled block production.or with a 10% stake you can control over the half of delegates and sign on a alternative "main" chain (?)yes, I think so. with 10% stake you can control 57 delegates at this moment, then reject all the blocks signed by the rest 44 delegates and also exclude the transactions which don't vote for you. but we are only talking about this technically.
Quote from: heyD on January 07, 2015, 10:27:27 amin fact, techically speaking at this moment you don't need 51% of stake to attack BTS, 16% are enough. if you have that much stake you can vote all of your 101 delegates in, which means you take full control of the whole dpos network since right now the delegate which gains most votes is only supported by less than 16% stake. when you do so, you can have all of your delegates disabled block production.or with a 10% stake you can control over the half of delegates and sign on a alternative "main" chain (?)
in fact, techically speaking at this moment you don't need 51% of stake to attack BTS, 16% are enough. if you have that much stake you can vote all of your 101 delegates in, which means you take full control of the whole dpos network since right now the delegate which gains most votes is only supported by less than 16% stake. when you do so, you can have all of your delegates disabled block production.