unless it's a lose-lose game.
If there is no bomb-proof protection from replay attacks (and there is not afaik) you could not move your coins on a chain without risking that they get moved on the other:
https://themerkle.com/what-is-a-bitcoin-replay-attack/
If there is no bomb-proof protection from replay attacks (and there is not afaik) you could not move your coins on a chain without risking that they get moved on the other:
https://themerkle.com/what-is-a-bitcoin-replay-attack/
I have no worries about being able to disassociate coins if we experience a contentious hard fork because of BU.
Tainting with coin base rewards is certainly a bomb-proof method to disassociate coins. Due to the very nature of a hard fork (not backwards compatible), coin base rewards on the new chain will never be valid on the old chain (old clients don't accept those rules), so any transaction created which includes a coin base reward from the new chain will never be valid on the old chain. Bomb-proof.
As far as the other method I mentioned earlier in this thread, it's not quite as bomb-proof, it would require the entire chain being rewritten back to your transaction which disassociated those coins. Of course, this applies to any transaction which uses a block chain. Wait for as many confirmations as necessary (which during a contentious hard fork, where both chains use the same proof of work, would be far more than usual).