<p>If two or more people choose the same, non-random seed while looking for vanity address with the same pattern, they will end up with the same private key. This would happen due to them either iterating to the same private key from the seed, or by ending up with the same private key by using the given language's version of rand() function with identical seeds.</p>

<p>However, if one was to chose a random seed, here are the probabilities of accidentally ending up with the same keypair / address:</p>

<p>To obtain the same <a href="https://en.bitcoin.it/wiki/Technical_background_of_Bitcoin_addresses" rel="nofollow">address</a>, the result of RIPEMD-160 hashing would need to be the same. Probability of that happening is 1 in 2^160.</p>

<p>To obtain the same private key, it is a probability of 1 in <a href="https://en.bitcoin.it/wiki/Secp256k1" rel="nofollow">n</a>, where n is the order of <a href="https://en.bitcoin.it/wiki/Secp256k1" rel="nofollow">secp256k1</a> and equal to FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFE BAAEDCE6 AF48A03B BFD25E8C D0364141, or about 2^256.</p>

CC BY-SA 3.0
2013-02-15T08:06:45.777Z
you didn't get the question, I think. vanitygen tool starts random process of finding a key that matches the given pattern. assuming this search always starts from a known specific chunk (with no random number seed), then it is quiet possible that two different runs to end up with the same pair. right?
vi.su.
CC BY-SA 3.0
2013-02-15T09:11:23.793Z
@vi.su. edited accordingly
ThePiachu
CC BY-SA 3.0
2013-02-15T10:14:12.910Z
not true. tried to generate smaller pattern with the same random number seed, and both the runs generated different results. may be there is something like,  time seed (current millisecond), but when I checked the code couldn't found anything related.
vi.su.
CC BY-SA 3.0
2013-02-15T12:24:05.420Z
@vi.su. It may be the case that the vanity address generator uses cryptographically secure random numbers, meaning that you can't really arrive to the same random number with it. It might take things like random temperature reading and what have you that would be impossible to reproduce.
ThePiachu
CC BY-SA 3.0
2013-02-15T07:22:31.827Z
2013-02-15T09:11:12.140Z
2013-02-15T09:11:12.140Z
ThePiachu
<p>In simple terms, if you were testing against 500k patterns at 25/Mkey a second, it'd take about 25 quadrillion years to get a few collisions. Factoring out the randomness of course, as the nature of randomness entails that it could take 2 seconds or 2 sextillion years.</p>

<p>Even if you put all the calculating power of the entire bitcoin network on it, it would still take 10^12+ years.</p>

CC BY-SA 3.0
2015-05-12T20:05:28.493Z
what if a quantum computer was able to do 999/Mkey's a second?
Patoshi パトシ
CC BY-SA 3.0
2013-10-18T00:36:06.300Z
2013-10-18T00:36:06.300Z
nathan
<p>Samr's vanitygen gets its initial private key from OpenSSL's random functions, which have been well vetted. Even if you specify a random seed (which is a good idea to add even more randomness) the entropy generation random libraries from the crypto is still used. It has equal randomness and strength as Bitcoin's address/key generator, with the exception that you are discarding millions of addresses that don't start with your vanity phrase.</p>

CC BY-SA 3.0
2013-02-15T11:48:05.623Z
2013-02-15T11:48:05.623Z
Spanky Monk
<p>With no random number seed specified, assuming all vanitygen runs start with specific chunk for iteration, what are the possibilities of two different vanitygen runs to end up with the same address - private key pair?</p>

CC BY-SA 3.0
2013-02-15T04:09:44.343Z
Related question - 1, 

What's the probability of vanity pools causing RIPEMD-160 (public key hash) collisions 

http://bitcoin.stackexchange.com/questions/5740/whats-the-probability-of-vanity-pools-causing-ripemd-160-public-key-hash-coll
vi.su.
CC BY-SA 3.0
2013-02-15T04:10:34.930Z
Related question - 2, How easy is finding related vanity addresses http://bitcoin.stackexchange.com/questions/7649/how-easy-is-finding-related-vanity-addresses
vi.su.
<vanity-address><vanitygen>
what are the chances of vanitygen address - private key pair collision?
vi.su.
# what are the chances of vanitygen address - private key pair collision?

(Asked by: username_0 on 2013-02-15)

With no random number seed specified, assuming all vanitygen runs start with specific chunk for iteration, what are the possibilities of two different vanitygen runs to end up with the same address - private key pair?

**Tags:** vanity-address, vanitygen

> **Comments:**
> **username_0**: Related question - 1,   What's the probability of vanity pools causing RIPEMD-160 (public key hash) collisions   http://bitcoin.stackexchange.com/questions/5740/whats-the-probability-of-vanity-pools-causing-ripemd-160-public-key-hash-coll  
> **username_0**: Related question - 2, How easy is finding related vanity addresses http://bitcoin.stackexchange.com/questions/7649/how-easy-is-finding-related-vanity-addresses  

---

## 3 answers

### Answer by username_4 on 2013-02-15. Score: 5 | Accepted answer

Samr's vanitygen gets its initial private key from OpenSSL's random functions, which have been well vetted. Even if you specify a random seed (which is a good idea to add even more randomness) the entropy generation random libraries from the crypto is still used. It has equal randomness and strength as Bitcoin's address/key generator, with the exception that you are discarding millions of addresses that don't start with your vanity phrase.


---

### Answer by username_1 on 2013-02-15. Score: 2

If two or more people choose the same, non-random seed while looking for vanity address with the same pattern, they will end up with the same private key. This would happen due to them either iterating to the same private key from the seed, or by ending up with the same private key by using the given language's version of rand() function with identical seeds.

However, if one was to chose a random seed, here are the probabilities of accidentally ending up with the same keypair / address:

To obtain the same [address](https://en.bitcoin.it/wiki/Technical_background_of_Bitcoin_addresses), the result of RIPEMD-160 hashing would need to be the same. Probability of that happening is 1 in 2^160.

To obtain the same private key, it is a probability of 1 in [n](https://en.bitcoin.it/wiki/Secp256k1), where n is the order of [secp256k1](https://en.bitcoin.it/wiki/Secp256k1) and equal to FFFFFFFF FFFFFFFF FFFFFFFF FFFFFFFE BAAEDCE6 AF48A03B BFD25E8C D0364141, or about 2^256.

> **Comments:**
> **username_0**: you didn't get the question, I think. vanitygen tool starts random process of finding a key that matches the given pattern. assuming this search always starts from a known specific chunk (with no random number seed), then it is quiet possible that two different runs to end up with the same pair. right?  
> **username_1**: @vi.su. edited accordingly  
> **username_0**: not true. tried to generate smaller pattern with the same random number seed, and both the runs generated different results. may be there is something like,  time seed (current millisecond), but when I checked the code couldn't found anything related.  
> **username_1**: @vi.su. It may be the case that the vanity address generator uses cryptographically secure random numbers, meaning that you can't really arrive to the same random number with it. It might take things like random temperature reading and what have you that would be impossible to reproduce.  

---

### Answer by username_2 on 2013-10-18. Score: 1

In simple terms, if you were testing against 500k patterns at 25/Mkey a second, it'd take about 25 quadrillion years to get a few collisions. Factoring out the randomness of course, as the nature of randomness entails that it could take 2 seconds or 2 sextillion years.

Even if you put all the calculating power of the entire bitcoin network on it, it would still take 10^12+ years.

> **Comments:**
> **username_3**: what if a quantum computer was able to do 999/Mkey's a second?  

---

