Topic: Safely moving coins after fork and understanding replay attack (Read 162 times)

Since there is no replay protection on B2X. I'm wondering about strategies to safely move coins after the fork in order to avoid replay attacks.

My understanding of replay attacks is that since there is no differentiator between the chains, if you move one of the coins then an attacker could then just copy that transaction and send it to the other chain and it would be valid so both coins would be sent to the address you wanted only one of the coins to be sent to. Of course this attack only makes sense if it is done by the person or organization that you are sending the coins to.

I guess if you just send the coins to an address you had before the fork, even if a replay attack occurred it would just send all your coins to that address right? So you'd still have all the coins just at the address you send them to?

I'm thinking the way to protect against replay attacks is to send each set of coins, one right after the other, to two different addresses, that currently hold no coins. If you do these transactions one right after the other, no replay attack could happen in later blocks because all the coins have already been sent. And since you now have them in different addresses, any possibility of future replay attacks wouldn't matter because you don't have any of the other coins at either address. So then you should be free to send your coins wherever safely.

Does that make sense? Any safety problems or warning with that?