Pages:
Author

Topic: Clearing the FUD around segwit - page 6. (Read 3874 times)

full member
Activity: 201
Merit: 157
April 02, 2016, 04:20:03 PM
#3
nice writeup.   minor nits:

Quote
Segwit was in fact originally planned as a hard fork, but the developers realized that it could be done as a soft fork and doing so would be safer than a soft fork.

Quote
Segwit is a cludgy hacked together and unready software

Better: Segwit is kludgy hacked together software that is not ready.

legendary
Activity: 1162
Merit: 1004
staff
Activity: 3374
Merit: 6530
Just writing some code
April 02, 2016, 03:12:22 PM
#1
I wrote a post on my website to try to clear up the misunderstandings that people have and spread about Segregated Witness.

http://www.achow101.com/2016/04/Segwit-FUD-Clearup

If you think I missed something or made a mistake, please let me know and I will change it. Feel free to discuss what I have written however I ask that you keep the discussion more technically oriented and less politically.

If you have any additional questions about segwit, I will try to answer them. If I think it is something that many people will ask or misunderstand, I will add it to the post.

Local rule: no posts about blockstream or claims that blockstream controls core development.

*Disclaimer: I am not one of the developers of Segwit although I have done extensive research and am in the process of writing segwit code for Armory.
Pages:
Jump to: