From what I have read, if some miners go ahead with SegWit2X then there's a risk of transactions made using bitcoin-qt will also be valid on the SegWit2X fork - is this true? If so, can something be done to ensure that TXs are valid only on the current/non-SegWit2X chain?
-
rebroad commented at 3:08 AM on November 5, 2017: contributor
- rebroad renamed this:
replay protection (sexwit2x)
replay protection (segwit2x)
on Nov 5, 2017 -
MarcoFalke commented at 3:39 AM on November 5, 2017: member
You might want to try splitting your coins. It could take several tries but should work eventually.
Anyway, support requests should be directed to Bitcoin stack exchange
On Nov 4, 2017 20:10, "Rebroad" notifications@github.com wrote:
From what I have read, if some miners go ahead with SegWit2X then there's a risk of transactions made using bitcoin-qt will also be valid on the SegWit2X fork - is this true? If so, can something be done to ensure that TXs are valid only on the non-SegWit2X fork?
— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub https://github.com/bitcoin/bitcoin/issues/11609, or mute the thread https://github.com/notifications/unsubscribe-auth/AGGmvz8e_p7iuuU35D7l_-Vvrb8sqFLyks5szScUgaJpZM4QSPlv .
- sipa closed this on Nov 5, 2017
- MarcoFalke locked this on Sep 8, 2021
Contributors