Pages:
Author

Topic: Bitcoin private key BASE58 problem - page 3. (Read 766 times)

legendary
Activity: 2268
Merit: 18711
November 24, 2021, 09:21:16 AM
#9
I do not understand then, why whole crypto industry is in fear of an arrival of quantum computers?

Because what you write there is not known even public key to be cracked?
You cannot obtain a public key from knowledge of just the address. Further, quantum computers do not provide a significant advantage over conventional computers when trying to reverse a hash, and so even with quantum computers it will still remain impossible to obtain a public key from an address.

However, whenever you make a transaction in bitcoin, you must include the public key of whichever address the coins you are spending are stored on. This public key is then stored as part of your transaction data on the blockchain, and therefore is public knowledge which anyone can look up. Quantum computers provide an exponential speed up over conventional computers when attempting to reverse the ECDLP, which would potentially allow an attacker in the future to obtain a private key from knowledge of the public key.

If you never reuse an address, then this will not be a concern of yours ever. If you do reuse addresses, then you need to think about stopping doing that in maybe 20 years' time.
legendary
Activity: 1512
Merit: 7340
Farewell, Leo
November 24, 2021, 09:19:28 AM
#8
I do not understand then, why whole crypto industry is in fear of an arrival of quantum computers?
Because they are fearmonger.  Tongue

Joke asides, it's because when Bitcoin started in 2009, Satoshi chose to make the coinbase transaction payable in public key. The uttered “Pay-to-public-key” (P2PK). As a result, thousands of addresses containing this unspent output of 50 BTC have exposed their public key.

Besides that, every address that is reused has also exposed its public key. Currently, the one with the most bitcoins, Binance's, has revealed its public key.
sr. member
Activity: 310
Merit: 727
---------> 1231006505
November 24, 2021, 07:38:28 AM
#7
Almost sleeping but:  Embarrassed

I read somewhere that wallet address is the public key generated from private key:

34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo                               wallet address (richest in the world)
0523e522dfc6656a8fda3d47b4fa53f7585ac758cd7c0caa48         decoded wallet address

1P5ZEDWTKTFGxQjZphgWPQUpe554WKDfHQ
00f22f5563839ba6ba5aa8d3726fcbc675cb3e4c9e215b75ef

38UmuUqPCrFmQo4khkomQwZ4VbY2nZMJ67
054a782fe173a0b6718d39667b420d9c8b07e94262578fac8c


I know that public key for ecc secp256k1 is 64 bytes long, why then dcoded wallet has got only 25 bytes???

It all depends on the address type. For P2PKH (Pay to Public Key Hash) addresses the address is indeed a representation of the public key. But as o_e_l_e_o already explained it is not simply taking the public key and apply base-58 encoding.

However two of the three addresses you linked start with a '3'. These are P2SH (Pay to Script Hash) addresses. The decoded wallet addresses refers in those cases to the hash of a redeem script, so it isn't based on a public key.
jr. member
Activity: 38
Merit: 34
November 24, 2021, 07:10:18 AM
#6
Thanx!

I do not understand then, why whole crypto industry is in fear of an arrival of quantum computers?

Because what you write there is not known even public key to be cracked?

I read some articles and it is written that private key simply leaked from third-party-companies? Am I right?

So not using third parties one should be safe with cryptocurrency?
legendary
Activity: 2268
Merit: 18711
November 24, 2021, 06:29:29 AM
#5
An uncompressed bitcoin public key is 65 bytes long, made up of "04", followed by the 32 byte x coordinate and then the 32 byte y coordinate.
A compressed public key is 33 bytes long, made up of either "02" or "03" depending on if the y coordinate is positive or negative, and then the 32 byte x coordinate.

An address is not simply a public key in Base58Check. To convert a public key to an address, you must first SHA-256 hash it, then RIPEMD-160 hash it, then add a 0x00 network byte to the start, SHA-256 hash it twice, take the first four bytes of this hash as a checksum and append it to the end, and then convert the whole thing to Base58Check. If you want to work backwards from an address, you can only strip the checksum and network byte to arrive at the RIPEMD-160 hash output. You can't go back any further to find the public key.
jr. member
Activity: 38
Merit: 34
November 24, 2021, 06:15:56 AM
#4
Almost sleeping but:  Embarrassed

I read somewhere that wallet address is the public key generated from private key:

34xp4vRoCGJym3xR7yCVPFHoCNxv4Twseo                               wallet address (richest in the world)
0523e522dfc6656a8fda3d47b4fa53f7585ac758cd7c0caa48         decoded wallet address

1P5ZEDWTKTFGxQjZphgWPQUpe554WKDfHQ
00f22f5563839ba6ba5aa8d3726fcbc675cb3e4c9e215b75ef

38UmuUqPCrFmQo4khkomQwZ4VbY2nZMJ67
054a782fe173a0b6718d39667b420d9c8b07e94262578fac8c


I know that public key for ecc secp256k1 is 64 bytes long, why then dcoded wallet has got only 25 bytes???
legendary
Activity: 3668
Merit: 6382
Looking for campaign manager? Contact icopress!
November 24, 2021, 06:08:27 AM
#3
Although the previous link is not bad at all, I'll add this, from Bitcoin wiki, which may be more complete: https://en.bitcoin.it/wiki/Wallet_import_format
Also when you have such questions, these two sites (https://en.bitcoin.it and https://learnmeabitcoin.com/) are good places to look/research Wink
legendary
Activity: 952
Merit: 1385
November 24, 2021, 06:01:01 AM
#2
Read: https://learnmeabitcoin.com/technical/wif

First 2 characters (80/ef) marks real network or testnet.

At the end 8 characters are checksum generated by hashing private key.
Before checksum you may have also marker '01' which tells to produce compressed public key and produces WIF L.. or K.... Without '01' you receive WIF 5...

jr. member
Activity: 38
Merit: 34
November 24, 2021, 05:53:24 AM
#1
I try to learn something but I do not understand following:

It is said that bitcoin private keys from any generator are provided in BASE58 format

on this page I found many examples for private keys:  https://bitkeys.work/

It should be that bitcoin uses secp256k1 ECC  ?  So private key is 32 bytes?

here are some decoded private keys into hex from abovementioned page:

L52sDjGxf8Y5NHy5BjTpQHQUjHDjrqErHyTomskefFXrKPdjf7Di                                                        base58
80e91ed90e9a784499a4e37580de2f5d6b622ba96ff1f735f1992ce787575a44d9010c3e5e49               hex

L2HBA8KcR57PYoGCbZmKUNvmhu7SsrupYj172fQAGkgY75sGUjHQ
8096f833ea1ee11688ad8718e37b3ea81e76911eabed36bbeadb42b6e08b669ee4013cd4ac07

KwXvqELPvZUFgFZ5RhWWLQJQrPvEbk6WKktBk5smCqBeLc17uEvQ
80095f3f838b21709382525317062ada9231188e60304eaaf3d287ed7e7a8c825a01252f78ad

WTF, why private key is not 32 bytes long after decoding base58?  But it has got 6 bytes more?
Also 80 at the beginning seems to be very suspicious....

Any clarification will put me back to a sound sleep during the night...
Pages:
Jump to: