> Please enlighten me on how you intend to change the blocksize in everyone else's client?
By convincing them to do so, in the same way that every other change to bitcoin is made? Or, alternatively, implement my changes via a soft fork, get half the hash power, and start orphaning people. Segwit, for example, was a major change to the bitcoin protocol, deployed via exactly this same strategy.
> The correct action was taken to do nothing, since it was too controversial to force one opinion on everyone
Segwit was very controversial as well. Don't for a second pretend like it wasn't. Lots of people disagree with it. Perhaps not a majority, but a large amount did. And yet segwit was activated and exist today. It was literally a soft fork blocksize increase that was forced on people who disagreed.
And before someone brings up the whole "soft fork, vs hardfork", I'd like to point out that segwit itself was a soft fork blocksize increase. Blocksize increases do not require hardforks. some methods of increasing the blocksize do, but there are many ways to do the same thing that segwit did, and increase the blocksize via a softfork.
So if you really want to be technical, the way that I would increase the blocksize a second time, is to create a second softfork blocksize increase, convince 51% of the hashpower to include the change, and then orphan all blocks that don't use the new changes.
At this point it doesn't matter if some people refuse to install the software. Soft forks are backward compatible, and all past nodes would follow, unless they specifically decide to hard fork away to stop the soft fork.
If you want proof that a blocksize increase can be done with a soft fork, go google "Extension blocks". It was a soft fork blocksize increase, created by Joseph Poon, the Lighting Network inventor. If you do believe that I am credible on the topic of soft fork blocksize increases, then surely you should believe that the inventor of the lightning network is credible.
No, I meant Joseph Poon. He created the most infamous version of the extension blocks proposal for the bitcoin protocol.
Although I guess I should have said "one of the people who created this proposal", as there were multiple authors. chjj also deserves much of the credit. I only referenced Joseph specifically, because of the lightning network thing, which core supporters seem to like a lot.
By convincing them to do so, in the same way that every other change to bitcoin is made? Or, alternatively, implement my changes via a soft fork, get half the hash power, and start orphaning people. Segwit, for example, was a major change to the bitcoin protocol, deployed via exactly this same strategy.
> The correct action was taken to do nothing, since it was too controversial to force one opinion on everyone
Segwit was very controversial as well. Don't for a second pretend like it wasn't. Lots of people disagree with it. Perhaps not a majority, but a large amount did. And yet segwit was activated and exist today. It was literally a soft fork blocksize increase that was forced on people who disagreed.
And before someone brings up the whole "soft fork, vs hardfork", I'd like to point out that segwit itself was a soft fork blocksize increase. Blocksize increases do not require hardforks. some methods of increasing the blocksize do, but there are many ways to do the same thing that segwit did, and increase the blocksize via a softfork.
So if you really want to be technical, the way that I would increase the blocksize a second time, is to create a second softfork blocksize increase, convince 51% of the hashpower to include the change, and then orphan all blocks that don't use the new changes.
At this point it doesn't matter if some people refuse to install the software. Soft forks are backward compatible, and all past nodes would follow, unless they specifically decide to hard fork away to stop the soft fork.
If you want proof that a blocksize increase can be done with a soft fork, go google "Extension blocks". It was a soft fork blocksize increase, created by Joseph Poon, the Lighting Network inventor. If you do believe that I am credible on the topic of soft fork blocksize increases, then surely you should believe that the inventor of the lightning network is credible.