If the address on the ledger device screen, matched the address he was shown in Ledger Live, then he should be "OK".

Note that clicking "approve" on the device doesn't actually do anything... It is just there as a sort of trigger to try and make the user take the time to actually double check that the 2 addresses do in fact match. You don't need to click approve to be able to receive coins.

You can in fact get a "receive" address from Ledger Live without even having the device connected, although this is NOT recommended (as you cannot confirm that Ledger Live is giving you the correct address! )

No... the script selection specifies the script to be used (ie. the type of address you want to generate, Legacy, Nested Segwit or Native Segwit). The derivation path is the path you want to use to start generating keys. Electrum will then follow the derivation path to start generating private keys... and from those keys, will use the specified script type to convert it to an address.

If you only use one account in Ledger Live... then, as Abdussamad suggests, you will NOT need to modify the derivation path, simply select the script type, the derivation path will default to the correct setting.

However, if you do use multiple "accounts" in Ledger Live (ie. You have Bitcoin Native 1 and Bitcoin Native 2)... then you WILL need to modify the derivation path AFTER selecting the script type, as Electrum only allows ONE account per wallet.

Also, you can use ANY derivation path you like, in combination with any script type... Electrum won't care. For instance, if I select "Native Segwit"... and ridiculous non-standard derivation path:


I get Native Segwit addresses:


If I select Legacy, with the same derivation path... I get Legacy addresses:



And you can see that because they have the same derivation path... they are created from the same private key... they just use a different script type:



Test BIP39 seed used: domain average merry rare quarter again cute mango trend gasp strategy fade

1. Create a SegWit wallet in Electrum
2. Click "Receive" tab in your SegWit wallet and copy the address
3. Click "Send" in your legacy wallet, paste the SegWit address
4. In the amount box, type a ! (this will send ALL the funds minus the fee)
5. Set the fee to what you want either with slider or manually

Based on your other thread, PyWallet is not going to be of any use to you. PyWallet is more useful for recovering accidentally deleted wallet.dat's and/or dumping private keys from wallet.dat that you know the password for (or that are unencrypted).

It won't help you bruteforce the wallet password... and it won't be able to extract private keys without the password.

Or, if you're going to end using Bitcoin Core anyway... you can save yourself a lot of hassle and simply use the Bitcoin Core console/cli and do: getnewaddress "" "p2sh-segwit" and it will automagically create a new P2SH-P2WPKH address for you.


ps. there was a slight typo in your 3rd paragraph:
Should be "segregated witness".

Otherwise a comprehensive guide.

Unfortunately, this is not the correct forum to seek help for hardware issues such as this. You'd either need to try asking on the "Altcoin Mining" board (NOTE: the bitcoin mining board only deals with ASIC related hardware issues, not GPU)...

or, better yet, seek assistance on an external Computer Hardware dedicated forum like Tom's Hardware or Linus Tech Tips or something like that.

If you're hoping that you could just bruteforce the private key by figuring out which part of the keyspace your private key is in based on just the public key/address... then you're trying to do the "impossible". The nature of SHA256 hashing etc makes it impossible to figure out where in the keyspace your private key comes from.

If this was actually possible, then bitcoin would be fundamentally broken and useless. As anyone could take any given address, figure out the keyspace to look in and start bruteforcing away. No one's coins would be safe.


If you don't actually have the original or a backup of the wallet data file, or a seed mnemonic or "most of" the private key... and all you have is a public key/address... then your coins are lost.

Is it still opening the Testnet wallet? It sounds like you were possibly using the wrong "shortcut" to start Bitcoin Core... The installer will create two:



And because Windows 10 is a bit stupid sometimes (all the time?)... it can sometimes select the TestNet version as the "best match" if you click "start" and start typing "Bitcoin"

Given that you can generate any script from a given private key, logically that makes sense... the radio buttons are telling Electrum what script type you want from generate from your keys... whereas the derivation path is just that, the path to use to get to the keys you want to use. The fact that certain script types default to specific derivation paths is irrelevant. You can use whatever you want, and Electrum will go ahead and use it.

Fancy generating native SegWit addresses from a BCash derivation path? Feel free!  

That's one of the beautiful things about Electrum, it lets you do a lot of weird and wonderful things. The onus is then on the user to remember whatever "non-standard" stuff they have choosen to do.

No...  For all the reasons outlined by o_e_l_e_o, it is simply impossible to create a "foolproof, 100% accurate, fee estimation model". The goalposts are always shifting... the best thing someone can do is learn how to interpret the information available, and then make a decision based on that information and their personal requirements. Some people want/need "next block", some people want "cheapest", some people want "cheap but relatively quick"... by looking at the mempool data, you can get a feel for what the network is up to, and what you're going to need to pay to try to achieve your desired goal.

Simply relying on a website that says "pay X sats/byte" will often lead to:

a. overpaying
or
b. confusion when a transaction doesn't confirm with the next block like the "bitcoin fee website" said it would

It's like relying on bitcoin wallets that have "economy", "standard" and (so-called) "high-priority" fee estimates.

At the end of the day... there is no reason why you can't use both Electrum and Ledger Live. I do... and it doesn't cause any issues.

Ledger Live is necessary for installing/removing coin apps, doing firmware upgrades etc. So, you're definitely going to need to use it at some point, so you may as well install it and experiment with it. It's quite handy for viewing your entire portfolio as well if you are holding multiple coins).

But I also appreciate some of the more advanced features in Electrum, so will use that as well when I need to make sure of those features (coin control, pay2many etc).


Nope. Ledger Live works perfectly fine with Windows 10. That is exactly what I am using. The issues people were having was trying to use Ledger Live on unsupported versions of Windows... ie. Windows 7.

There were some recent issues with some overzealous antivirus programs incorrectly detecting the installer as being infected ("false positives")... and some recent issues with the update process being a bit screwy... but as far as I'm aware, Ledger Live+Windows 10 is OK.

Unfortunately, without the 12 word seed mnemonic, you will be unable to restore your ETH account (and the ETH private keys) that were generated by your Mycelium wallet.

The xprv that you have is BTC specific... it's derived from the seed (that would be restored from your 12 word seed mnemonic)... but you cannot go from xprv -> seed... only seed -> xprv.


Mycelium also supports adding an ETH account and ERC-20...

You could potentially be waiting for quite a while (as in hours if not days):


There are currently some 30+ blocks worth of transactions all sitting at the 2+ sats/byte type fee range... which is about what your #2 & #3 transactions were set to... #4 is higher, but is effectively a CPFP of #3 (which was quite big at 635 bytes)... so with #4 being 258 bytes... the combined size is 893 bytes with a combined fee of 0.00002528 + 0.00003375 = 0.00005903... which only gives ~6 sats/byte... or 1.5 sats/WU.

If you're really lucky, and it stays "quiet" and there aren't many more transactions broadcast... #3 and #4 might confirm in the next hour or so... but #2 could stay unconfirmed for quite a bit longer!

Basically, your only option is to try and bruteforce it... or engage the services of someone else to bruteforce. There is no "magic bullet" that will allow you to access your funds. If you haven't been able to bruteforce the password in the last 10 months, then there is a good chance that the Hashcat mask(s) you've been using is/are no good.

Can you please share here what hashcat settings you have tried?

In your friend's Ledger Live, when he clicks on "Receive" (to get a receiving address)... Which of the following 3 options is the "Account to Credit" listed as? :

- Bitcoin 1
- Bitcoin 1 (legacy)
- Bitcoin 1 (native segwit)

You do if you want to use (or you have already setup in Ledger Live) more than 1 account on your Ledger. As far as I'm aware, Electrum does not "search" for used addresses in accounts higher than the 'default' account of 0.

And then do everyone a favour and send a message to Paxful support and tell them to implement support for SegWit addresses. It has been a long time since it was introduced, and forcing users into using Legacy wallets does not help adoption.

No... RBF was rolled into Bitcoin Core in v0.12... which was released in February 2016.

That's a full 2 years BEFORE v0.16 (Feb 2018).

The thing is that RBF was, and still is, Opt-In. You have to specify that you want your transaction to be RBF:



You can set it to default to this by using walletrbf=1 in your bitcoin.conf file

You do realise that changing the password for the wallet.dat on your local computer does absolutely NOTHING to other copies of that wallet.dat right?

I especially like the way you have the notepad reminding yourself to send 1 BTC to iasenko and math09183 ... I also like the way you have the "new password" shown in your video

As Dave pointed out, there is nothing stopping you from using "dumpprivkey" or "dumpwallet" or signing a message from "1GRth6rP4uaPXdw2T6HcGmi7f1RzW4xV94" while Bitcoin Core is resyncing. There is no need to "wait another month"

Except for the fact that you can't sign a message from "1GRth6rP4uaPXdw2T6HcGmi7f1RzW4xV94" can you? 

Yes, it is ridiculously easy to do.

When you do the initial wallet setup (note that it pays to Connect/unlock Ledger Device and select the Bitcoin App before you begin): New/Restore -> Standard Wallet -> Use a hardware device -> [Select your Ledger Device shown]...

You'll end up on this screen:



Simply select the script type that you want (Legacy, Nested Segwit or Native SegWit)... and optionally, as BitCryptex mentioned, modify the derivation path to see the account you want.