Topic: Segregated witness - The solution to Scalability (short term)? - page 10. (Read 23195 times)

LN needs two things to work properly:
 - free blockspace
 - fixed transaction malleability

the first one is not really solved (in my opinion at least) but the second one is.

LN needs two things to work properly:
 - free blockspace
 - fixed transaction malleability

the first one is not really solved (in my opinion at least) but the second one is.

All we can do is choose to use it or move on.

However here in bitcoin world, there is no such kind of financial responsibility. If devs push in a change which resulted in customer loss, the devs are not responsible for the damage, or to say, they don't have enough money to compensate the loss from millions of users. The users are all on their own

Of course it's a proven system that has bailouts happen all the time. I've already said I'm willing to take the risk. Now, would you like me to start listing Bitcoin's failures starting with malleability and work backwards to be fair? Before you answer realize I'm going to fill a couple of pages of not only functional code problems but, because of the links you used, I'm going to list every theft that happened from human error or because Bitcoin made those thefts possible. BTW: no one bails out Bitcoin users and the FDIC doesn't reimburse them.

Right, so essentially we need to use at our own risk and trust that they will make the right choices and implement the correct improvements. It's a little more risky than trusting the current proven system

if they mess up bitcoin, the dev's own income and savings is also lost..
thats why they dont want to mess up. and each new release is tested. and in the result of a bug in a new release. people downgrade to previous version and the bug is gone until its sorted out for an amended new release.

bitcoin is actually more secure then you think, you are not relying on 1 coders say so. there are usually 1000+ coders all using new releases before the general users even get the option to upgrade. so if there was any issue, the coders would be the first to get affected.

However here in bitcoin world, there is no such kind of financial responsibility. If devs push in a change which resulted in customer loss, the devs are not responsible for the damage, or to say, they don't have enough money to compensate the loss from millions of users. The users are all on their own

This is growing tiresome. Do you fully understand the complexities of the ACH/EFT system? I bet, just like me, you have a general understanding of how it works but have never seen the code behind it. I would also bet you have or have had at least one debit card and credit card in your life because almost everyone in western society has. There were 22 billion ACH transactions in 2013 with a total value of $38.7 trillion and almost no one really understands how it works. The way the ACH/EFT system continues to operate is by government and private oversight. People make a career out of working in finance and programming who oversee the system and there are laws that govern the form of that oversight.

The users of Bitcoin believe that system is flawed. They see potential in Bitcoin and are willing to use it. That requires faith in the original architect and the developers that continue to improve it because there is no governing body to regulate its continued operation or bailout its failures as there is with ACH/EFT. That leaves two possibilities for our acceptance and use of Bitcoin. Either build up a world class understanding of at least C++, Python, Java and elliptic curve cryptography or trust the people that are doing the job for you. I've learned to trust some of the scientists that work on this project based on their actions. Others I don't trust at all. Unless a mistake becomes blatantly obvious or someone I trust decides to speak out against this change I'm going to trust it because my understanding is limited. I suggest you do the same.

To migrate to a large change in infrastructure, you need to not only understand the solution, but also fully aware of the impact to the existing system and all the other systems that are dependent on them, potential security risk, evaluate its risk/reward ratio, and finally and most important, you should always be able to roll back to the old version if something went wrong

A soft fork qualify the last criteria, but still, from risk/reward point of view, I don't feel it worth the effort given the risk it involves. You change to a new untested architecture, what if after 1 years when majority of the nodes were upgraded to SW and found out that there is a deadly security hole that can not be covered, thus hackers can spend anyone's coin?

Bitcoin's value relies purely on its security model. Existing architecture worth a lot because it is robust and time tested for almost 7 years. It worth a little in the beginning, since there are too many possible security risk to break it apart, thus it must survive the test of time to gain its value. Now if you change to another untested architecture, it will basically reset its value to zero, and take equal long time to establish people's trust