@jonny1000 :
I do agree that the statement "
BIP101 and 8MB blocks are already supported by a majority of the miners" in the industry letter was not based on fact.
I would agree that it was a deliberate attempt to get momentum behind
XT.
I disagree with your assessment of the consequences of their support - they do not mention exclusivity in that letter. And I think that is a crucial difference between the approaches taken by XT/Classic and Core.
One is a competitive proposition, the other feels it has to use anti-competitive means to achieve its ends.
In the interests of balancing your lopsided list of counterproductive approaches out a bit, based on reality, I present to you:
Further examples of small blocker side counterproductive approaches:
- Issuing a restrictive SegWit omnibus plan which denies simple block size increases past at 1MB, moving significant on-chain scaling into an undefined future and introducing dubious economic distortions
- Pushing unwanted changes such as RBF on the community against consensus and without 95% activation when it suits Core
- Accusing others of being blockers when a 95% activation (e.g. SegWit) seems unlikely, even though Core would not hesitate to exercise a 5% veto
- Aggressive and rude language, turning developers away from the small blocker side. e.g. saying Bitcoin is not a "coffee money", terms such as "Hearnia", "Gavincoin", "Toomimcoin", "Gavinistas"
- Questioning the motivation of the large blockers (!)
- Engaging in ridiculous conspiracy theories, such as bigger blocks are a CIA initiative pushed by Gavin/Hearn etc., will lead to immediate decentralization, overturning of the 21M coin limit, doomsday collapse of coin value due to HF, ...
- Turning a blind eye to your own centralized node count (have a look at the sudden Core node collapse in the pic below - tell me what you think!)
- Miners rewarding their own customers with priority service
- Spreading falsehoods such as the Classic team are not competent and capable of scaling Bitcoin in a safe way.
- Conflating the issue of removing the development team with eliminating a network rule (!)
The more I think about it the longer I can make this list too. But I do agree it's counterproductive. We already know this is unnecessary and just delays the implementation of better solutions and growth of Bitcoin.
O lookey here, a roughly ~750 node drop in Core 0.12 nodes. Centralized much?
(About Gavin)
He still has my full respect, and I believe many others feel the same. He's someone who can apologize and correct himself when he's wrong, and he's shown that on multiple occasions. I'll take that anyday over those who lie repeatedly and unabashedly. That's too reminiscent of today's style of politics.
And I wanted to say, that if you're looking for reasonable policy, the conservative 2MB change with SegWit on the roadmap is about as reasonable (read: conciliatory) as I can imagine. You're not going to get a better deal (although as I've said to you before, you're always welcome to take Classic and change the 75/28 parameters to something you think the community would get behind sooner). But somehow that hasn't happened.