[Bitcoin-segwit2x] Strong 2-Way Replay Protection
jameson.lopp at gmail.com
Sun Oct 8 21:18:55 UTC 2017
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.
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.
On Sun, Oct 8, 2017 at 4:51 PM, bitPico <bitpico at icloud.com> wrote:
> 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.
> > On Oct 8, 2017, at 4:40 PM, Jameson Lopp via Bitcoin-segwit2x <
> bitcoin-segwit2x at lists.linuxfoundation.org> wrote:
> > 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.
> > 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!
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the Bitcoin-segwit2x