4 ms·
This situation perfectly demonstrates the possible repercussions of performing rushed and contentious hard forks (which is actually the worst way one should do
by antonios 10y ago
This situation perfectly demonstrates the possible repercussions of performing rushed and contentious hard forks (which is actually the worst way one should do a hard fork). Possible replay attacks alone cause considerable confusion amongst Ethereum users. I believe Vitalik and the whole Ethereum dev team sound much more relaxed than they really are at this point.
Note that Ethereum was just used for speculation so far. Had the same thing happened on Bitcoin, it would wreak havoc to its reputation and utility as a token to transfer wealth...most importantly because it would destroy two very important properties: Immutability and fungibility.
Ethereum developers don't seem to care that much about those properties so far.
- UweSchmidt 10y agoThe hardfork was on a clock to prevent the "hacker" (a.k.a. the person who just executed the code as it was coded and therefore inteded) from cashing out. No doubt developers went through a few extremely stressful weeks.