pull down to refresh
You’re interested in replay protection. Here is explained how BCH implemented it.
Note that this describes how BCH changed the protocol to make it impossible to replay transactions in either direction, because the transaction format was changed.
In the case of Bitcoin vs RDTS, the problem would be that both networks accept the same transaction format, except for the new rules introduced by RDTS.
Thank you!
I'll find you a few tomorrow
@remindme in 10 hours
Here are some of Aaron's guides from the last time around we had stupid hardfork troubles
https://bitcoinmagazine.com/technical/beginners-guide-claiming-your-bitcoin-cash-and-selling-it
https://bitcoinmagazine.com/technical/bitcoin-beginners-guide-surviving-bgold-and-segwit2x-forks
Like back then, some of the hww might supply access to the forked coin and so you'd be able to spend directly from there
Additionally, it currently seems SegWit2x will fork without strong replay protection. This means that post-fork, BTC transactions and B2X transactions will look identical and could both be valid on both blockchains.
Therefore, spending coins on the BTC blockchain could make you accidentally spend the “equivalent” B2X on the SegWit2x blockchain, and the other way around. Instead of paying someone only BTC, you may unintentionally send B2X as well — or vice versa. The BTCs and B2Xs are initially “stuck together.”
"To be on the safe side, you should probably not spend an coins after the SegWit2x fork at all. As explained below, you’ll first need to “split” your coins"
I'll check them out thank you
Edit: what would I even search for? "Spend fork coins"
"How to send fork coins?"