4 ms·
3. the btc devs did not decide to abandon the longest chain, the miners voluntarily chose to stop mining the chain they were working on and begin building on a
by tfha 8y ago
3. the btc devs did not decide to abandon the longest chain, the miners voluntarily chose to stop mining the chain they were working on and begin building on a different chain.
And, it's significantly less likely that this would happen again today. Bitcoin has matured a lot and the types of pressures that existed in 2013 to push changes onto the network have largely been eliminated today.
- hudon 8y ago> 3. the btc devs did not decide to abandon the longest chain See, now you're trying to censor history. Here's a refresher of what happened: >>> from https://freedom-to-tinker.com/2015/07/28/analyzing-the-2013-bitcoin-fork-centralized-decision-making-saved-the-day/ https://freedom-to-tinker.com/2015/07/28/analyzing-the-2013-... Right away, developers start giving out advice to downgrade: 23:49 Luke Dashjr surge_: downgrade to 0.7 if you mine, or just wait 23:50 Pieter Wuille doublec: do you operate a pool? 23:50 doublec yes 23:50 Pieter Wuille doublec: then please downgrade now BTC Guild gets going immediately… 23:51 BTC Guild BTC Guild is going back to full default block settings and 0.7 soon. 00:01 BTC Guild Almost got one stratum node moved … even at significant monetary cost. 23:57 BTC Guild I've lost way too much money in the last 24 hours from 0.8
- tfha 8y agoYes, this was done with the consent of the miners, and not by pushing out a hardfork onto the network. The miners could have easily refused to perform the downgrade. The majority of nodes on the network stuck to following the longest chain rule and noticed nothing out of the ordinary.