Problem importing addresses | Bitcointalksearch.org

Charles-Tim

legendary

Activity: 1512

Merit: 4795

Leading Crypto Sports Betting & Casino Platform

Quote from: NotATether on March 17, 2021, 10:26:57 AM

Quote from: Lion_King_ on March 17, 2021, 03:12:42 AM

I used bitaddress.org in most cases, but for some wallets it is not suitable, due to the different formats (example of Trustee Wallet).

Is it because that you are trying to import generated segwit (bc1 or 3) addresses in them?

First of all, we should not hide the fact that Trust wallet has gone completely close source, but that is not the main reason of this post. It is impossible to import Bitcoin private key into Trust wallet, it can only be done using the seed phrase. Although, Trust wallet support importation of some coins private key (I do not know if master private key or extended private key is sopoorted)

I was surprised to notice this on Trust wallet as it currently supports private key importation of 36 altcoins while not support that of bitcoin.

NotATether

legendary

Activity: 1568

Merit: 6660

bitcoincleanup.com / bitmixlist.org

Quote from: Lion_King_ on March 17, 2021, 03:12:42 AM

Then, as I understand it, it makes no sense to use this address generator https://gist.github.com/colindean/5239812, all addresses start with the letter M.

It's only generating addresses in base58, public and private keys are for some bizarre reason encoded in PEM format instead of base58. I'm not sure what the author was trying to accomplish here since no bitcoin software reads PEM files.

Quote from: Lion_King_ on March 17, 2021, 03:12:42 AM

Or something could be done to change the format to fit for import into this wallet.

I believe that when you decode a PEM elliptic curve private key it has the factor multiplied by the generator point inside, however it takes quite a bit of effort to convert the factor to a Base58 WIF.

Quote from: Lion_King_ on March 17, 2021, 03:12:42 AM

I used bitaddress.org in most cases, but for some wallets it is not suitable, due to the different formats (example of Trustee Wallet).

Is it because that you are trying to import generated segwit (bc1 or 3) addresses in them?

Charles-Tim

legendary

Activity: 1512

Merit: 4795

Leading Crypto Sports Betting & Casino Platform

That private key does not ended in the red bracket you used for demarcation. Also know that cryptography is wider, the example above like the one below is an 'Elliptical Curve Keys created using OpenSSL' not the way bitcoin private key is created. This is used in generating a self-signed certificate
https://www.scottbrady91.com/OpenSSL/Creating-Elliptical-Curve-Keys-using-OpenSSL

-----BEGIN EC PRIVATE KEY-----
MHcCAQEEIKEubpBiHkZQYlORbCy8gGTz8tzrWsjBJA6GfFCrQ98coAoGCCqGSM49
AwEHoUQDQgAEOr6rMmRRNKuZuwws/hWwFTM6ECEEaJGGARCJUO4UfoURl8b4JThG
t8VDFKeR2i+ZxE+xh/wTBaJ/zvtSqZiNnQ==
-----END EC PRIVATE KEY-----

NotATether has commented about how bitcoin private keys looks like, the WIF-compressed starts with either K or L while the WIF starts with 5. To do that, bitaddress.org is enough. There is another type that is used to generate the WIF-compressed or WIF private key which are in hexadecimal, while the last one starts with 6P if you encrypt your private with BIP38 passphrase. But the wallet import formats start with 5, K or L. For low transaction fee, compressed private key should be used.

Lion_King_

newbie

Activity: 8

Merit: 1

Then, as I understand it, it makes no sense to use this address generator https://gist.github.com/colindean/5239812, all addresses start with the letter M.
Or something could be done to change the format to fit for import into this wallet.
I used bitaddress.org in most cases, but for some wallets it is not suitable, due to the different formats (example of Trustee Wallet).

NotATether

legendary

Activity: 1568

Merit: 6660

bitcoincleanup.com / bitmixlist.org

Compressed private keys start with a 5H, 5J, or 5K. Uncompressed keys start with K or L. Your private key doesn't start with any of these ("M") because it is not in Base58 WIF format, you have an ASCII-armored PEM private key, which is not a valid bitcoin private key. You didn't even paste the entire private key - only the first line - but it doesn't matter because that isn't a valid bitcoin private key either.

(By the way, please do not use either of those private keys now that you have posted them online. Someone will probably steal money from them.)

edit: spelling

TheBeardedBaby

legendary

Activity: 2240

Merit: 3150

₿uy / $ell ..oeleo ;(

Quote from: Lion_King_ on March 17, 2021, 02:12:29 AM

Hello everyone, I had some difficulties with importing addresses, I did everything through blockchain.com wallet, I did the generation from https://gist.github.com/colindean/5239812.

But when I made addresses from bitaddress.org everything was fine, what could be the problem??

And this with many addresses.

Let me quote it first because so the images could be visible because the image hosting site you are using is awful, full of adds and actually not trustworthy.
Next time you upload images, better use more reputable hosting sites like imgur or imgbb.

Lion_King_

newbie

Activity: 8

Merit: 1

Hello everyone, I had some difficulties with importing addresses, I did everything through blockchain.com wallet, I did the generation from https://gist.github.com/colindean/5239812.
https://i114.fastpic.ru/big/2021/0317/37/01fe1adc0f755ad96cc407dfddff6037.png
https://i114.fastpic.ru/big/2021/0317/bc/1fafc467fa732a6b7cf10306c0abeebc.png
But when I made addresses from bitaddress.org everything was fine, what could be the problem??
https://i114.fastpic.ru/big/2021/0317/1e/829e0e3e5e4c37df892dbe2486257e1e.png
https://i114.fastpic.ru/big/2021/0317/ce/fe8104ab369affd5c8f811057551bdce.png
And this with many addresses.

Topic: Problem importing addresses (Read 151 times)