Bytemaster: "rather produce no than two blocks"

Started by santaclause102, December 20, 2014, 01:55:40 PM

Previous topic - Next topic

0 Members and 1 Guest are viewing this topic.

liondani

Quote from: emski on December 20, 2014, 07:50:18 PM
Quote from: vikram on December 20, 2014, 07:39:01 PM
Yes! Slower confirmation time is much better than a forked network! In the future, double-producing blocks could get your delegate account fired and retracted.

It is not only forked network. The security is much lower if delegates are able to easily sign 2 chains.
How can you be sure that your chain is OK even with 60% delegate participation ?
Who will prove to you that these delegates are not signing other chains with higher participation ?
same concerns here...

Sent from my ALCATEL ONE TOUCH 997D

[url="https://www.steempeak.com/@liondani"]https://www.steempeak.com/@liondani[/url]

emski

Quote from: vikram on December 20, 2014, 07:39:01 PM
Yes! Slower confirmation time is much better than a forked network! In the future, double-producing blocks could get your delegate account fired and retracted.

It is not only forked network. The security is much lower if delegates are able to easily sign 2 chains.
How can you be sure that your chain is OK even with 60% delegate participation ?
Who will prove to you that these delegates are not signing other chains with higher participation ?
[url="https://bitsharestalk.org/index.php/topic,9857.0.html"]https://bitsharestalk.org/index.php/topic,9857.0.html[/url]

vikram

Yes! Slower confirmation time is much better than a forked network! In the future, double-producing blocks could get your delegate account fired and retracted.

santaclause102

#1
I didn't see this direction propagated on this forum so here it is :) Here https://www.dropbox.com/s/0m0plhj8ggw2pi9/Mumble%20Chat%2012_19_2014%20with%20intro.ogg?dl=0  around minute 12 BM made clear what delegates are supposed to do in case of a fork.