Rare address hall of fame

[jasemoney]

Message:

Code:

31-chars address 111111nFTRm5GCoUNS7mURKmZEJAu1j belong to in100

Signature:

Code:

INc3ltQdAyVGBWSyEPd9tb0BcllgPXfPfxU5ZFAFRsA3GaXhEnRQ8vD7aWXGQ7guE46JTYio5p93TzFStJsZT4w=

ive been trying! so far all ive got is six ones, 111111 and 33 char.

easier to oclvanitygen prefix 111111
than
-r "^1[1-9A-HJ-Za-km-z]{0,32}\$" or however it goes.

would love to be able to use regex on gpu -_-

[1713430971]

1713430971

[basil00]

Wow.  I missed this post but that us amazing!  That would take forever with my rig.  How fast are you able to generate addresses?

Thanks for noticing   It took me about 1 week to generate on a Haswell 4 core / 8 threads.

Using vanitygen to find such pairs of addresses is not feasible, e.g.

$ vanitygen "18eXmgR5Svoqqa6"
[1.34 Mkey/s][total 24407296][Prob 0.0%][50% in 3.161665e+10y]

...so 50% probability in about 32 billion years!

I didn't use vanitygen, but rather a specialized tool designed to find partial address collisions based on the Birthday Attack.  I might clean up the code and release it; although I am not sure if it has any use beyond some novelty value.

The code currently uses CPU only.  But a GPU port would make 100+ bit collisions feasible.

[tspacepilot]

Message:

Code:

31-chars address 111111nFTRm5GCoUNS7mURKmZEJAu1j belong to in100

Signature:

Code:

INc3ltQdAyVGBWSyEPd9tb0BcllgPXfPfxU5ZFAFRsA3GaXhEnRQ8vD7aWXGQ7guE46JTYio5p93TzFStJsZT4w=

ive been trying! so far all ive got is six ones, 111111 and 33 char.

easier to oclvanitygen prefix 111111
than
-r "^1[1-9A-HJ-Za-km-z]{0,32}\$" or however it goes.

would love to be able to use regex on gpu -_-

Since all matches to your regex are going to be finite (bitcoin addresses are of finite length) then you could just compile your regex out to a pattern list and use that.  Ie, because of the finiteness constraint, regexes are just syntactic sugar.

[xhomerx10]

Wow.  I missed this post but that us amazing!  That would take forever with my rig.  How fast are you able to generate addresses?

Thanks for noticing   It took me about 1 week to generate on a Haswell 4 core / 8 threads.

Using vanitygen to find such pairs of addresses is not feasible, e.g.

$ vanitygen "18eXmgR5Svoqqa6"
[1.34 Mkey/s][total 24407296][Prob 0.0%][50% in 3.161665e+10y]

...so 50% probability in about 32 billion years!

I didn't use vanitygen, but rather a specialized tool designed to find partial address collisions based on the Birthday Attack.  I might clean up the code and release it; although I am not sure if it has any use beyond some novelty value.

The code currently uses CPU only.  But a GPU port would make 100+ bit collisions feasible.

 This is very interesting.  I have some reading to do!  Thanks

[tspacepilot]

Wow.  I missed this post but that us amazing!  That would take forever with my rig.  How fast are you able to generate addresses?

Thanks for noticing   It took me about 1 week to generate on a Haswell 4 core / 8 threads.

Using vanitygen to find such pairs of addresses is not feasible, e.g.

$ vanitygen "18eXmgR5Svoqqa6"
[1.34 Mkey/s][total 24407296][Prob 0.0%][50% in 3.161665e+10y]

...so 50% probability in about 32 billion years!

I didn't use vanitygen, but rather a specialized tool designed to find partial address collisions based on the Birthday Attack.  I might clean up the code and release it; although I am not sure if it has any use beyond some novelty value.

The code currently uses CPU only.  But a GPU port would make 100+ bit collisions feasible.

 This is very interesting.  I have some reading to do!  Thanks

Hey, same here,  thanks to both basil00 for the feat and for xhomerx10 for drawing my attention to it!

[Velkro]

1BubbLingsoup9hqv7cjnnrWFt9GmEmCHS      (12-char real-word vanity address - owner: xhomerx10)

This is really impressive. Im using site that offer up to 9 char long case insensitive address. Though they are good, but this is another level :O

[TheGr33k]

1BubbLingsoup9hqv7cjnnrWFt9GmEmCHS      (12-char real-word vanity address - owner: xhomerx10)

This is really impressive. Im using site that offer up to 9 char long case insensitive address. Though they are good, but this is another level :O

Dont use online vanity gens, they are known to steal your money. Use the vanity gen software.

[tspacepilot]

1BubbLingsoup9hqv7cjnnrWFt9GmEmCHS      (12-char real-word vanity address - owner: xhomerx10)

This is really impressive. Im using site that offer up to 9 char long case insensitive address. Though they are good, but this is another level :O

Dont use online vanity gens, they are known to steal your money. Use the vanity gen software.

There are vanity pools that use the split key technique so that you've got guarnteed saftey, but if these online vanitygens aren't doing that, then it certainly is dangerous.

[Velkro]

Dont use online vanity gens, they are known to steal your money. Use the vanity gen software.

I heard there was scam website like that before (scandal described on reddit), but im using address generated by online website for 8 months now and never got any problems.

[r3wt]

Not a single address, but how about the "longest shared prefix"?

18eXmgR5Svoqqa6PaYVrKvbH6hvrp5xe3A
18eXmgR5Svoqqa6JXSMmbNaD4Cs5ThcV1P

(15 chars)

The hash160 shares 83bits:

53e1f4f491509f9012bd901be5147447f770018b
53e1f4f491509f9012bd825ce1e9599b253188ef

over half of the address.

The addresses are on the blockchain.  Proof of ownership:
"This address is controlled by basil00."
H3l9fTn8FRRMvBdiF0Wx/hV/aKQ+OsTjmzrF6/3X9KwlWmxbeb12KzkMHqG4AvJPj5PJUErLTkksnf+JbQEmd6E= (address #1)
H5fp1+mGX8D9ImzapYG1MC/V86N9RbDbYSfbLpyWaUH1ptnfbR+OP9Mt+fnC5UgyziuP6BHsDNUtb9c5jcTqBes= (address #2)

i vote this goes into the hall of fame.

[godlyitems]

19dFcBU96MGkKLibVZ3ncNmtZz7Chk9j5K

Well, nothing special here lol  . By the way can we generate our wallet address ?
Like we can use anything we want, for easy to remember that address.

[basil00]

Not a single address, but how about the "longest shared prefix"?

18eXmgR5Svoqqa6PaYVrKvbH6hvrp5xe3A
18eXmgR5Svoqqa6JXSMmbNaD4Cs5ThcV1P

The tool I used to generate these addresses is now available here: https://github.com/basil00/pairgen
A pre-built version is here: https://github.com/basil00/pairgen/releases

[e1ghtSpace]

Not a single address, but how about the "longest shared prefix"?

18eXmgR5Svoqqa6PaYVrKvbH6hvrp5xe3A
18eXmgR5Svoqqa6JXSMmbNaD4Cs5ThcV1P

The tool I used to generate these addresses is now available here: https://github.com/basil00/pairgen
A pre-built version is here: https://github.com/basil00/pairgen/releases

Nice! Thanks for releasing this, maybe I can find a cool address like that.
Have you found any more addresses like that recently?

[Satu]

Not a single address, but how about the "longest shared prefix"?

18eXmgR5Svoqqa6PaYVrKvbH6hvrp5xe3A
18eXmgR5Svoqqa6JXSMmbNaD4Cs5ThcV1P

The tool I used to generate these addresses is now available here: https://github.com/basil00/pairgen
A pre-built version is here: https://github.com/basil00/pairgen/releases

Look good. Now I can easily find similar addresses. Might be downloading it when more people downloaded it.

[basil00]

Have you found any more addresses like that recently?

I am attempting to generate a second 80-bit address pair, but no luck yet.  Pairgen is a bit different than vanitygen, in that the more work you do, the probably of finding a solution increases.  I was actually lucky to find the first pair so quickly (after one week, was expected about two weeks).

You can however easily generate smaller pairs, e.g. 51-bit collision (for 10chars) generated just now:

message = "This is a real Bitcoin address."
sig[1] = HxupEyHga60CrSmm298Zp1thMYIsAoGaaGCusFKSSYkkf40nQx0dZsxd8jdQlW1wkJIQ8GPPsvOyZXd 2rjOpI8o=
sig[2] = IGUrV4deRXq7DfSOzHgl6DgbwGr5dSp+SCi4ApehLf4AADNVhb1BgfHxZuwpHgicd2ioHY342WbZFsAiTXMx2Vc=
shared = 10chars
addr[1] = 17qvygfdtmtnqAkGpStab7rfXQTvirMhZT
addr[2] = 17qvygfdtmharpKrTahbL1oQvSb9vTqVYt

This took about 46 seconds to generate.

As a very very rough guide (based on my CPU), ~40bits = 3seconds, ~50bits = 1minute, ~60bits = 1hour, ~70bits = 1day, ~80bits = 10 days, etc., etc.

If you want to really go nuts, you can use the "--job" to distribute address generation across multiple machines (see the docs).  This is similar to vanitygen's split key mining.  With enough cores, probably 100+ bits are do-able.  Alternatively, one could port pairgen to use vanitygen's calc_addrs.cl for GPU mining.

[TheGr33k]

19dFcBU96MGkKLibVZ3ncNmtZz7Chk9j5K

Well, nothing special here lol  . By the way can we generate our wallet address ?
Like we can use anything we want, for easy to remember that address.

Not anything we want, its random. Vanity gen just generates millions or billions of addresses untill it finds a pattern you specified. You cab get words at the start of your address. Like 1Greekhut is one I generated

[xhomerx10]

Not a single address, but how about the "longest shared prefix"?

18eXmgR5Svoqqa6PaYVrKvbH6hvrp5xe3A
18eXmgR5Svoqqa6JXSMmbNaD4Cs5ThcV1P

The tool I used to generate these addresses is now available here: https://github.com/basil00/pairgen
A pre-built version is here: https://github.com/basil00/pairgen/releases

 Thanks a lot for putting your software out there for us to use!
Can't wait to get home to try this out

[funtotry]

I see most of the addresses are from the vanity person, when generating vanity addresses, you can put on log all addresses and therefore you can have the MILLIONS of addresses per seconds logged in a file, which you can then search for some cool patterns later. If your going for some "novelty" addresses, I think doing that is the best way.

[tspacepilot]

Not a single address, but how about the "longest shared prefix"?

18eXmgR5Svoqqa6PaYVrKvbH6hvrp5xe3A
18eXmgR5Svoqqa6JXSMmbNaD4Cs5ThcV1P

The tool I used to generate these addresses is now available here: https://github.com/basil00/pairgen
A pre-built version is here: https://github.com/basil00/pairgen/releases

 Thanks a lot for putting your software out there for us to use!
Can't wait to get home to try this out

Thanks from me as well.  I read about the birthday attack and I think I understand it pretty well.  I'm looking forward to browsing your code to see the implementation you came up with.

[funtotry]

Not a single address, but how about the "longest shared prefix"?

18eXmgR5Svoqqa6PaYVrKvbH6hvrp5xe3A
18eXmgR5Svoqqa6JXSMmbNaD4Cs5ThcV1P

(15 chars)

The hash160 shares 83bits:

53e1f4f491509f9012bd901be5147447f770018b
53e1f4f491509f9012bd825ce1e9599b253188ef

over half of the address.

The addresses are on the blockchain.  Proof of ownership:
"This address is controlled by basil00."
H3l9fTn8FRRMvBdiF0Wx/hV/aKQ+OsTjmzrF6/3X9KwlWmxbeb12KzkMHqG4AvJPj5PJUErLTkksnf+JbQEmd6E= (address #1)
H5fp1+mGX8D9ImzapYG1MC/V86N9RbDbYSfbLpyWaUH1ptnfbR+OP9Mt+fnC5UgyziuP6BHsDNUtb9c5jcTqBes= (address #2)

I am personally not a fan of shared prefixes, when I send stuff I check the first 8 or so digits, and if they are the same, I send it. Theres a VERY small chance the address I forgot to copy has the same first 8 digits as the address copied by mistake, so this practice works very well for me. I also see no reason to have address pairs unless to trick people.