People like to say there are no dumb questions, only dumb answers... but then again, your question has been asked (and answered) multiple times. So, it is probably classified as an "unnecessary question".

If you're already in the "Beginners & Help" (aka B&H) section, you should really have read the sticky posts at the top like this one: Newbies - Read before posting

There is a LOT of very good information in that thread... like this:


That last link leads to a post by theymos describing the merit system and how it affects ranks. This post starts with:

It depends on your viewpoint. What if you sent something to someone by mistake... this "feature" allows you to correct that mistake.

Additionally, it does allow for more certainty that anything deleted stays deleted (assuming you do it quick enough and the other party hasn't taken screenshots etc). As DireWolfM14 said, it's a tool... and like any tool it can be abused.

As long as you understand how the system works, you can protect yourself from the abuse. Sadly, the "scam accusations" board is littered with instances of people who don't understand how the system works

It might be a secure messaging system... but it's certainly not a "secure" system for trading!

Can't say I've had any real issues with Windows10+Ledger Live+Ledger Nano S

Are the glitches you are seeing with it stuck on the bootloader when you're attempting to update the firmware on your Nano S devices? Or was it just when you attempted to connect your Nano S to the computer to use it normally (ie. making a transaction)?

That depends on whether or not a password was used and/or whether or not full file encryption was used.

Electrum supports THREE different options:

1. Unencrypted (wallet is stored in plaintext)
  - No password required

2. "Secrets only" encrypted (wallet is still plaintext, but the "secrets" (private keys/seeds etc) are encrypted)
  - Wallet will open without the password, but password required to send transactions/view seed and private keys etc

3. Full file encryption
  - Wallet will not even open without password


In any case, the file itself is just a simple text file... not sure you'll find a "standard" hex pattern that will guarantee identification of an Electrum wallet file.

In cases #1 & #2, a plaintext file search for: "wallet_type" should find those...

In case #3, I've some that end in == and some that end in = and some that don't...

The issue is indeed most likely due to your firmware being outdated. You will need to update it if you want to use Ledger Live.

Do not be concerned about installing a new firmware IF you have access to the 24 words recovery seed mnemonic. If you have the 24 words, you will be able to fully recover, even if you completely wipe your device. So, before you attempt anything else, do you have those 24 words which should have been written down when you setup your Ledger?

Firstly, don't lose hope. It's just a "simple" network issue. Your coins are most likely safe. You can confirm that by checking your address on a blockexplorer website.

What country are you located in? There have previously been issues with certain countries blocking network traffic that affects ones ability to use Electrum. Users have had to use proxies/VPNs to get around this.

Do you have any Antivirus or Firewall software running? What OS are you using?

It's not a bad theory... the issue likely being that unless he is actively promoting it to appear at the top of Google search results, then the chances of someone stumbling across this site is actually quite slim.

From what I've seen/read regarding users ending up on these fake bitcoin sites... it's down to the fact that it was "the first result on Google" There isn't really any way to combat that except to pay for all the keywords!

No. There are plenty of examples of coins being listed on the "big" exchanges that have "crashed and burned" and are now mostly worthless...


It's definitely not insider trading. Insider trading is using private (aka "insider") knowledge to gain an advantage. Like for instance, say you worked at Company A and knew that Company A had just scored a massive defence department contract worth billions of dollars but the deal had not been publicly announced. Going out and buying as many shares as possible of Company A before the public announcement would be "insider trading".

It could potentially be a conflict of interest... for instance if Brian Armstrong could somehow "force" Coinbase to start massively promoting "Aella" to try and pump the price or something... but I don't see that being a very realistic scenario.

Given that it's public knowledge he is backing it... and also that he works at Coinbase... it would be hard to achieve anything like that without being publicly called out on it.

And that is specific to the GPU slot only? Does it make any difference adding that to the CPU slot as well?

Do you have an alternative source for this information? linustechtips.com seems to be down at the moment... I'm getting cloudflare errors

Sorry to hear that... Since I stumbled across the daily raffles, I've quite enjoyed:

1. Trying to catch the announcements due to my timezone
2. Failing spectacularly at picking the correct number!  

The pandemic has certainly impacted on so many facets of our lives... travel, shopping... and now sending/receiving mail

So thanks for all the raffles so far... and I look forward to playing again when things get back to something resembling normalcy. Stay safe everyone!

I'm not sure all that work is necessary.

The page, while not looking "fancy", certainly gets across the main message. "This *was* a fake site, if you downloaded from it, you've downloaded a fake version of Electrum. Here are some helpful links".

I don't think it needs a "beautiful" design to get that message across. In fact, it might be better that it doesn't look fancy. One could argue that people are more likely to notice something that doesn't look "normal" and maybe take the time to stop and read what looks like "error messages"... as opposed to thinking they just clicked on the wrong thing and click "back" to return to search results etc.

I honestly don't know that answer to that question. It could be that, or it could have simply been the more common "no route"-type issue. I had a few of those at various times (with lnd etc)... sometimes channels drop off and you can't get a payment route.

But yeah... a nonfunctional libsecp256k1-0.dll might cause issues.

You can sign with it, but not using the default HD blockchain.com wallet. It requires a bit of a workaround and you would need to export your private keys out of blockchain wallet and then import them into another wallet and use that... for instance:

1. Use your 12 word backup phrase from blockchain.com and create a "BIP39" wallet within Electrum. Electrum would then have the same addresses as your blockchain.com wallet and would let you sign using your "blockchain.com" addresses

or

2. Use your 12 word backup phrase from blockchain.com with an (offline) copy of Ian Coleman's Mnemonic code converter. That will give you the private keys for your blockchain.com addresses, you can then use those private keys and import them back into blockchain.com... it should let you sign a message with one of those imported addresses.

NEITHER of these options should be used lightly and without taking adequate precautions to secure your 12 word backup phrase and/or private keys.

In other news... mocacinno has been kind enough to provide a small file hosting repository for me... so, in future I'll be able to get 4.0.0 builds uploaded there instead of having to rely on free file hosting sites that have popups and ads and shit like that.

As you can see, aside from my current build, it also has my PGP signature (hcp_pgp.asc) and a .sig file for the build itself. You can also see the instructions in the README for how to retrieve my public key from keybase.io.

Again, big thanks to mocacinno... he really does an awful lot for our community!

I concur... it's looking more likely to be caused by either:

1. BIP39 Passphrase

or

2. Incorrect backup seed

In both of these cases, recovery could prove very difficult if OP doesn't recall details of either

The problem isn't the large number of addresses... it's the fact that large numbers were used for the "address_index" value in the derivation path.

ie. something like: m/44'/0'/0'/0/1000000000

Obviously, as Electrum works sequentially from 0, getting up to the "billions" value is going to take a while (and something it wasn't really designed to do).


Hadn't noticed that Ian Coleman's tool had that "starting index" feature! brilliant stuff...

Yeah... the reason why the account extended key would be different is because the derivation path that a given coin uses should have a different "coin_type" value:

m / purpose' / coin_type' / account' / change / address_index

So, for Bitcoin it would be m/44'/0'/0'/0/0 but for BCH it would be m/44'/145'/0'/0/0

If you simply use the Bitcoin path in a BCH wallet, it will work and should provide the 'same' addresses (assuming the BCH wallet allows custom derivation paths). This is basically what Ledger did for their "split" wallet when the BCH fork happened. Ie. It allowed you to access the BCH in you BTC derivation path.

So-called "Registered" coin_types can been found here: https://github.com/satoshilabs/slips/blob/master/slip-0044.md

As achow101 said... you don't need to mess about with the pywallet dump or inspecting the wallet.dat file. Even an encrypted/locked wallet.dat can be loaded and viewed in Bitcoin Core without knowing the passphrase.

You only need to use the passphrase should you wish to do anything involving the "private" data... that is to say, any action requiring access to private keys (such as dumping the wallet.dat, signing a transaction, exporting private keys etc).

So, if you simply put the wallet.dat in the Bitcoin Core data directory and start Bitcoin Core, you'll be able to see the entire transaction history, all the addresses AND any labels that were given to addresses/transactions.

I had that exact error initially... it's because it is generating the wrong "type" of dll... ie. 32bit instead of 64bit.

Refer: https://github.com/spesmilo/electrum/issues/5976#issuecomment-589809870

If you're building manually outside of the docker "fresh_clone"... you need to ensure you have "gcc-mingw-w64" installed:

Then make sure you set the correct GCC_TRIPLET_HOST variable when running contrib/make_libsecp256k1.sh. I believe the comments in contrib/make_libsecp256k1.sh were updated to reflect which command you needed. Refer: https://github.com/spesmilo/electrum/commit/875e6b31b1d4fa0e133a7176e7592361c45beee7