melvincarvalho on Nostr: Watched the first hour of this. There are some good, but incomplete arguments. I'll ...
Watched the first hour of this. There are some good, but incomplete arguments. I'll go over the main 2:
- Bitcoin is not easy to change because, as sipa put it, it's like changing the wheels of a ferrari going at full speed. The risk is of a chain split, which basically blows up the whole project. So any change has to be clearly more valuable than the risks.
- Layer 2 which you both talk about is very powerful. It's more powerful that probably you realize. For example RGB is turing complete. So just use that, it can do anything. Or merge mining, or side chains, or any number of solutions. The end user will not care about the technical details under-the-hood.
Given those 2 points, the solution is to just build things, that users want. Rather than trying to fork the project. None of the people that are trying to fork the project have built things that people want. So just write code and use layer 2. If your project is any good, people will use it.
- Bitcoin is not easy to change because, as sipa put it, it's like changing the wheels of a ferrari going at full speed. The risk is of a chain split, which basically blows up the whole project. So any change has to be clearly more valuable than the risks.
- Layer 2 which you both talk about is very powerful. It's more powerful that probably you realize. For example RGB is turing complete. So just use that, it can do anything. Or merge mining, or side chains, or any number of solutions. The end user will not care about the technical details under-the-hood.
Given those 2 points, the solution is to just build things, that users want. Rather than trying to fork the project. None of the people that are trying to fork the project have built things that people want. So just write code and use layer 2. If your project is any good, people will use it.