How private key works?

[RentGPU]

I want to ask a simple question , i will form it as example to make it clear
If we have 2 btc addresses with the exact same letters but in diffrenet order like 1.abcd. 2.bcda as i know private key is mathimatically connect to the public key so does one private key open both addresses or the order of letters is changing the private key??

[1714875205]

1714875205

[1714875205]

1714875205

[ranochigo]

If we have 2 btc addresses with the exact same letters but in diffrenet order like 1.abcd. 2.bcda as i know private key is mathimatically connect to the public key so does one private key open both addresses or the order of letters is changing the private key??

The answer is usually no. But I'll explain what I mean when I say its depends.

One private key can be take two different forms, the compressed and the uncompressed. Both of the forms corresponds to two different addresses. If the two different addresses happens to fit the kind of sequence you said, it will be possible for one private key to spend inputs in the two different addresses though you will have to convert the private key to compressed/uncompressed. It is highly unlikely for this to happen.

Else, 1Address and 1address don't have the same private key, even if the subsequent letters are the same. Changing the address by a letter would make the address invalid.

Eg. 192fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is my address.
129fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is invalid.

[Thirdspace]

If we have 2 btc addresses with the exact same letters but in diffrenet order like 1.abcd. 2.bcda as i know private key is mathimatically connect to the public key so does one private key open both addresses or the order of letters is changing the private key??

The answer is usually no. But I'll explain what I mean when I say its depends.

One private key can be take two different forms, the compressed and the uncompressed. Both of the forms corresponds to two different addresses. If the two different addresses happens to fit the kind of sequence you said, it will be possible for one private key to spend inputs in the two different addresses though you will have to convert the private key to compressed/uncompressed. It is highly unlikely for this to happen.

Else, 1Address and 1address don't have the same private key, even if the subsequent letters are the same. Changing the address by a letter would make the address invalid.

Eg. 192fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is my address.
129fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is invalid.

I'm sorry not trying to takeover RentGPU thread but I have question related to the bolded words
Lets say 1Aaaa privkey is 5Kxxx and 1Bbbb privkey is L2yyy and 1Bbbb is compressed address of 1Aaaa
are you saying using L2yyy I can spend unspent outputs from 1Aaaa?
reason I asked is, long time ago I imported addresses to blockchain.info using the uncompressed form (5K...)
so I get the uncompressed addresses imported and displayed on my account
but today I clicked show privkey on menu, blockchain.info is showing me compressed privkey (L2...)
why is it showing me the compressed privkey while addresses that I use are uncompressed
I haven't tried making transaction but planning soon to figure this out

[RentGPU]

If we have 2 btc addresses with the exact same letters but in diffrenet order like 1.abcd. 2.bcda as i know private key is mathimatically connect to the public key so does one private key open both addresses or the order of letters is changing the private key??

The answer is usually no. But I'll explain what I mean when I say its depends.

One private key can be take two different forms, the compressed and the uncompressed. Both of the forms corresponds to two different addresses. If the two different addresses happens to fit the kind of sequence you said, it will be possible for one private key to spend inputs in the two different addresses though you will have to convert the private key to compressed/uncompressed. It is highly unlikely for this to happen.

Else, 1Address and 1address don't have the same private key, even if the subsequent letters are the same. Changing the address by a letter would make the address invalid.

Eg. 192fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is my address.
129fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is invalid.

Thanks for your answer, what i am asking is if it does happen that two addresses have the same combination not order so they will share also private key , as i see you are saying that is right but it will not happen to find two addesses with the exact same combination

[ranochigo]

I'm sorry not trying to takeover RentGPU thread but I have question related to the bolded words
Lets say 1Aaaa privkey is 5Kxxx and 1Bbbb privkey is L2yyy and 1Bbbb is compressed address of 1Aaaa
are you saying using L2yyy I can spend unspent outputs from 1Aaaa?

Somewhat correct.

Both of the WIF keys comes from the same private key, albeit with a different prefix to signal your wallet on how to treat the address. You have to convert the compressed key back to uncompressed key first so that you can import it into your wallet to get 1Aaaa. Bitaddress.org does this for you in their "wallet details" tab. I would highly recommend you to download the script offline for more security.

[cr1776]

If we have 2 btc addresses with the exact same letters but in diffrenet order like 1.abcd. 2.bcda as i know private key is mathimatically connect to the public key so does one private key open both addresses or the order of letters is changing the private key??

The answer is usually no. But I'll explain what I mean when I say its depends.

One private key can be take two different forms, the compressed and the uncompressed. Both of the forms corresponds to two different addresses. If the two different addresses happens to fit the kind of sequence you said, it will be possible for one private key to spend inputs in the two different addresses though you will have to convert the private key to compressed/uncompressed. It is highly unlikely for this to happen.

Else, 1Address and 1address don't have the same private key, even if the subsequent letters are the same. Changing the address by a letter would make the address invalid.

Eg. 192fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is my address.
129fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is invalid.

Thanks for your answer, what i am asking is if it does happen that two addresses have the same combination not order so they will share also private key , as i see you are saying that is right but it will not happen to find two addesses with the exact same combination

Order does indeed matter as they are, at root, just representations of numbers.  So 12345 and 54321 while having the same component integers are different numbers and so correspond to different points on a curve. (Simplified explanation, of course.). And 12345 and 54321 would be points on the curve, but not random enough to be safe.

Also since they are just numbers, you could create two private keys that swap the last two "digits" (and then re-encode the new one - there are checksums in there to decrease the chance that a typo would result in a valid address) to verify this for yourself.

[Katashi]

If we have 2 btc addresses with the exact same letters but in diffrenet order like 1.abcd. 2.bcda as i know private key is mathimatically connect to the public key so does one private key open both addresses or the order of letters is changing the private key??

The answer is usually no. But I'll explain what I mean when I say its depends.

One private key can be take two different forms, the compressed and the uncompressed. Both of the forms corresponds to two different addresses. If the two different addresses happens to fit the kind of sequence you said, it will be possible for one private key to spend inputs in the two different addresses though you will have to convert the private key to compressed/uncompressed. It is highly unlikely for this to happen.

Else, 1Address and 1address don't have the same private key, even if the subsequent letters are the same. Changing the address by a letter would make the address invalid.

Eg. 192fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is my address.
129fqgb5aCKrjNkudGqSWR6Nuu4J8tEMB7 is invalid.

nice this is a very precise explanation i was also wondering and finding answer for the same question glad someone had posted it. Thank you by the way now i know hoe this private key works. Godbless to both of you.

[coder0x15]

Private key (32b number, random) --1--> Public key (64byte number, elliptic curve point) --2--> Hash (20byte number) --3--> Address (Base58 string).

1. Elliptic curve point multiplication
2. SHA256, ripemd160
3. Hex converts to Base58