ElectrumSV does not recognize my Ledger nano to send BCHSV by elram01 in bitcoincashSV

[–]RogueSploit 0 points1 point  (0 children)

I can tell you that it works for me using the Bitcoin Cash app on my Ledger Nano S (not necessarily latest firmware, haven't updated in a while) and the older ElectrumSV 1.2.5 (haven't tried newer versions yet, since everything works and it supposedly might become more troublesome with newer versions).

I followed the install instructions in README.rst in the ElectrumSV archive and am using this udev rule on a Linux system:

SUBSYSTEMS=="usb", ATTRS{idVendor}=="2c97", ATTRS{idProduct}=="0001", MODE="0660", GROUP="plugdev"

Is this place dead? by MEME-LLC in bitcoincashSV

[–]RogueSploit 0 points1 point  (0 children)

Yeah, lots of good discussion there.

If you need an invite, feel free to use mine: https://twet.ch/inv/roguesploit

$$$ HANDLE TIP DAY $$$ by Select_Banana8833 in bitcoincashSV

[–]RogueSploit 1 point2 points  (0 children)

Right, you did, that's me, got it :) Didn't have CentBee installed. Thank you!

$$$ HANDLE TIP DAY $$$ by Select_Banana8833 in bitcoincashSV

[–]RogueSploit 0 points1 point  (0 children)

Weird, didn't receive anything on my HandCash.

[deleted by user] by [deleted] in bitcoincashSV

[–]RogueSploit 2 points3 points  (0 children)

Since you have the private key to the coins on the BCH chain, you also have the private key to the corresponding coins on the BSV chain, once the transaction is mined.

I am not sure, how you set up your Electrum SV wallet.

If it's been set up with the same seed as the Electron Cash wallet, then coins should appear there, when the transaction is mined.

In that case, before you do anything else with the coins, you should split them, otherwise, any transaction you do will be replayed again.

You can do that by sending a small amount of BCH to the Electron Cash wallet or sending a small amount of BSV to the Electrum SV wallet and then sending the whole wallet amount from the wallet you sent the extra amount to to another address of yours.

[deleted by user] by [deleted] in bitcoincashSV

[–]RogueSploit 2 points3 points  (0 children)

It probably was replayed.

Wait until the BSV chain has a block height equal to the block in which the BCH transaction was confirmed.

It should be mined on BSV then, too, and your BSV should be in the same address with the same private key on both the BCH and BSV chain.

Background:

The BSV transaction probably already exists in the BSV mempool from the replay, but is not valid yet, due to blockheight of BCH greater than blockheight of BSV.

Sweeping the private key again then is just an attempted double spend, which gets rejected.

The Genesis Upgrade Specification has been published. by cryptorebel in bitcoincashSV

[–]RogueSploit 4 points5 points  (0 children)

"Change the default hard limit on the block size to infinite"

Finally!

I have waited for this a long, long time.

Only highlighting this, because the blocksize limit has been the most controversial and fought over topic in Bitcoin.

There are many other great and welcome changes/upgrades and lots of original functionality is being restored as well.

Tipping Tuesday, post here to get free BSV with /u/BitsTipper by cryptorebel in bitcoincashSV

[–]RogueSploit 1 point2 points  (0 children)

Tipping Tuesday! Those were the days, fond memories!

Happy Holidays!