4 ms·
It's actually not true that there's never been a hard fork. I know the Core FAQ says that, but it's incorrect. When we moved past Berkeley DB to LevelDB, there
by mike_hearn 11y ago
It's actually not true that there's never been a hard fork. I know the Core FAQ says that, but it's incorrect. When we moved past Berkeley DB to LevelDB, there was an accidental hard fork that revealed limits in older nodes nobody knew about. But those limits had to go, and so the change was attempted again in a more controlled manner some time later. So it was known that the network would start producing blocks that older nodes would reject. That's a hard fork. It was scheduled in advance and went off smoothly.
The idea that hard forks are dangerous or irresponsible is a belief that is not well supported. However it's a rather good piece of Bitcoin Core propaganda to scare people away from doing what's necessary.
- kanzure 11y ago> The idea that hard forks are dangerous or irresponsible is a belief that is not well supported bip99 - https://github.com/bitcoin/bips/blob/master/bip-0099.mediawiki https://github.com/bitcoin/bips/blob/master/bip-0099.mediawi... https://www.reddit.com/r/bitcoinxt/comments/3t21dh/dangerous_homebrew_cryptography_in_blockstream/cx586r1 https://www.reddit.com/r/bitcoinxt/comments/3t21dh/dangerous... https://www.reddit.com/r/Bitcoin/comments/3griiv/on_consensus_and_forks_by_mike_hearn/cu0yv0r https://www.reddit.com/r/Bitcoin/comments/3griiv/on_consensu... > scare people away from doing what's necessary Most block size hard-forks can be deployed as a soft-fork. "It's necessary" is highly contentious and you have failed to cite any of the arguments you disagree with- you're wasting everyone's time.
- wraithm112 11y agoI said "intentional hard-fork" for a reason. For everybody's reference, the bdb to leveldb hard-fork happened in early 2013. Everybody acted swiftly to correct the issue by downgrading to 0.7 if I recall correctly. An accidental hard-fork is a completely different animal from an intentional contentious hard-fork where half of the network goes one way and the other half the other way for the foreseeable future.
- mike_hearn 11y agoSo did I. Please re-read my post. The same change that triggered the accidental fork was done smoothly later on, but the change was the same - it was a deliberate hard fork. You probably didn't notice because there was plenty of lead time and I don't think any miners got split off the chain, even though they could have.
- deleted 11y ago[deleted]
- jcansdale 11y agoWould it be fair to say it was a deliberate hard rule change that because it was rolled out in a controlled manner didn't manifest itself as a hard-fork? IMHO there are ways to mitigate the dangers of an hard rule change so that a hard-fork never actually happens. For example, a notification period followed by a version based soft-fork should be able to get an overwhelming majority of miners on board. If blocks on the minority chain are taking over a day to generate and there is a massive transaction backlog, the minority chain is unlikely to make it to 6 blocks. Does that make sense? A hard rule change without a hard-fork?
- sail 11y agoMike, can you imagine any way to run a cryptocurrency so that growth doesn't threaten decentralization? Could a cryptocurrency not be controlled by those who can afford to spend the most in CPU power (like governments)? Could consensus occur by human power?