Post
Topic
Board Bitcoin Technical Support
Re: What's the current state of replay protection for the forks?
by
LoyceV
on 13/12/2023, 15:24:21 UTC
BSV
Looks like a dead ecosystem. The main website looks like bizarre propaganda for CSW, with little to no information about the technology. There is an electron fork that doesn't look maintained. Only have binaries available for Windows and Mac. No AppImage or deb file for Linux, have to build from source. Tried to build from source but it only supports up to Python 3.9.X. Tried to build with 3.10 but lots of errors. Doesn't look widely supported on exchanges and for the pittance I would be collecting here, my time is worth more than this.
To quote myself:
It's the most annoying one with the shittiest wallet software

You can use the lack of replay protection to create a signed transaction on a BCH wallet, then broadcast it on the BSV chain. Here's how I did it:
BSV's lack of replay protection was once again the solution to my problem Cheesy
This is how I recovered BSV that was sent to pubkey (many years ago):
  • First, move BCH and eCash to a new address
  • Install a fresh spare laptop (with VPN of course)
  • Download the full BCH client (the one Forked from Bitcoin Core) (note: I do not trust this software, but used CoinMarketCap.com to find the "official" website)
  • Import the pubkey, let it synchronize the first few years (until the coins show up, but before they are sent out (after all, you should have moved your BCH out of this address already))
  • Take it offline
  • Import the private key
  • Create a raw transaction to a new address (this transaction won't be valid on the BCH chain, but will work on the BSV chain). Just in case, I used a legacy address
  • Copy the transaction to a USB stick
  • Check it (I used BCH's Electrum Fork for this, in a VM), and broadcast it online on the BSV network
  • Use another device to broadcast the transaction on the BSV network. I used https://whatsonchain.com/broadcast (on Tor)
  • Wipe the laptop (don't let it go online again after you entered the private key!)