3 ms·
Given that the bitcoin community normally seems so enamoured with trustless systems, I did think it was extremely odd that people went along with Segwit2x when
by michaelt 9y ago
Given that the bitcoin community normally seems so enamoured with trustless systems, I did think it was extremely odd that people went along with Segwit2x when it was implemented in such a way that the Segwit camp got a trustless guarantee while the 2x camp got no such guarantee.
After all, if Segwit have already got their payoff, what incentive do they have to support 2x?
- 127 9y agoAs far as I'm aware the Bitcoin developers never signed the New York Agreement. It was a group of people and businesses that came together to "fix" Bitcoin into something they saw an improvement. They just lacked developers and community support.
- VonGallifrey 9y agoAs far as I am aware the Bitcoin Core developers are just a group of people that called their client "reference client" and are themselves very entangled with Business interests of a particular company. They are not "official" and have no real authority to call their client "reference client" but somehow every time someone speaks about the NY Agreement it gets pointed out that Bitcoin Core has not signed. Who cares what they signed or didn't sign? They did sign the HK Agreement and then broke it shortly after. They have proven that they don't give a shit about such agreements. NY Agreement didn't lack developers (just not the Bitcoin Core Developers) and they didn't lack community support. Bitcoin Core is just very good at controlling communication channels through Censorship and Propaganda.
- just_one_time_ 9y agoThe private company Blockstream ($76 mil, VC, mostly from AXA) employs the most active Core contributors.
- xorcist 9y agoThere are no well defined "camps" in the community. The tendency to define camps is part of the attempt to frame the discourse around project governance in single technical terms like "block size". Those descriptions seldom make any sense to describe the behaviours of the diverse actors in the ecosystem, and only serve to muddle the deployment scenarios of various improvements to the Bitcoin protocol. Segwit2x did what it was intended to do, but what that was varied wildy between the various actors involved. It never bothered with deployment scenarios or any sort of definition what the intended end game was, and how it was to be managed going forward, not because the people involved were somehow incompetent but because those were not relevant to the initiative. Some saw it as a golden opportunity to pump an otherwise uninteresting hard fork, some as a possbility to do an ICO, some as free publicity for their startup and some to make a name for themselves as narrators of the Bitcoin story. It did all that and more. We'll probably see more similar initiatives in the future, but the community will probably care less about them going forward.
- just_one_time_ 9y agoBlockstream (Bitcoin Core) simple gave an ultimatum (with various reasons such as the increased time needed to implement 2 mb blocks). Adam Back and Greg Maxwell simply said that unless activation happened in this way, they would not support it.
- lawn 9y agoThis point was brought up directly after the agreement. Look and behold that was exactly what happened. The theory I like is that they were too gullible and trusting. Their stated mission was to unite the two camps big blockers and segwit supporters and to avoid a divide in the community. What they didn't realize was that the community was already divided and it's impossible to unite Core's blind focus on off chain scaling with on chain scaling.