Can't Import Bitcoin Address to Electrum

[entebah]

i just found my wallet that i create in 2019 and I already send 0.001 BTC to that address.
but sadly I can't import that address to Electrum that I just installed.
after a few searches and I found that my private key is a different type from the example from Electrum.
my private key contains

Code:

p2wpkh-p2sh:5H.......

while in the example

Code:

p2wpkh-p2sh:KxZcY4

is there any way to fix it so I can access my wallet?

[1715137072]

1715137072

[1715137072]

1715137072

[LoyceV]

my private key contains

Code:

p2wpkh-p2sh:5H.......

That looks okay. See this post for the differences:

For P2SH-P2WPKH addresses (Addresses starting with "3")
Just add p2wpkh-p2sh: directly in front of your  private key.
For example

Code:

p2wpkh-p2sh:5BitcoinPrivateKey

This should generate the corresponding p2wpkh-p2sh bitcoin address.

For P2WPKH addresses (Bech32, starting with 'bc1')
This time we'll add p2wpkh: in front of the private key.
For example

Code:

p2wpkh:5PrivateKey

This should generate the corresponding Bech32 address

Did you try to create a New Wallet in Electrum? File > New > Next > Import Bitcoin addresses or private keys > "your private key"?

[nc50lc]

is there any way to fix it so I can access my wallet?

Electrum doesn't support importation of Uncompressed WIF Private key with P2WPKH-P2SH script flag because it's non-standard.

Does your address starts with '1', '3' or 'bc1'?
If it's '3' and "p2pkh-p2sh" is specifically written on your backup, then I'm afraid your issue is more than just importation of the private key
but spending its bitcoins since mostly all nodes will reject transactions that you'll create.

Additionally, I'm not aware of any wallet that derives SegWit addresses from uncompressed WIF PrvKey.

If it's '1', then import it without "p2pkh-p2sh:" and it'll let your click the next button.

[LoyceV]

Electrum doesn't support importation of Uncompressed WIF Private key with P2WPKH-P2SH script flag because it's non-standard.

I never caught that part, while I've quoted Xynerise's post many times.

[entebah]

Did you try to create a New Wallet in Electrum? File > New > Next > Import Bitcoin addresses or private keys > "your private key"?

I follow the first step but still can't import

is there any way to fix it so I can access my wallet?

Electrum doesn't support importation of Uncompressed WIF Private key with P2WPKH-P2SH script flag because it's non-standard.

Does your address starts with '1', '3' or 'bc1'?
If it's '3' and "p2pkh-p2sh" is specifically written on your backup, then I'm afraid your issue is more than just importation of the private key
but spending its bitcoins since mostly all nodes will reject transactions that you'll create.

Additionally, I'm not aware of any wallet that derives SegWit addresses from uncompressed WIF PrvKey.

If it's '1', then import it without "p2pkh-p2sh:" and it'll let your click the next button.

my address starts with '3' and maybe because the address is uncompressed. Because when I create my address that time I use VanitySearch 1.11 to create the address.
and I don't know that the address I create is an uncompressed one.

So, there is no way to spend the bitcoin from that address?

[LoyceV]

So, there is no way to spend the bitcoin from that address?

Uncompressed Segwit addresses can be spent, but only if a miner manually includes your transaction. This 2021 transaction with 0.001 BTC (your entire balance) as fee hasn't been confirmed yet. This guy paid 1 BTC ($19k at the time), and it still took more than a year for a miner to manually include his transaction. Doing it manually poses the risk of messing up and losing the entire block reward, so I get that miners aren't too happy to include non-standard transactions.

See:

It was the wish with segwit to prohibit the use of uncompressed keys. But there was a concern that problem's like OP's would arise from incompetent buggy software-- potentially involving really large funds losses.  In an abundance of caution these the rule was made initially standardness-only.  It has turned out to be less of an issue than had been feared (the OP's is the only sizable case I've heard of, at least).

I think the best thing to do now, is doing nothing. Just keep the private key for many years. It may at some point become possible to move your funds (for instance by the time block rewards are so low your transaction fee is worth the risk). Until then: HODL