Pages:
Author

Topic: Is there a way to transfer BTC from an offline wallet (Armory) to a new... (Read 262 times)

newbie
Activity: 14
Merit: 4
I worked guys!

It took me some time copy/paste all the "adresses" carefully - but it worked!  Grin
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  Grin If yes? Yes! Keys Smiley


Again, thanks - your help was humbeling. <3
legendary
Activity: 2338
Merit: 5297
Self-proclaimed Genius
I worked guys!

It took me some time copy/paste all the "adresses" carefully - but it worked!  Grin
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.
newbie
Activity: 14
Merit: 4
I worked guys!

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



THANK YOU ALL!


Love from Sweden.
legendary
Activity: 2338
Merit: 5297
Self-proclaimed Genius
-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.
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
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.
legendary
Activity: 3206
Merit: 2904
Block halving is coming.
~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.
newbie
Activity: 14
Merit: 4

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.
legendary
Activity: 2380
Merit: 5178
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.  






legendary
Activity: 3206
Merit: 2904
Block halving is coming.

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.
newbie
Activity: 14
Merit: 4
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. =)
legendary
Activity: 3206
Merit: 2904
Block halving is coming.
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.
newbie
Activity: 14
Merit: 4
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?
legendary
Activity: 2506
Merit: 2832
Top Crypto Casino
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"?
newbie
Activity: 14
Merit: 4
I don't understand which one I should use "p2wpkh:5PrivateKey".
Each private key can create a few different address types. By adding p2wpkh: in front of it, you tell Electrum which one to use.

A took a random key and added p2wpkh: infront of it to se if "Next-button" was highlighted, It wasnt.
legendary
Activity: 2380
Merit: 5178
If the address starts with "bc1q", you need to apply this when importing:
The bc1q address OP is talking about can't be an Armory address. Armory doesn't generate bech32 addresses.

Armory generates legacy addresses (by default) and nested segwit addresses.
Armory also generates P2SH-P2PK addresses. As far as I know, Armory use a specific script type for generating these addresses and they can't be imported to electrum.
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
I don't understand which one I should use "p2wpkh:5PrivateKey".
Each private key can create a few different address types. By adding p2wpkh: in front of it, you tell Electrum which one to use.
newbie
Activity: 14
Merit: 4
If you don't know what was the address you used when receiving bitcoin, copy and paste all private keys into electrum. One of them should be associated with your address.
If the address starts with "bc1q", you need to apply this when importing:
How To Import Segwit WIF ~ to Electrum
~
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

There are approx 70 keys, I don't understand which one I should use "p2wpkh:5PrivateKey".

Again, sorry for being such an ....


Kind regards,
Martin
legendary
Activity: 3290
Merit: 16489
Thick-Skinned Gang Leader and Golden Feather 2021
If you don't know what was the address you used when receiving bitcoin, copy and paste all private keys into electrum. One of them should be associated with your address.
If the address starts with "bc1q", you need to apply this when importing:
How To Import Segwit WIF ~ to Electrum
~
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
legendary
Activity: 2380
Merit: 5178
All I have for sure is the recipient adress, starts with bc1q (42 characters long)- all keys starts with 5. What am I missing?
What do you mean by recipient address? Do you mean the address you are going to send bitcoin to? If so, it can't help you.

When you deposited to Armory, you used an address for receiving bitcoin. That's the address you need to find in Armory. As Armory generates legacy addresses by default, it probably starts with 1.
If you don't know what was the address you used when receiving bitcoin, copy and paste all private keys into electrum. One of them should be associated with your address.
Note that private keys start with 5, K or L.
newbie
Activity: 14
Merit: 4
I have only made one transfer to Armory (never again)
So, you only need to export the private key of the address you sent bitcoin to.

Check "Address String" when exporting private keys. (It's shown in the image below.)

https://i.imgur.com/pFBEFC8.jpg

Then try to find the address you sent bitcoin to. Copy its private key and paste it into electrum.
(The private key is below the address and in front of "PrivBase58".)

All I have for sure is the recipient adress, starts with bc1q (42 characters long)- all keys starts with 5. What am I missing?
Pages:
Jump to: