How do I split BCH/BSV?

Bitcoin Cash hard fork and reply protection.

On November 15, Bitcoin Cash was hard-forked and split into two separate chains, Bitcoin ABC and BitcoinSV. These are two different and non-compatible blockchains with two different teams that follow their own rules. However, there is no replay protection between them. It means that either of your BCH (ABC)/BSV transactions will be available on both chains simultaneously (double-spend). 

To prevent that, you need to split BCH from BSV before sending money. Splitter tools mix each of your transactions with a special one. This measure helps make each transaction unique and prevent networks from simultaneous broadcasting.

How to split your BCH/BSV?

Atomic Wallet doesn't provide a splitter tool. To split BCH and BSV, you need to do the following:

  1. Open Atomic Wallet and search BCH and BSV.
  2. Open your account on an exchange that supports both forks (Binance, Poloniex, Kraken etc). 
  3. Send either BCH(ABC)/BSV from your Atomic Wallet address to your exchange wallet address. Once sent, you will see both currencies gone.
  4. Once the transaction is complete, you will see both currencies deposited to your exchange wallet address.
  5. Withdraw either of BCH or BSV back to your Atomic Wallet address. You will see the currencies going separately.

Once withdrawn, you can use these coins separately from your Atomic Wallet. 

Important: Bear in mind that if someone sends you unsplit coins, your BCH and BSV might get split again. In that case, you will have to repeat the procedure.

If you didn’t split your BCH/BSV coins the double-spend error may occur. You may find both coins to be gone if you performed a swap with one of them. For example, you swap BSV for BTC, but also your BCH is gone. If that’s the case, please contact our support or about the swap. They will make a refund. However, the refund may take 2 weeks and longer. Be careful and make sure your coins are split before making operations with them.

Did this answer your question? Thanks for the feedback There was a problem submitting your feedback. Please try again later.