Pages:
Author

Topic: Understanding Public and Private Keys - page 3. (Read 2219 times)

cp1
hero member
Activity: 616
Merit: 500
Stop using branwallets
May 31, 2014, 12:35:43 PM
#9
Ok, but that doesn't really satisfy. Because as more people used bitcoin, and more an more addresses are generated, and the longer its been around, there would be more and more of a chance of duplicate addresses.

Question: after an addresses is loaded with funds and added to the blockchain, then, does that information get sent to these automatic addresses generators in all the web, desk, and mobile wallets, and the bitaddress.org generator too? I don't think so. So how do they know they are not creating an address which was already created?

The chances are extremely slim, but technically speaking, it IS POSSIBLE.

Send me your private key and I'll promise not to use that address. Pinky swear.
legendary
Activity: 4438
Merit: 3387
May 31, 2014, 12:33:00 PM
#8
In short, the chances of two people generating the same private keys are so low that it is not worth worrying about. Do you worry about being hit by a meteor?

Ok, but that doesn't really satisfy. Because as more people used bitcoin, and more an more addresses are generated, and the longer its been around, there would be more and more of a chance of duplicate addresses.

Question: after an addresses is loaded with funds and added to the blockchain, then, does that information get sent to these automatic addresses generators in all the web, desk, and mobile wallets, and the bitaddress.org generator too? I don't think so. So how do they know they are not creating an address which was already created?

The numbers are so huge that none of the things you mention, even multiplied by a billion, make the slightest difference.

The number of possible addresses is 2160. If 10 billion people have generated 1 billion addresses each, then the chances of a new address colliding with any of those is 1 in 2141. That's a 1 in 2,787,593,149,816,327,892,691,964,784,081,045,188,247,552 chance.

Let's pretend that Bitcoin is as big as Visa, which can process 24,000 transactions per second. In a million years, bitcoin will have processed up to 800,000,000,000,000,000 transactions. If a new key were generated for each of those, then there is still only a 1 in 2,000,000,000,000,000,000,000,000,000,000 chance that it will be a duplicate.
newbie
Activity: 56
Merit: 0
May 31, 2014, 12:22:21 PM
#7
In short, the chances of two people generating the same private keys are so low that it is not worth worrying about. Do you worry about being hit by a meteor?

Ok, but that doesn't really satisfy. Because as more people used bitcoin, and more an more addresses are generated, and the longer its been around, there would be more and more of a chance of duplicate addresses.

Question: after an addresses is loaded with funds and added to the blockchain, then, does that information get sent to these automatic addresses generators in all the web, desk, and mobile wallets, and the bitaddress.org generator too? I don't think so. So how do they know they are not creating an address which was already created?

The chances are extremely slim, but technically speaking, it IS POSSIBLE.
cp1
hero member
Activity: 616
Merit: 500
Stop using branwallets
May 31, 2014, 12:18:48 PM
#6
And none of them are telling the other what keys have been used already.

If you had to ask other people not to use your private key then your coins would be stolen in seconds.
copper member
Activity: 1498
Merit: 1528
No I dont escrow anymore.
May 31, 2014, 12:11:16 PM
#5
-snip-
So why is it not possible that duplicate addresses can be created? Why is it not possible that a private key can be discovered by luck or brute force?

Because for one

-snip-the chances of two people generating the same private keys are so low that it is not worth worrying about. -snip-

but most people dont grasp how slim the chance for this actually is.

Lets play a game with private/public keys, shall we?

I have a public key (e.g. the one in my signature) the chance for you finding the private key for it is the same chance to find a bucky ball within planet earth (this includes the core and the air). If you want to see the calculation go here: https://bitcointalksearch.org/topic/m.6473942

If this is to abstract you can think off it as finding a single water molecule in every water source (this would ofc include animals and humans) on earth. Yet this is way off, you have a very good chance to find this water molecule compared to your chance to find the private key to my public one.

These chances are so minimal that even if everyone would make a new address for every transaction for the next 1000 years, the chance of collision (2 same private keys) is still minimal. I probably will do a calculation on how slim exactly sometime in the future.
legendary
Activity: 4438
Merit: 3387
May 31, 2014, 11:54:06 AM
#4
In short, the chances of two people generating the same private keys are so low that it is not worth worrying about. Do you worry about being hit by a meteor?
newbie
Activity: 56
Merit: 0
May 31, 2014, 08:48:50 AM
#3
Hey, If you want consistent explanation reads It on wiki.

Private key: https://en.bitcoin.it/wiki/Private_key

Public key: https://en.bitcoin.it/wiki/Address

I read both of those wikis completely but I did not find the answers to my questions.
legendary
Activity: 938
Merit: 1000
May 31, 2014, 08:19:07 AM
#2
Hey, If you want consistent explanation reads It on wiki.

Private key: https://en.bitcoin.it/wiki/Private_key

Public key: https://en.bitcoin.it/wiki/Address
newbie
Activity: 56
Merit: 0
May 31, 2014, 08:12:24 AM
#1
Can anybody explain in simple form why keys are safe?

There are several exchanges with wallets, desktop wallets, web wallets, mobile wallets, etc, and all of them are generating new addresses and private keys all the time for every user. And none of them are telling the other what keys have been used already. So why is it not possible that duplicate addresses can be created? Why is it not possible that a private key can be discovered by luck or brute force?
Pages:
Jump to: