ChapInRed gave me permission to share his PMs about
claiming BSV from old sent-to-pubkey transactions.
First: move your BTC to a safe new wallet. Then dust your BCH and eCash addresses to make sure you have replay protection. Move BCH, BTG, eCash and BCD to a new wallet. Now all that's left (ignoring the worthless forks) is BSV. BSV is the most annoying Fork with very shitty software. Don't trust it on your main computer, use a spare system or VM (and wipe it afterwards!)
Forget ElectrumSV:
Use BSV's Bitcoin Core clone (which doesn't have a GUI):
Start again with bitcoind, sync blocks for a while, take offline, backup the .bitcoin folder to use again later
Import one private key so I only have one UTXO to possibly use at once.
bitcoin-cli sendtoaddress "[receiving address from ElectrumSV" <amount-in-address> "test" "ElectrumSV" true(true at the end is for
subtractfeefromamount)
bitcoin-cli gettransaction [hex string from output of above]Copy the hex transaction string from this
Checked it in
https://whatsonchain.com/decode - looks correct
Tried to broadcast it on
https://whatsonchain.com/broadcast~
I can restore the .bitcoin folder and do each of those 2 private keys in turn.
it worked! 6 confirmations
~
Yes, the importing one privkey at a time method was just to do simple coin control. Looks like the lockunspent command would be another way.
Happy for you to quote or reuse as you wish. As we're using an incomplete blockchain on disk, the conf file needs disablesafemode=1 added somewhere, otherwise you get nowhere (at least with the commands I was using).
I just started bitcoind in one terminal (using Ubuntu) and once that was running without throwing errors, I entered the bitcoin-cli commands in another terminal. bitcoin-cli stop will stop bitcoind gracefully.
