Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: Wind_FURY on September 29, 2017, 06:40:03 AM



Title: What can the community do to make Segwit2x include replay protection?
Post by: Wind_FURY on September 29, 2017, 06:40:03 AM
We know that part of the reason why Segwit was activated was because of the threat of the UASF. Now what can the community do to make the developers of Segwit2x/btc1 and the NYA signatories include replay protection in the new fork this November?

I cannot believe that the people in the forum are taking it very lightly. I am posting this thread in this subforum to know what can we do technically.

Maybe we can do it like what the UASF did.


Title: Re: What can the community do to make Segwit2x include replay protection?
Post by: Ucy on September 29, 2017, 07:50:52 AM
Unity is needed badly. Unfortunately there aren't alots of believers here . Most came here to milk the Forum/Bitcoin to death and then disappear. I just wish TRUE believers are identified, put in strategic positions,  well incentived - rewarded. This will definitely help keep the community invincible. There are people here who just hate Bitcoin or don't care at all.
 It is just not OK to keep rewarding them too much. They will grow fat and destroy everything we believe in Just like Cancer cells.


Title: Re: What can the community do to make Segwit2x include replay protection?
Post by: aleksej996 on September 29, 2017, 10:02:02 PM
Other then boycott the companies that are backing it up, nothing. If we just boycott the companies that signed the NYC agreement, that would place the financial pressure on them to implement the protection in their software, as then people could use both chains. This makes sense, because anyone that doesn't support the fork will not be able to do business with those companies anyway if replay protection is not implemented, since you can't even get the free coins, let along do anything else with these companies that use another blockchain that can not safely coexist with this one, in the same user base at least.