All chainforks are not hardforks. Short chainforks happens every day. Usually because miners can't distribute their newfound blocks fast enough. This one was caused by a malicious miner not validating blocks, and mining on top of an invalid one. It disappeared as soon as the correctly validated chain overtook it. This only show the dangers of one miner controlling too much hashrate. All nodes, new and old, accepted the correctly validated chain as soon as it overtook the bad chain, and nobody were forced to upgrade anything. (Those who hadn't upgraded were potentially vulnerable to double spends however, as with all chainforks when you don't require enough confirmations. This is a good reason for merchants to stay up to date.)
The August 2010 fork was much longer, btw. That fork was caused by a bug which had to be fixed for the nodes to reject the faulty chain.
A hard fork is different. In a hard fork where the fork has a miner majority, the two chains will live on in parallel. Correctly validating nodes will never switch to the fork.
The so-called "Classic", "XT", "Unlimited", etc forks are especially dangerous, since upgrading won't help either. There will just be different coins, and you have to make a choice of one of them. Due to incompetent fork developers, you can't even run one of the other coins on the same computer at the same time as Bitcoin Core, since they demand to bind to the same ports. Constantly keeping up with which fork to use this week is too much for most users, and since their SPV wallets will be rendered useless, they will probably just try to get rid of their coins ASAP. It would be sad end for Bitcoin, I think.
If some competent developer should think about forking bitcoin, he should start
here and get 100% consensus first. There are many good reasons for a fork. Forking for a simple block size change is just dumb, and most people see that.
Very good post; it helped me finalize a previously incomplete thought.
It's entirely technically possible for Bitcoin and GavinCoin to have an amicable "
velvet divorce." That would obviously be best for both projects, and the general crypto community. They could still be friends, and avoid traumatizing their dependents.
But that's not happening, despite Core's peace offerings, olive branches, and other entreaties to stop the escalation and rancor.
So why are the Gavinistas insisting on a long, ugly, drawn-out, fractious divorce, complete with accusations and counter-accusations of conflicting interests, infidelity, and 'the other side' being terrible human beings?
Cui bono?Thanks to your post, it is now clear the Gavinistas insist on this extended, messy divorce proceeding because they want to take as much of Core's 'stuff' as possible. Like a greedy wife, who anticipates the court (of public opinion) favoring her, the Gavinistas want not only the common law property of the code, but also the kids and everything else, leaving Core destitute but still obligated to work on development.
So what we have here is a nasty custody battle. The cheating wife initiating the divorce demands to be awarded the kids, the house, the car, the cash, the IRA, and the dog, plus expansive spousal/child support (expecting Core to continue working just to support them), etc.
The Gavinista sense of
unlimited entitlement is appalling. They don't care about what's best for stakeholders, only about getting even with (ie, having their revenge on) Core.
They won't be satisfied unless they get the sha256 PoW, the ASICs, the pools, the users, the port numbers, the brand, the economy, the ecosystem, the forum, the subreddit, the alert key, etc.
For them it is not enough that GavinCoin live; they need Core to die miserable and alone, because Hell hath no fury...
Luckily, Honey Badger signed the ultimate prenuptial. Let the screeching Gavinista harpies bitch all they want, they can't touch his assets!