Is there a way to transfer BTC from an offline wallet (Armory) to a new...

[deliciousdelux]

OP's problem is not whether his addresses are segwit or legacy. His problem is that he is importing invalid private keys or he's exported them from Armory in a format that Electrum does not accept. This is why the Next button is not clickable.
@OP, when you exported the private keys, did you check the "Private Key (Plain Base58)" box? Do the private keys start with "L" or "K"?

I was very clear with that I used  Saffello which used Segwit before, but now Taproot (have no clue of the difference), is this the source of my problem - hence I'm f*cked?

[BitMaxz]

I was very clear with that I used  Saffello which used Segwit before, but now Taproot (have no clue of the difference), is this the source of my problem - hence I'm f*cked?

The only problem is that the private key that starts with 5 doesn't support yet on Electrum but all private keys you have are uncompressed WIF private key you can convert them into the compressed private key that starts with L or K.

There is a tool that you can convert them you can use https://www.bitaddress.org/ under wallet details and paste the private key that starts with 5 and you will see all details after you click the details. You can also use this tool https://iancoleman.io/bitcoin-key-compression/ to convert them into compressed WIF keys.

Or you can try to disable or uncheck plain base58 when exporting private keys from the armory. Let see if it will show K or L private keys instead of 5.

[deliciousdelux]

I was very clear with that I used  Saffello which used Segwit before, but now Taproot (have no clue of the difference), is this the source of my problem - hence I'm f*cked?

The only problem is that the private key that starts with 5 doesn't support yet on Electrum but all private keys you have are uncompressed WIF private key you can convert them into the compressed private key that starts with L or K.

There is a tool that you can convert them you can use https://www.bitaddress.org/ under wallet details and paste the private key that starts with 5 and you will see all details after you click the details. You can also use this tool https://iancoleman.io/bitcoin-key-compression/ to convert them into compressed WIF keys.

Or you can try to disable or uncheck plain base58 when exporting private keys from the armory. Let see if it will show K or L private keys instead of 5.

Thanks, however - I'm by no means "locked" to Eletrum - any wallet where I can transfer my Armory-BTCs will do. =)

[BitMaxz]

Thanks, however - I'm by no means "locked" to Eletrum - any wallet where I can transfer my Armory-BTCs will do. =)

What do you mean locked to Electrum?

There are many wallets but it seems that you've experienced some issues with Armory wallet according to your old post on the Armory section.

Why not, focus on Electrum first because it is one of the easy-to-use wallets.

The important here you already have the private keys that you can use to import your old wallet where your $30 in BTC is located or saved.

As what I mention above the private keys that starts with 5 you can convert them and I'm sure it will work after you convert them into k or L.

[hosseinimr93]

OP's problem is not whether his addresses are segwit or legacy.

One of problems is that Armory doesn't generate native segwit addresses at all. But OP is talking about an address starting with bc1q.
The other problem (as rightly mentioned by you) is that he is probably entering an invalid private key.

The only problem is that the private key that starts with 5 doesn't support yet on Electrum

You can import private keys that start with 5 into electrum and there is no need to make any conversion.
Look at images below. I imported private keys exported from Armory wallet into electrum without any problem and generated same addresses.  

[deliciousdelux]

Thanks, however - I'm by no means "locked" to Eletrum - any wallet where I can transfer my Armory-BTCs will do. =)

What do you mean locked to Electrum?

There are many wallets but it seems that you've experienced some issues with Armory wallet according to your old post on the Armory section.

Why not, focus on Electrum first because it is one of the easy-to-use wallets.

The important here you already have the private keys that you can use to import your old wallet where your $30 in BTC is located or saved.

As what I mention above the private keys that starts with 5 you can convert them and I'm sure it will work after you convert them into k or L.

Ok, thank you. I'll look into it in the morning (it's 1 am here). G'night and thanks for everything.

[BitMaxz]

~snip~

The legacy one will work but the segwit one(p2sh-p2wpkh) will not work. If you put import the private key on Electrum with the Segwit one the result of the address will convert to the legacy wallet.

I already tried that on Electrum even adding script type it won't let you click the next button. So converting them into compressed private key will solve his issue.

[LoyceV]

The legacy one will work but the segwit one(p2sh-p2wpkh) will not work. If you put import the private key on Electrum with the Segwit one the result of the address will convert to the legacy wallet.

I already tried that on Electrum even adding script type it won't let you click the next button.

Isn't that because you can't spend funds from a Segwit address created from an uncompressed pubkey in the normal way? See this post.

[nc50lc]

-snip- If you put import the private key on Electrum with the Segwit one the result of the address will convert to the legacy wallet.

I already tried that on Electrum even adding script type it won't let you click the next button. So converting them into compressed private key will solve his issue.

That's because of Electrum's current behavior when importing private keys:

• If there's no prefix, it will import the private key into P2PKH whether it's WIF compressed or not.
• If there's a prefix, it will follow that prefix's script type.
• For SegWit (P2WPKH / P2WPKH-P2SH), it wont take uncompressed WIF private key because using uncompressed WIF prvKey in SegWit is non-standard.

Converting the WIF keys to compressed surprisingly works (not for P2SH-P2PK, only for P2SH-P2WPKH),
Armory will display the uncompressed WIF key when exporting a P2WPKH-P2SH address' keys (which is wrong IMO), but able to derive the correct nested SegWit address based from the compressed public key.
Maybe that's the reason why that option is grayed-out when selecting an address type in the GUI of v0.96.5.

[deliciousdelux]

I worked guys!

It took me some time copy/paste all the "adresses" carefully - but it worked!  



THANK YOU ALL!


Love from Sweden.

[nc50lc]

I worked guys!

It took me some time copy/paste all the "adresses" carefully - but it worked!  

Wait! You said "addresses".
Have you successfully created an [imported] Electrum wallet, not an [imported, watching-only] wallet?
Check the wallet's name in Electrum's title bar.

Or do you mean you've copy/paste all the "private keys"?
If yes, then it's all good.

[deliciousdelux]

I worked guys!

It took me some time copy/paste all the "adresses" carefully - but it worked!  

Wait! You said "addresses".
Have you successfully created an [imported] Electrum wallet, not an [imported, watching-only] wallet?
Check the wallet's name in Electrum's title bar.

Or do you mean you've copy/paste all the "private keys"?
If yes, then it's all good.

I don't know the correct terminology and english isn't my native language, however - we learn it school as a side course for six years and then we have all american/english movies/series and ofcourse forums of a kinds.

However   If yes? Yes! Keys 


Again, thanks - your help was humbeling. <3