Electrum 4.0.2 imported wallet from Bitcoin Core, cannot send BTC cannot get key

[Lexx2k]

Small update.

It seems like i seen payment requests arriving to my Bitcoin Core wallet, so it seems like that is why i am unable to sign transactions through Electrum. I am being asked to sign it in Bitcoin core? That payment request was added on Electrum but looks like they show in Bitcoin core. So it might be a good sign. I read somewhere that problem with importing keys from Bitcoin core is that you still need it and full blockchain to sign transactions. Maybe i read something wrong however.

[1714021954]

1714021954

[1714021954]

1714021954

[Abdussamad]

there was a wallet file corruption bug in previous versions. you may have been hit by that. i suggest starting over on a fresh PC. leave your current system untouched for reference purposes. restore from the private keys corresponding to addresses with unspent outputs (coins).

The problem is as mentioned above. I have only select private keys, the Addresses that Electrum made from who knows where,

i should have included a link to the relevant github issue. the wallet file corruption bug results in wallets displaying addresses from a different seed/wallet. it requires you to have generated more than one wallet in a session and for you to have a dodgy drive. for example USB drives are disproportionately effected.



https://github.com/spesmilo/electrum/issues/5082

another possibility is that you simply have a watch only wallet. in that case it should say watch only in the title bar and under wallet > information.

[Lexx2k]

there was a wallet file corruption bug in previous versions. you may have been hit by that. i suggest starting over on a fresh PC. leave your current system untouched for reference purposes. restore from the private keys corresponding to addresses with unspent outputs (coins).

The problem is as mentioned above. I have only select private keys, the Addresses that Electrum made from who knows where,

i should have included a link to the relevant github issue. the wallet file corruption bug results in wallets displaying addresses from a different seed/wallet. it requires you to have generated more than one wallet in a session and for you to have a dodgy drive. for example USB drives are disproportionately effected.



https://github.com/spesmilo/electrum/issues/5082

another possibility is that you simply have a watch only wallet. in that case it should say watch only in the title bar and under wallet > information.

It's 100% not watch only.

Drive is normal hard drive which is slow but very stable model. I might of generated Standard wallet previously. But not one after another very fast. It says imported wallet, not watch only or standard.

Besides my was created on 3.3.8 they added checks to prevent this i beleive. And i do not have seed i tried to retreive it, if it was due to that situation i supposed to have seed in my wallet, or master key. I don't have either.

It might look like my issue, however i do not think i created standard wallet prior to making Imported one, even if i did i never cared to write seed phrase down. How does one know this kind of issue even can occur. I might of wirtten it down, but i doubt i can find it anymore anyway, since i never used that wallet, even if it was ever made actually.

[Lexx2k]

I found deleted Default wallet on one of the shadow discs and recovered it, however none of my passwords match. Could that be the answer. It was created in March, i don't remember deleting or creating any wallets in march. So i have the wallet now. Now i need to figure how to brute force it... Obviously i would remember my passwords.

[Lexx2k]

Basically downloaded Blockchain for Core past the date of transaction, i cannot see it. It is really that problem with corrupt wallets. Except i don't remember creating any standard wallet prior to making imported one. So who the hell knows how to get funds out of this damn electrum now.
Does anyone have any idae or suggestions on what to do? Since it's not hacked and not stolen, it's obviously a bug Electrum to blame for... But what do i do now? I will be really lucky if i find something like passphrase writen somewhere. But how could i get this issue if i didn't make Standard wallet that has passphrase?

[nc50lc]

Basically downloaded Blockchain for Core past the date of transaction, i cannot see it.

Does your Bitcoin core's wallet.dat contains the prv keys of your funded addresses in Electrum?
If you have imported random keys from Electrum, then it shouldn't work unless you're lucky to pick the right ones.
If those funded addresses' keys are the ones affected by the corruption, then there's nothing else you can do with that corrupted wallet file.

The other option is to look for the original wallet.dat from Bitcoin core where those prv keys were extracted from, you can import that back to Bitcoin core instead.
Aside from that, I'm out of ideas.

[HCP]

Aside from that, I'm out of ideas.

Me too... I'm still struggling with the "OP imported 5 keys, ended up with a wallet with 10s/100s of addresses" part.

In all honesty, it sounds like the wallet file is corrupted (KeyError crashes, inability to send funds or see private keys etc), and the OP has unfortunately sent coins to addresses that are stored in the wallet file but the private keys for these addresses are not or the private keys are corrupted

In my opinion, it is going to be very hard to troubleshoot and/or say definitively what the actual problem is without someone with the technical knowledge taking a look at the wallet file... maybe a screen show with the "secret" stuff redacted?

@Lexx2k... Is your wallet file password protected and/or fully encrypted? Or are you able to view the basic structure of the wallet file in a text editor?

[Lexx2k]

Yes basic structure of file looks fine, i can see it and open it without encryption.

I received transactions on core from 2 addresses. 1 showing as Watch only and rest didn't show on core.

[Lexx2k]

Even tho i am already tired as hell of trying all options possible (so much for newbie friendly software with no recover options in case of imported corrupted wallets)...
I will try to explain how i got part of transactions.

Wallet was created by importing keys from core pretty straightforward.
Then after i couldnt transfer funds and couldn't see them on other Electrum wallet, which is strange since i used same private keys. All this transactions even the ones i see on core now, didn't show in new imported wallet.
I took the priv keys from electrum back to Bitcoin core and was able to see 2 addresses transactions out of 13.... now go figure what the hell happened. That means that part of addresses generated from electrum belonged to old private keys but most belonged to new ones that Electrum didn't register in Wallet file... That probably also means that there is different master keys for that Bitcoin core wallet in case of Passphrase change? I don't think i changed passphrase however. Now i am trying to get old priv key if any different from older wallet.dat file. but i think i already did that and nothing happened.

[nc50lc]

That probably also means that there is different master keys for that Bitcoin core wallet in case of Passphrase change?

Bitcoin core will only change the master key if you encrypt a non-encrypted wallet.
It wont if you've just changed the passphrase.

[Lexx2k]

Could this happen if i used older version of Wallet.dat and there is later one available with possible more addresses ? Damn core is scanning blockchain again, which takes ages so i cannot check that option.

[Lexx2k]

Still same result, that addresses that was caught up from Electrum is there, but rest is still missing.
Electrum just bloated out bunch of keys that has no connection with Private keys given and didn't attach any keys to this addresses... Basically lost shitton of money to the air. I guess best idea would to be patient and never stop using Bitcoin Core. As this is not hack or anything, this is loss because of the Electrum numerious bugs and this is not the 1st one that made people lose access to funds. Old wallets unaccessible now because of password corruption, no way to recover data for imported wallet, new 4.0.2 Elecrtum cannot broadcast or send funds actually, even through console. When password enters sometiems the error comes out that it has 4 symbols instead of something until its restarted. To many bugs... Their own wallet is cool and all if you make new one, but it should not make people lose money because there is such function to import, that does not work as intended should disable it and not let people lose their stuff. Not the first corrupted wallet issue.

Basically i tried everything i could try nothing worked. Now i am just trying all backups from Wallet.dat, but i am pretty sure its waste of time. As i never had such keys as Electrum assigned addresses to.

[Lexx2k]

Basically downloaded Blockchain for Core past the date of transaction, i cannot see it.

Does your Bitcoin core's wallet.dat contains the prv keys of your funded addresses in Electrum?
If you have imported random keys from Electrum, then it shouldn't work unless you're lucky to pick the right ones.
If those funded addresses' keys are the ones affected by the corruption, then there's nothing else you can do with that corrupted wallet file.

The other option is to look for the original wallet.dat from Bitcoin core where those prv keys were extracted from, you can import that back to Bitcoin core instead.
Aside from that, I'm out of ideas.

I have no idea how 2 addresses worked and rest didn't actually the strangest thing this was not the first transactions that worked, it's more like in the middle of them. Earliest ones are lost and the latest ones too. Guess i was just if you can say "lucky" to hit the addresses assigned to correct keys with 2 transactions. And one which is real strange, has been imported as watch only from Private key, i don't know how it's possible even. Wallet structure is identical to normal newly created wallet that has no different addresses than imported. It did not have a chance to generate wrong addresses yet.

Now only chance i might have is old Wallet files for Electrum, that by some reason i cannot open because of wrong password, which i am sure is right i never had other one. Have 2 versions at least older and newer one. But i cannot open them, unless i get AES decryption key which is my password...

[Lexx2k]

As i suspected after 3 days of trying. Issue was in old wallet.dat file. It didn't have some hidden new master keys or private keys. The amount of displayed addresses didn't change. But after i used latest wallet.dat all transactions showed and funds was taken out swiftly because now i need new wallet due to, to many manipulations trying to fix it.
Problem is Electrum picked up that new hiden addresses and send funds to them. And i still cannot see any new addresses or keys in my Core. They came in as brand new addresses i never seen before. But non the less it was received.
Also another issue that stands, is electrum Crashing when trying to display private keys from imported wallets as well as from GUI or Console after updating to 4.0.2, alltogether or single. Also forever disabled buttons to sign or broadcast. Unable to send funds through console. Seems it cannot connect to servers well enough to process transaction. I would recommend for people using Electrum to switch to core. To many bugs in Electrum. So much again for Newbie friendly easy wallet Well i am happy now finally i can sleep well.

[HCP]

As i suspected after 3 days of trying. Issue was in old wallet.dat file. It didn't have some hidden new master keys or private keys. The amount of displayed addresses didn't change. But after i used latest wallet.dat all transactions showed and funds was taken out swiftly because now i need new wallet due to, to many manipulations trying to fix it.

Which wallet.dat are you talking about? Wallet files for Electrum? or actual wallet.dat files for Core?

I'm still very confused as to what the actual issue was here... because now you're talking about "hidden" master/private keys?

Can you just answer one thing for me... when you imported your "5 keys"... how many addresses were showing in the Electrum "Addresses" tab?

[Lexx2k]

Electrum was fine, except that it couldn't send anything out and bugged export keys commands in console and gui. Electrum seems like was unable to find/link this keys to private keys until i synced the actual latest core wallet to blockchain. Wish i knew what the issue was exactly. Just magic no logic.

At a time i made it, i imported all keys found in Core which was 3. Later i dug out more but this is not releavant to the problem. Multiple addresses in amount of more than 100, was derived from this keys and some unknown keys to me looks like. As Newly created Electrum with same addresses do not show any new transactions. So, it looks like, there is keys that Bitcoin Core did not show, even tho they are there. Since Core has no command to Display all priv keys.

Wallet.dat is for the core, i was unable to see transactions made in Electrum on old wallet.dat in Bitcoin core. So when i made backup i thought all Wallet.dat files supposed to be same, with 1 master key. Obviously i was wrong. It missed something, that did not allow me to see transfers. When i put latest version of it i was able to see them.

If you don't understand you just cannot, took me 3 days of trying everything anyway to fix this.
If you didn't read about it before, if you import keys to Electrum both Core and electrum becomes 1 wallet basically. Anyway i will delete all this old stuff and make fresh ones. To avoid such a clutter of old stuff.

[HCP]

Electrum seems like was unable to find/link this keys to private keys until i synced the actual latest core wallet to blockchain. Wish i knew what the issue was exactly. Just magic no logic.

Electrum, by default, connects to public servers which will not be affected by your Bitcoin Core node. So, whether or not your Bitcoin Core was synced should not make any difference... unless you are connecting your Electrum to your own private Electrum Server (like ElectrumX, electrs or Electrum Personal Server) which is connected to your Bitcoin Core node.

Are you running a private Electrum Server?

Basically, if the private keys in Electrum are the same as the ones in Bitcoin Core and have been imported as the appropriate script type so that the addresses holding coins in Bitcoin Core are the ones being displayed in Electrum... Then everything should work.

Since Core has no command to Display all priv keys.

It does... The command is dumpwallet

It will allow you to dump ALL the private keys contained in the wallet.dat (including ones in the keypool which are not displayed in the "receiving addresses" list)

If you didn't read about it before, if you import keys to Electrum both Core and electrum becomes 1 wallet basically.

That's not how it works... The two wallets, while containing the same keys/addresses, still operate independently of each other.

For instance, it's possible to export a single key out of Bitcoin Core and put that into Electrum, but still have other keys in Bitcoin Core that aren't in Electrum... And vice versa, you could have keys in Electrum that are not in Bitcoin Core.

However, for any private key/address pairs that are in both wallets you should see all the same transactions for those addresses (assuming both wallets are properly synced and up to date).

[Lexx2k]

Yep the issue is, why i couldn't see them on same wallet.dat that was older and synced, but could see them in later one which is basically same wallet. Remains mystery to me. Keys should be same, but this is not related to electrum.
No i don't use private node or local one. My wife is able to use sign and broadcast fuctions on Electrum, i cannot. Something was definitely screwed up in my electrum wallet. Probably it was bugged from long time ago when i created it. But in end of 2019 i think it was already 3.3.8 so shouldn't have happened. Well hope it's a single case like this. As i was not able to find anyone with same issue yet. However for now i will stick with Core. Better wait 2 hour to sync than lose everything because of bug.