How are you installing 0.21.1? Which file did you download from bitcoincore.org?

Did you download the "exe": https://bitcoincore.org/bin/bitcoin-core-0.21.1/bitcoin-0.21.1-win64-setup-unsigned.exe
or did you download the "zip": https://bitcoincore.org/bin/bitcoin-core-0.21.1/bitcoin-0.21.1-win64.zip

If you downloaded the .exe, then it should have "installed" 0.21.1 into the default location (C:\Program Files\Bitcoin) overwriting any previous version. If you downloaded the .zip and extracted it, it will just run from the directory where you extracted it... any existing shortcuts in the Start menu will likely continue to point at the "old" version in the default installation location.

That is to say, if you "installed" 0.17 using an .exe and it is in "C:\Program Files\Bitcoin"... if you download the 0.21 .zip file, and it is in C:\Users\YOURUSERNAME\Downloads\bitcoin-0.21.1-win64 and you run it from there... then 0.21 will open... but if you use the Start menu shortcut, it will likely start up version 0.17 instead!


As someone else already mentioned, there is also a possibility that something is "broken" with your Windows 10 install, and it is automatically restoring a previous "Restore Point" from before 0.21 was installed.

If this seems to happen overnight, it might be caused by an automatic windows update that is restarting your PC, encountering an issue and then restoring.

Is your wallet a "[2fa]" wallet? Is that what it says in the title bar next to the wallet name? Like this:


If it says [2fa], you will not be able to get the correct seed out of the app... as you have a 2 Factor Authentication wallet... and only 1 out of 3 master private keys is stored in the wallet file.

If you don't have the actual seed written down somewhere, you won't be able to recover the wallet. At best, you could create a new transaction and send funds out... but that would require that you have the Google Authenticator code setup.


If it doesn't say "[2fa]"... what does it say? "[standard]" or "[imported]"?

Seems the take away from all this is that while backups are not strictly necessary (as you can always just resync)... they can be a huge "time saver"!

36.5 hours to sync ElectrumX is fairly slow. Even electrs on my Raspberry Pi 4B didn't take anywhere near that long to build it's databases.

From memory... BRD is (was?) leveraging something like BitcoinJ and connects directly to Bitcoin node's, like Bitcoin Wallet for Android... rather than connecting to wallet specific servers like Electrum does.

As such, the syncing is generally a little slower, as it is using Bloom Filters from "random" full nodes, as opposed to dedicated servers etc, but obviously still faster than doing a full blockchain download and verification.

Enter "FastSync"... which is basically BRD's version of a "custom server" like ElectrumX/electrs/EPS etc, but from what I can tell is hosted by BRD themselves... you can read more here: https://brd.com/blog/fastsync-explained

I can't say I've ever experienced an app shutting down a VPN connection (excluding the actual VPN app itself of course)...

Is your device rooted?

As I mentioned earlier, Ledger Live claim that it is automatically verifying the download for you when you use the update button...


So, theoretically, there is no need to verify anything if you use the "in app" update button... you only need to manually verify the installers that are downloaded manually.

Sounds like you had no Bitcoin on the key/addresses generated by that seed at the time of the fork. If you loaded that seed into Electrum and it showed a Bitcoin balance as at 1 August 2017, it should also have had Bitcoin Cash.

Loading the seed into Electron Cash, did it show any history at all? Were the BCH coins moved after the fork?


Those old "non-12" word phrases (ie. 15, 16 or 17 words etc) generally tend to be a "password recovery" phrase for blockchain.info... not a "seed" as such.

You can attempt to use it here: https://login.blockchain.com/wallet/forgot-password

What fixed the issue you were having with Bitcoin Cash? It might be helpful for anyone else finding this thread later if you could explain what you did to get it.


I believe the "official" website is: https://electrumsv.io/

But I offer no guarantees, use at your own risk

If I understand Dave's somewhat obtuse comment correctly, it would appear that his eyesight is failing him

@DaveF, if it makes you feel any better... I'm probably not far off needing to do the same!

I'm confused by your logic and reasoning here... You can totally using existing seed phrases/master public keys to create a MultiSig wallet. Yes, it will generate different keys/addresses, but you can still create a MultiSig address using them.

What do you mean by a "single pubkey" wallet? Do you mean a wallet that has been imported using WIF keys? Because they don't even have master public keys... and Electrum doesn't even support creating single address MultiSigs... it has to be done using seed phrases or master keys.

The portable version is no more "insecure" than the normal windows installer or standalone version.

So, assuming you have taken the proper precautions... ie. confirmed digital signature of Electrum portable download and have taken steps to ensure your "personal" computer is malware and virus free... then it should be perfectly fine.

The dangers associated with the portable version are that it can lead to "dangerous" or "risky" behaviour... ie. putting it all on a USB stick and then using that USB stick on computers that you have no control over. For instance, public computers, internet cafes, other people's machines etc. where you have no idea what is/isn't installed or running on them.

Your Bitcoin Core was pruned? Well that would certainly prevent Armory from working properly.



Depends on what you want... If you want to continue using Armory, then you'd be advised to get Bitcoin Core fully synced and NOT pruned, and Armory connected to it.

If you just want your coins out, export the keys, import into Electrum and send them wherever you like.

It sounds like your "max Gas" value might not be high enough for the Gas required to execute the transaction you're attempting.

What wallet are you using? If the wallet you're using is something like MyCrypto, they have some reasons for this error listed here: https://support.mycrypto.com/troubleshooting/sending/gas-required-exceeds-allowance-or-always-failing-transaction

The old "legacy" format Bitcoin Core wallets will just scan all 3 variants of an imported WIF key... I'm not sure what happens with the new descriptor wallets, but given that you can specify the script type in the descriptor, it's possible it may only scan the one you specify (again, not 100% as I haven't played with descriptor wallets very much, and I think can also import WIFs into descriptor wallets).

Mycelium just does all 3 and you can "tap" on the screen to swap between Legacy, Nested and Native Segwit etc.

Electrum will only do one type per wallet file for HD wallets...  but for imported key wallets, you can mix and match... if you want to scan all three, you just put the private key in three times, once with each prefix.

mocacinno is correct... you cannot convert an existing wallet so that it is MultiSig and has the same addresses as the existing wallet. Once you create the MultiSig wallet, the addresses will be different.

However, you can use your existing wallet as one of the parts of a MultiSig setup.

The short answer is... Yes, it'll be fine.


Your wallet file won't be upgraded to use either bech32 or lightning... it will look and function identically to how it does now. The new features are mostly optional extras... except for bech32 being the only option for newly created Electrum seed wallets now.

But, as noted, pre-existing wallets will continue to use the address types they were originally created with.

dblog.txt should be in the same directory as armorylog.txt

If you haven't manually modified the Armory data directory, then it should be:

To be 100% sure what the Bitcoin data directory actually is, you can simply open Bitcoin Core GUI... look in "Window -> Information"... and see what the value for "datadir" is:


If it isn't "C:\Progam Files\Bitcoin" then you've setup Armory incorrectly.

Honestly, you should NOT be using C:\Program Files\Bitcoin as a datadir... as newer versions of Windows treat C:\ as being somewhat protected as it is the system drive... and you can often end up with really weird permissions errors if you're trying to read/write from certain directory paths


EDIT: oops, thanks nc50lc #ninjaedit

Found an interesting note in the "Bitcoin deterministic wallet compatibility" spreadsheet that is available here: https://onedrive.live.com/view.aspx?resid=584F122BA17116EE!313&app=Excel


It seems that prior to version 1.4... Mycelium for IOS was using a "different" derivation path:





So, I would suggest that you try and import the seed into Electrum, when prompted for the script type/derivation path, Click on the "legacy (p2pkh)" option... and then change the derivation path from: m/44'/0'/0' to: m/44'/0'/0'/0

The screen should look like this:



Hopefully that will find the missing addresses/transactions/coins etc.

It's not exactly a new idea is it? I could swear there were reports of clipboard hijacking malware that did exactly this (contact a cloud based server to get a suitable "fake" address) at least 2-3 years ago.

Is it just the shear volume of available replacement addresses that is news?