To salvage the wallet.dat make a copy or another backup of your wallet.dat first before the operation and put it in the bitcoin core wallet folder. After that run the Bitcoin core wallet -salvagewallet you can put it on Bitcoin shortcut check the image below as a reference
The -savagewallet command line option was removed from Bitcoin-qt/cli v0.21.0it's moved to 'bitcoin-wallet' tool as " salvage". Here's how to use the command using that tool: -snip-" bitcoin-wallet" is in the " daemon" folder inside Bitcoin Core's installation directory ( where bitcoind and bitcoin-cli are located). To use it, open Terminal, cd to the directory where bitcoin-wallet is. Then use the command ( provide the full path to the wallet.dat file): bitcoin-wallet --wallet="E:\Folder\wallet.dat" salvage It wont return with any response ( unless it failed) but you will see a backup file ( wallet.dat.xxxxx.bak) where the wallet.dat is located. The new wallet.dat is the " salvaged" wallet.
|
|
|
-snip-
Thank you. Unfortunately exporting the private key to a separate wallet didn't work, it's still stuck on synchronizing. Have you closed Electrum then renamed the wallet file that causing the issue before opening the newly created imported wallet? That is to make sure that it wont open when you run Electrum . Because it it's just thousands of transactions, it should work; it wouldn't if the original wallet is running in another instance or in the background since both will query the same server. Otherwise, I'd second the suggested 'Bitcoin Core' and disable " pruning".
|
|
|
That's "cool" but insecure. The number of fingerprint variations aren't even close to the total number of valid private keys.
Plus depending on the method; for example, if it's just based from basic details of the fingerprint (like our smartphone use), collisions may occur. You'll get unique results if the method is based from the 'minute details', however, a slight scratch could produce a different result.
...I think the technology is already available but no one wants to implement such idea.
|
|
|
-snip- Yes that's right. One of the addresses has thousands of deposits.
Please let me know what I can do to recover my funds! Thank you
A possible workaround is to create an imported wallet using the private keys of all the other addresses excluding the one with thousands of deposits. That's if the excluded address doesn't have a relatively large balance, otherwise, try to create another imported wallet with that address' PrvKey, it may work if not included with the rest. To export the keys from your wallet: Go to 'Addresses' tab (" View->Show Addresses" to enable the tab), right-click on an address and select " private key". Copy the private key including the script type ( eg. p2pkh:Kjs539fa9A.......). To create an imported wallet: Create a new wallet ( File->Restore->Type a wallet name), select " Import Bitcoin addresses or private keys"; Then paste the keys including the script type, one line per key. After that just make sure not to open the wallet that's failing to connect; renaming the wallet file from your drive should do the trick.
|
|
|
Based on the OP, it looks like it's your Private keys that are missing some characters. Anyways, for the address, try using www.walletexplorer.com. It has an auto-complete feature for the partial address that you will paste on their search box, the catch is: the address should at least been used once ( and not recent) for it to be registered to their database. Example: if you search for " 1BitcoinEaterAddre", it will automatically redirect you to " 1BitcoinEaterAddressDontSendf59kuE". More characters means more accurate search.
|
|
|
First thing is, your Electrum wallet wasn't an account like a bank, there's no central server that hodls the wallet/funds. That said, no one can restore a wallet aside from the owner (yourself) by using its backup like the "Seed Phrase", wallet file or private keys.
If you think the amount of Bitcoin ($12?) is worth recovering, you can ask the "repairer" if they can recover the files from the disk. Doing the recovery yourself is risky. The sole file that you need is the wallet file that has the same name as your wallet (default name: default_wallet, wallet_1, wallet_2, ...)
|
|
|
-snip- Probably I should give up all further attempts to make direct LN channel between my Electrum wallets. >:(
Same here like I've mentioned, that confirmed that I'm not the only one having trouble establishing a channel between two Electrum. :) Try to post a new issue on Electrum's Github Repository: github.com/spesmilo/electrum/issuesMaybe the Devs have a workaround. But first, use 'search' to look for similar issues .
|
|
|
-snip- Is there a risk that I can really mess things up irrevocably, or make matters much more complicated for myself, by reinstalling Ledger Live from their website? I'm not very tech savvy, so I don't want to make my life more difficult than it already is. Nothing if it concerns only Ledger Live. It's just an interface that your Ledger Nano use to watch the funds, the keys are safely stored in your Hardware wallet. Just make sure that you wont expose your " Recovery Phrase" anywhere, because some fake versions of Ledger Live ask the user to enter it in case you've downloaded a fake.
|
|
|
-snip- There is a message at on the top of my Ledger Live screen that says "Update to Ledger Live version 2.38.2 is available". On the right of that, it says "Download update". A few weeks ago, I clicked on this (without connecting Ledger Nano S, obviously), and it just kept going in circles, and never updated. It was useless.
If the in-app updater doesn't work, download the latest version of Ledger Live from their website instead, the install it over the old version. Link: https://www.ledger.com/ledger-liveIf updating Ledger Live doesn't work, then you'll have to update the firmware by other means.
|
|
|
-snip- I just completed setup for Trevor One.
I'm not here to answer since I don't use Gemini or " Trevor", but is that a typo? Because I haven't heard of a " Trevor One" hardware wallet and the site 'trevor.io' doesn't offer hardware wallet-related software
|
|
|
Link doesnt work The links in my reply? It's working at my end, I guess your ISP is blocking GitHub or some other reasons why you can't access it. Link opens but win-download button cant find the file, it says no longer on server Those links aren't supposed to be download links. Those are links to Electrum's repository ( just for reference) and to ThomasV and SomberNight which have their contact info.
|
|
|
Just like other custodial wallets, it depends on their fee-estimation algorithm that's partly based from the average size of the mempools.
After clicking "Continue", the funds wont be sent immediately, you'll see another window showing the fee rate and the previous info. There should be a settings icon near the fee where you can customize it.
|
|
|
What exactly is the fee when doing this? Because when I went to coinbase account and clicked on withdrawing btc from my coinbase account on my computer, for some reason I can't choose the amount of btc I want to withdraw. but the USD amount? Also why does it not show the btc amount that I am withdrawing on coinbase?
There's an " up-down arrows" button at the right-hand side of the send window, it will switch the value from fiat to BTC ( and vice versa). Yes, there's a fee. A selection of fee rate will be shown after you click " Continue".
|
|
|
IDK what that test is for though since the issue is about 'imported' wallet turning into 'imported - watching only' wallet. -snip- If it turned into a watch-only wallet, he wouldn't be able to export private keys since watch only-wallets don't have private keys. When he attempted to do that, everything was OK. Right... and it will display " watching only" beside the wallet type next to the wallet name ( at the title bar on top).
|
|
|
Link doesnt work The links in my reply? It's working at my end, I guess your ISP is blocking GitHub or some other reasons why you can't access it.
|
|
|
“Seeds were working on it, doesnt work on 4.1.5“ It means it opens the wallet, there is no checksum, but no history no balance, totally different wallet i think.
Ah, so it's basically something similar to v0.30 and v0.34's compatibility-breaking update to the key derivation. But unfortunately, I don't know if there's another update like that. You can try to ask the developers themselves from electrum's Github repository. Specially ecdsa ( ThomasV) and SomberNight. ( they have email address in their GitHub profile)
|
|
|
Seeds were working on it, doesnt work on 4.1.5 That can't be. Seed phrase has been compatible to the latest version since it's implemented, even seed phrase from v0.30 will work with the latest ( but wont restore the correct keys). There are other wallets that use(d) their own implementation of seed phrase/mnemonic backups that aren't BIP39. Example is blockchain.info's old account recovery phrase; you might have used other wallets aside from Electrum. I dont give up😂 one more question whats the first v1 version of electrum that broadcast on ecdsa.electrum.org -snip-
You mean can be downloaded from electrum.ecdsa.org? IDK but this is the oldest archived page of the site's download page: web.archive.org/web/20121109025628/http://electrum.ecdsa.org/download.html
|
|
|
-snip- Thanks, that helped. Now I have the choice between two options one of which is Remote Node ID and this is exactly what I would like to use. But I'd like to have channel exclusively between two wallets I own, no middle-position node in between. Is that possible or the only way for me to have my wallets LN-connected is to establish connection of each of two wallets to one and the same known peer?
Those two are the only option if " Trampoline Routing" is enabled. You can customize the remote node once you've disabled the said feature in the settings. However, I haven't succeeded yet with creating a channel between two Electrum wallets. You can try though - by providing each other's 'Lightning Node ID' as the " Remote Node ID" ( Wallet->Information) followed by the IP address and port. eg: 02d50fdf1806b54aee46a0ed8c6d8512bee87e88e25029f3384a983c43c5d6a16c@111.111.111.111:9735 But like I've said, it never worked at my end.
|
|
|
-snip- but can not move further to open LN channel in Electrum connected to testnet as the wallet's Open Channel button remains in the gray state. The wallet is topped up with 0.01 tBTC which, from my understanding, is enough for channel support. The button remains inactive no matter whether trampoline is disabled or not. I would appreciate any suggestion on how to overcome things that block me from LN channel opening with Electrum.
The two things that you may have missed are: - Lightning should be enabled in the menu "Wallet->Information" if it's not ticked at least once yet (if it's created by an older version).
- The wallet's script (address) type should be Native Segwit ('bc1' address), other types including 2fa aren't compatible with Lightning.
|
|
|
Now is it possible at all to explain to me the following:
If I import my private key that is compressed and starts with an L into my Electrum it gives me immediately an address that is empty and obviously belongs to the key. Orb is green so one can assume it is synced. Done and accepted. But I would like to understand why if I leave it like that where the address is empty and the wallet is imported, after 2 days (it varies) it turns to watching only and the address change to my original address which was never imported to Electrum.
-snip-
Did it happen even in your latest attempt? Anyways, so the symptom's timing varies, interesting... Are you sure that you're the only one who have access to your computer(s)? Because it looks like someone has been creating the watch-only wallet by importing that address while you're away. That's the only logical answer that I can think of. I'm wondering, are you perhaps using " Deepfreeze" ( wiki) or other similar software? Yes guys I imported the key in my Electrum and got back the following address and private key from wallet
Address - 1EHNa6Q4Jz2uvNExL497mE43ikXhwF6kZm Private key - p2pkh:5HpHagT65TZzG1PH3CSu63k8DbpvD8s5ip4nEB3kEsreAnchuDf That's the correct pair, so it's working as intended. IDK what that test is for though since the issue is about 'imported' wallet turning into 'imported - watching only' wallet.
|
|
|
|