<div dir="ltr">Whatever measure you may use for "strength" or "weakness" is irrelevant - replay issues can affect any chain fork when there's inadequate protection at the protocol layer.<div><br></div><div>Given the inability to force software updates in a permissionless system, the optimal thing for groups that have already committed to deploy updated software is for them to protect users of both forks, but you could argue that this more an issue of morality. From a technical standpoint, as I mentioned before, lack of native protection results in the responsibility then falling upon the wallet and service layer.</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Sun, Oct 8, 2017 at 4:51 PM, bitPico <span dir="ltr"><<a href="mailto:bitpico@icloud.com" target="_blank">bitpico@icloud.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">This is a technical working group not one for speculation. If two chains emerge the weaker one MUST protect itself. We will know the weaker chain almost instantly when block 494,784 is passed. Until block 494,784 this is a non-issue.<br>
<div class="HOEnZb"><div class="h5"><br>
> On Oct 8, 2017, at 4:40 PM, Jameson Lopp via Bitcoin-segwit2x <<a href="mailto:bitcoin-segwit2x@lists.linuxfoundation.org">bitcoin-segwit2x@lists.<wbr>linuxfoundation.org</a>> wrote:<br>
><br>
> It seems clear to me that there is going to be a chain split, so the question comes down to who is going to put in the effort to protect users from accidentally sending crypto assets that they had no intention of sending. Without strong native two way replay protection at the protocol level, the responsibility will fall upon every wallet and service provider. As a result I'd expect to see a longer period of disruption / inaccessibility than we saw with the BCH fork, and probably several orders of magnitude greater instances of nontechnical users making mistakes to their own detriment.<br>
><br>
> I suspect that such a situation is destined to happen sooner or later given the permissionless nature of forks. The grand experiment must go on!<br>
><br>
<br>
</div></div></blockquote></div><br></div>