I think a "replay attack" could happen if you decide to spend your bitcoins on one chain and your transaction is picked up by a node on the alternate chain. This is a real threat, so maybe the fork must provide a way so that a transaction on one chain is not a valid transaction on the other chain. I don't know if the fork will provide such a protection. Based on your analysis, I guess it won't.
You are viewing a single comment's thread from:
@ghasemkiani this is something to worried about for sure, but i think there would be solution sooner or later...
However it doesn't seem to get solved at least at the time of this hard fork...
segwit2x team doesnt care and is garbage