<p>Your post is a series of questions, each of which I'm having trouble understanding specifically, but in general it seems that you are confused about the role of private and public keys in bitcoin. So, as a high level answer:</p>

<p>Bitcoin uses <a href="https://en.wikipedia.org/wiki/Public-key_cryptography" rel="nofollow noreferrer">public key cryptography</a> to verify that users are allowed to spend some bitcoin. A user will create a private/public keypair, and then create a bitcoin address from the public key. Any bitcoin sent to that address is only spendable if the private key signs a transaction spending it (the transaction includes the public key, so that the network can verify the signature). </p>

<p>The way public key cryptography works, it is computationally infeasible to work backwards from the public key, in order to find a private key. So a wallet cannot 'find' the private key for a given public key. </p>

<p>A bitcoin wallet can be thought of as a keychain app, because it stores the user's keypairs. So the wallet will manage your keypairs, create and sign transactions, etc. A private key is not used to sign into the wallet, for that you would use a secure login system (PIN, username, password, 2FA, etc, depending on the type of wallet).</p>

<p>To keep bitcoin safe, it is best to keep your private keys 100% offline, using hardware that never connects to the internet to generate (and potentially store) the keys.</p>

<p>With this setup, there is no reason to specify an 'owner' of an account or wallet, the network only cares about whether or not a signature is valid. </p>

<p>Any good wallet software will generate keys using a proper random number generator, and the keyspace is so large that the chance of ever generating the same private key twice is pretty much zero. The only way to create the same keys in two wallets is to either create the key in one wallet, and then import it to the second wallet, or use an HD wallet architecture and then use the same mnemonic seed phrase to create multiple wallet instances.</p>

CC BY-SA 4.0
2018-10-18T08:43:12.660Z
I edited the original question pretty drastically, If you feel I have undermined your (as usual excellent) answer, please rollback my edits.
RedGrittyBrick
CC BY-SA 4.0
2018-10-17T23:51:31.047Z
2018-10-17T23:51:31.047Z
chytrik
<p>my goal of questions this is why any wallet not able to compute private key created with public key generate? </p>

CC BY-SA 4.0
2018-10-17T14:41:16.907Z
This seems to be about seven different questions, and I'm finding them all pretty hard to understand.  Can you try to edit your post to focus on a more specific question, and to explain more clearly what you are asking?
Nate Eldredge
CC BY-SA 4.0
2018-10-17T14:50:54.873Z
I'm sorry, my goal of questions this is why any wallet not able to compute private key created with public key generate?
hami
CC BY-SA 4.0
2018-10-18T08:38:59.163Z
I edited your "question" to replace the large number of broad questions with the one in your comment - I think this is more answerable. If you dislike my changes, please use the **"[edited](https://bitcoin.stackexchange.com/posts/80181/revisions)"** link above and then **"rollback"** version 1.
RedGrittyBrick
<security><private-key><public-key>
Why can a wallet not compute the private-key from a public-key?
hami
# Why can a wallet not compute the private-key from a public-key?

(Asked by: username_0 on 2018-10-17)

my goal of questions this is why any wallet not able to compute private key created with public key generate?

**Tags:** security, private-key, public-key

> **Comments:**
> **username_1**: This seems to be about seven different questions, and I'm finding them all pretty hard to understand.  Can you try to edit your post to focus on a more specific question, and to explain more clearly what you are asking?  
> **username_0**: I'm sorry, my goal of questions this is why any wallet not able to compute private key created with public key generate?  
> **username_2**: I edited your "question" to replace the large number of broad questions with the one in your comment - I think this is more answerable. If you dislike my changes, please use the **"[edited](https://bitcoin.stackexchange.com/posts/80181/revisions)"** link above and then **"rollback"** version 1.  

---

## 1 answers

### Answer by username_3 on 2018-10-17. Score: 1

Your post is a series of questions, each of which I'm having trouble understanding specifically, but in general it seems that you are confused about the role of private and public keys in bitcoin. So, as a high level answer:

Bitcoin uses [public key cryptography](https://en.wikipedia.org/wiki/Public-key_cryptography) to verify that users are allowed to spend some bitcoin. A user will create a private/public keypair, and then create a bitcoin address from the public key. Any bitcoin sent to that address is only spendable if the private key signs a transaction spending it (the transaction includes the public key, so that the network can verify the signature).

The way public key cryptography works, it is computationally infeasible to work backwards from the public key, in order to find a private key. So a wallet cannot 'find' the private key for a given public key.

A bitcoin wallet can be thought of as a keychain app, because it stores the user's keypairs. So the wallet will manage your keypairs, create and sign transactions, etc. A private key is not used to sign into the wallet, for that you would use a secure login system (PIN, username, password, 2FA, etc, depending on the type of wallet).

To keep bitcoin safe, it is best to keep your private keys 100% offline, using hardware that never connects to the internet to generate (and potentially store) the keys.

With this setup, there is no reason to specify an 'owner' of an account or wallet, the network only cares about whether or not a signature is valid.

Any good wallet software will generate keys using a proper random number generator, and the keyspace is so large that the chance of ever generating the same private key twice is pretty much zero. The only way to create the same keys in two wallets is to either create the key in one wallet, and then import it to the second wallet, or use an HD wallet architecture and then use the same mnemonic seed phrase to create multiple wallet instances.

> **Comments:**
> **username_2**: I edited the original question pretty drastically, If you feel I have undermined your (as usual excellent) answer, please rollback my edits.  

---

