<p>No, there is no such problem. When BCH developers thought about introduction replay protection, they first agreed on the OP_RETURN-based one. Then they changed their minds and decided to use the better SIGHASH_FORKID-based one (see <a href="https://bitcoin.stackexchange.com/a/56874">details about BCH replay protection</a>).</p>
<p>Their first replay protection wasn't removed. It expired with block 530,000. After that block, unless you had moved your coins, it would have been impossible to separate your coins using that method.</p>
<p>That didn't matter to anyone then, since the second replay protection method introduced was made mandatory and worked perfectly. It was actually good enough to be exemplary (Bitcoin Gold copied it).</p>
<hr />
<p>If you have pre-2017 coins, then you have BTC, BCH, BCHA, and BCHSV. To split those, send your bitcoins and BCHs to Coinex and they'll split it for you. (It is suggested to check that your transactions don't have nLockTime.)</p>

CC BY-SA 4.0
2021-02-09T16:03:48.083Z
2021-02-09T16:56:55.620Z
2021-02-09T16:56:55.620Z
MCCCS
<p>I was speaking to a friend that mentioned that there were issues with pre-forked Bitcoin coins from Aug 2017 that never moved. He wouldn't tell me exactly what the potential issue was, but what were some discussed or potential issues with these unmoved pre-fork UTXOs?</p>
<p>Is it a potential double spend that could happen on these coins that never moved?</p>

CC BY-SA 4.0
2021-02-09T19:10:23.740Z
A potential issue I can imagine is that if you have BTC coins that never moved since the BTC-BCH fork, and you want to sell the BCH side using a recovery tool, you'll need to expose your private key to it - and that private key can be used to access your BTC as well. That's obviously a risky proposition, and it's better to use trustworthy software regardless. Still, my advice would be to move the BTC coins before trying to recover BCH; not for replay risk, but to avoid needing to expose a potentially live private BTC key.
Pieter Wuille
CC BY-SA 4.0
2021-02-10T14:31:37.873Z
Didn't the exchanges at that time have to modify their bitcoin software to extract these forked coins at one point?
Patoshi パトシ
CC BY-SA 4.0
2021-02-10T16:21:59.700Z
Possibly, but that was just due to the fact that BCH signatures worked slightly differently (and that's exactly what brings the replay protection).
Pieter Wuille
<bitcoin-cash><blockchain-fork><doublespend><utxo><utxo-set>
What were some discussed and current potential issues with pre-forked Bitcoin coins from August 2017 that have never moved since then?
Patoshi パトシ
# What were some discussed and current potential issues with pre-forked Bitcoin coins from August 2017 that have never moved since then?

(Asked by: username_0 on 2021-02-09)

I was speaking to a friend that mentioned that there were issues with pre-forked Bitcoin coins from Aug 2017 that never moved. He wouldn't tell me exactly what the potential issue was, but what were some discussed or potential issues with these unmoved pre-fork UTXOs?

Is it a potential double spend that could happen on these coins that never moved?

**Tags:** bitcoin-cash, blockchain-fork, doublespend, utxo, utxo-set

> **Comments:**
> **username_1**: A potential issue I can imagine is that if you have BTC coins that never moved since the BTC-BCH fork, and you want to sell the BCH side using a recovery tool, you'll need to expose your private key to it - and that private key can be used to access your BTC as well. That's obviously a risky proposition, and it's better to use trustworthy software regardless. Still, my advice would be to move the BTC coins before trying to recover BCH; not for replay risk, but to avoid needing to expose a potentially live private BTC key.  
> **username_0**: Didn't the exchanges at that time have to modify their bitcoin software to extract these forked coins at one point?  
> **username_1**: Possibly, but that was just due to the fact that BCH signatures worked slightly differently (and that's exactly what brings the replay protection).  

---

## 1 answers

### Answer by username_2 on 2021-02-09. Score: 1 | Accepted answer

No, there is no such problem. When BCH developers thought about introduction replay protection, they first agreed on the OP\_RETURN-based one. Then they changed their minds and decided to use the better SIGHASH\_FORKID-based one (see [details about BCH replay protection](https://bitcoin.stackexchange.com/a/56874)).

Their first replay protection wasn't removed. It expired with block 530,000. After that block, unless you had moved your coins, it would have been impossible to separate your coins using that method.

That didn't matter to anyone then, since the second replay protection method introduced was made mandatory and worked perfectly. It was actually good enough to be exemplary (Bitcoin Gold copied it).

---

If you have pre-2017 coins, then you have BTC, BCH, BCHA, and BCHSV. To split those, send your bitcoins and BCHs to Coinex and they'll split it for you. (It is suggested to check that your transactions don't have nLockTime.)


---

