Topic: Bitcoin Address Collisions. - page 3. (Read 3941 times)
What language are we talking in
Let's assume there are 2^160 possible, and equally probable to be generated, bitcoin addresses. Let's than assume there are 10 billions people on the planet, and each of them uses 100 new addresses a day. They continue to do so for 1000 years. After that period of time approx 3.65*10^17 addresses will be generated. Next address to be generated has probability of 2.5*10^-31 to collide with one of the existing addresses. That's several orders of magnitude less than 1 divided by Avogadro constant.
legendary
Activity: 1862
Merit: 1011
Reverse engineer from time to time
There are slightly less than 2160 possible bitcoin addresses, not 2256
Yeah, but there are still ~2^256(not exactly 2^256 private keys due to secpk256k1) so doesn't matter much, because you still need to try numbers from this large pool for the right private key which hashes to some RIPEMD160 hash. 
There are slightly less than 2160 possible bitcoin addresses, not 2256
The odds of a collision taking place, by my calculations, assuming 20 Million BTC address, are as follows:
2^256 1
______ = ____________________
~20 Million (Estimated BTC Address In Existence) 5.78960446186581E69
Which is equal to:
1
__________________ Or .00000000005064660113837803 %
1974466158682.1443
That is of 1 single collision taking place, so it seems rather unlikely.
Has anyone ever been able to confirm that an address collision took place? I ask because we seem to worry a lot about it, even though the odds seem stacked against such a happening.
2^256 1
______ = ____________________
~20 Million (Estimated BTC Address In Existence) 5.78960446186581E69
Which is equal to:
1
__________________ Or .00000000005064660113837803 %
1974466158682.1443
That is of 1 single collision taking place, so it seems rather unlikely.
Has anyone ever been able to confirm that an address collision took place? I ask because we seem to worry a lot about it, even though the odds seem stacked against such a happening.
Jump to: