[Bitcoin-segwit2x] Strong 2-Way Replay Protection

bitPico bitpico at icloud.com
Sun Oct 8 21:49:36 UTC 2017

Forcing upgrades is accomplished through miners both historically and documented by the inventor of Bitcoin (read the white paper about the chain with the most proof of work) as they own the blockchain; full nodes only enforce miners rules and cannot produce any blocks (that is proof of stake).

The 1 megabyte base blocks size is deprecated. We are upgrading from old software to new software (2 Megabyte base block size). The users that upgrade to the “non-deprecated” Bitcoin implementations have no problems. The ones who fail to upgrade are irrelevant to this working group and to Bitcoin as a whole.

> On Oct 8, 2017, at 5:18 PM, Jameson Lopp via Bitcoin-segwit2x <bitcoin-segwit2x at lists.linuxfoundation.org> wrote:
> 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.

More information about the Bitcoin-segwit2x mailing list