Hacker News new | ask | show | jobs
by twayamznacct 3150 days ago
IF there is a hard fork to resolve this I hope some very hard questions are asked regarding why there was a hard fork for this, and not one for the earlier Parity bug given that the amount of funds lost in both were roughly equivalent.

Unless I am recalling incorrectly, the bug during the summer did not impact anyone on the Ethereum team, while this one did.

Which would make the motivation behind a hard fork in this specific case ... questionable.

I think that would be the time I divest myself of the ETH I hold.

Disclaimer: (If it wasn't obvious from the above :) ) I hold a decent amount of ETH (thankfully not in a parity multi-sig wallet!)

1 comments

From what I understand, this can be fixed with a generalized fix for this class of contract bugs, which makes it different than the previous bug. More importantly, this can wait until the next planned hard fork, since the funds are locked and not going anywhere, so wouldn't need its own dedicated hard fork.