EOS non-hardforking solutions.

in #eos7 years ago (edited)

Ethereum smart contracts have had a number of high profile security breaches. The most recent breach of Parity client multisig wallets has raised the question of hardforking Ethereum to unlock ETH in the multisig wallets.

Whereas, I think hardforking Ethereum is fine, if that is the only solution, to the dilemma impacting Parity multisigs. I think it would take some comment and support by Vitalik to achieve a successful hardfork.

I am pleased to hear that Block One's EOS project is not using Parity and that EOS will have "non-hardforking solutions". Should security breaches occur in EOS smart contract code, finding a solution could be a lot easier than having to rely on a hardfork, whitehat group or both.

Screenshot_2017-11-10-00-35-11.png

Thanks for reading, comments welcome. What do you think of "non-hardforking solutions" ?

Sort:  

Yes, DPoS government consensus is superior to those hardfork debacles

Sure, I've just been reading about EOS producer hard fork voting
https://github.com/EOSIO/eos/issues/189

Will be intresting to see what possible solution Parity Tech comes up.

I would doubt they come up with something productive, the parity guys.

Good to hear that eos doesn’t use parity.
Check out my link on exodus wallet. Scary stuff.
https://steemit.com/bitcoin/@tt-dogg/warning-exodus-wallet-has-major-bugs

ima check it out... all my eos on exodus