Quote from: BlackHatCoiner on Today at 12:44:41 PM

Complaints. All I read is complaints and nothing in action. The Bitcoin network is in a state where the arguments for change must be very compelling. It is like complaining why you can't push a giant rock alone. Extensive research is underway on second layers, recognizing that adjusting the block size limit isn't a viable long-term solution. I neither believe that the block size should remain at 4 MB forever, but at least that is tested, and is proved to be quite sustainable.

Change is hard.

If you're one person, somehow you need to pour 14 8-hour days to make a minimum viable product of something that needs to be made. And that's assuming you even know what needs to be made in the first place, as well as how to make it.

Then there's getting people to join the idea. Unless you are already a famous developer like any of the Bitcoin Core members, the only option is to go to meetups like Bitcoin Amsterdam and then convince people that this is an idea worth making. (Ark)

Even when you do have something and assemble a team, occasionally problems appear that are obstacles for it being used on a wide scale (Lightning Network). Or maybe people simply don't trust your software (Liquid).

Occasionally, you will face opposition and even attacks, even if the change is something small (e.g. a website).

Then there's always the possibility that nobody ends up using your software. Or maybe they don't use it the way you intend it to (Rodarmor's Ordinals were never intended to cause a traffic jam but look where we are).

Although you mentioned there is a lot of research on second layers, there are very few people who will actually implement a production version of stuff in papers, and this extends well beyond cryptocurrency. It's part of the reason why specialist engineers are paid so much.

Block size will always be a division among bitcoiners, but the main solution is found in changing things. But like I said above, change is hard. People are unstoppable forces, and are capable of building anything (even alternate Core clients @franky1) but this is seemingly an unmovable object.

What happens when an unstoppable force meets an unmovable object?