It’s not an apples to apples comparison — I was there in 2013 with the 0.4/0.5 bdb issue happened, it was a split (not downtime), and the community went with 0.4 until 0.5 was patched. The community was much smaller. There was no downtime. There could have been loses on the centralized exchange side for the few hours of ambiguity. maybe there was 1 public report of loss at the time.
This is the lesson that ETH people were not around for. More moving parts; more failure cases. More client, more moving parts.
It’s not an apples to apples comparison — I was there in 2013 with the 0.4/0.5 bdb issue happened, it was a split (not downtime), and the community went with 0.4 until 0.5 was patched. The community was much smaller. There was no downtime. There could have been loses on the centralized exchange side for the few hours of ambiguity. maybe there was 1 public report of loss at the time. This is the lesson that ETH people were not around for. More moving parts; more failure cases. More client, more moving parts.