Topic: Rare address hall of fame - page 17. (Read 65005 times)

That's cool, but, don't you get confused because both your addresses there have half the address in common?
They both start the same..

I'd suspect he could always keep them apart as 'PaY' and 'TheV1P'

Quote from: basil00 on April 28, 2015, 08:07:10 AM

Also, is it possible to give it a prefix?
Like Vanity, e.g: 1xxxxx

For that, you'd be better off with vanitygen.
The addresses he generated rely on the birthday paradox. E.g. in a large crowd, chances are good two people share the same birth date (ignoring year) - but there's no telling in advance if that date is January 20th, May 1st or August 14th. Same with addresses - generate a bunch of them, and two are likely to share a characteristic - the same starting bits, ending bits, middle ~~bitch~~bits! (I meant BITS! Oh dear), whatever you'd set as criteria.. but the exact values can't be determined in advance.

Would this be considered a Birthday paradox event

1BirthDAY5nLWc9HLciynq5FSNWhemk5Kw
1BirthDayjAuMBf4XSs3VQV3UfE3UeVapb

Lol, funny but no. TheRealSteve was referring to this post:

Quote from: xhomerx10 on April 27, 2015, 01:58:21 PM

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 Wink

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.

Check out that wikipedia link to get the scoop.

BG4

legendary

Activity: 1006

Merit: 1024

PaperSafe

Quote from: TheRealSteve on May 06, 2015, 07:59:57 AM

That's cool, but, don't you get confused because both your addresses there have half the address in common?
They both start the same..

I'd suspect he could always keep them apart as 'PaY' and 'TheV1P'

Quote from: TheRealSteve on May 06, 2015, 07:59:57 AM

Also, is it possible to give it a prefix?
Like Vanity, e.g: 1xxxxx

For that, you'd be better off with vanitygen.
The addresses he generated rely on the birthday paradox. E.g. in a large crowd, chances are good two people share the same birth date (ignoring year) - but there's no telling in advance if that date is January 20th, May 1st or August 14th. Same with addresses - generate a bunch of them, and two are likely to share a characteristic - the same starting bits, ending bits, middle ~~bitch~~bits! (I meant BITS! Oh dear), whatever you'd set as criteria.. but the exact values can't be determined in advance.

Would this be considered a Birthday paradox event

1BirthDAY5nLWc9HLciynq5FSNWhemk5Kw
1BirthDayjAuMBf4XSs3VQV3UfE3UeVapb

louise123

sr. member

Activity: 462

Merit: 250

That's cool, but, don't you get confused because both your addresses there have half the address in common?
They both start the same..

I'd suspect he could always keep them apart as 'PaY' and 'TheV1P'

Also, is it possible to give it a prefix?
Like Vanity, e.g: 1xxxxx

For that, you'd be better off with vanitygen.
The addresses he generated rely on the birthday paradox. E.g. in a large crowd, chances are good two people share the same birth date (ignoring year) - but there's no telling in advance if that date is January 20th, May 1st or August 14th. Same with addresses - generate a bunch of them, and two are likely to share a characteristic - the same starting bits, ending bits, middle bitch, whatever you'd set as criteria.. but the exact values can't be determined in advance.

Got it.
Thanks!

TheRealSteve

hero member

Activity: 686

Merit: 500

FUN > ROI

That's cool, but, don't you get confused because both your addresses there have half the address in common?
They both start the same..

I'd suspect he could always keep them apart as 'PaY' and 'TheV1P'

Also, is it possible to give it a prefix?
Like Vanity, e.g: 1xxxxx

For that, you'd be better off with vanitygen.
The addresses he generated rely on the birthday paradox. E.g. in a large crowd, chances are good two people share the same birth date (ignoring year) - but there's no telling in advance if that date is January 20th, May 1st or August 14th. Same with addresses - generate a bunch of them, and two are likely to share a characteristic - the same starting bits, ending bits, middle ~~bitch~~bits! (I meant BITS! Oh dear), whatever you'd set as criteria.. but the exact values can't be determined in advance.

louise123

sr. member

Activity: 462

Merit: 250

Quote from: tspacepilot on May 05, 2015, 02:45:46 PM

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)

That's cool, but, don't you get confused because both your addresses there have half the address in common?
They both start the same..

Also, is it possible to give it a prefix?
Like Vanity, e.g: 1xxxxx

Nikinger

full member

Activity: 141

Merit: 100

Kinda too bad that there's no 0 in bitcoin base58 encoding, it would be nice to have a 0 after that 9

You can use "o" instead. I think both 123456789o123... and 123456789123... would be a canidate for the hall of fame Wink

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: 98problems on May 05, 2015, 02:15:46 PM

Quote from: tspacepilot on May 05, 2015, 01:57:22 PM

Quote from: tspacepilot on May 05, 2015, 01:57:22 PM

Does this address make it into the hall...??

1234567891p1rBJWFPmHTUiupi1VA6YKQw

Pretty cute but it seems borderline to me for hall of fame. Definitely a good one, but I don't know if it's top 10.

but theres no such type address and its unique i think the thread owner should add it

Kinda too bad that there's no 0 in bitcoin base58 encoding, it would be nice to have a 0 after that 9

98problems

sr. member

Activity: 364

Merit: 250

Does this address make it into the hall...??

1234567891p1rBJWFPmHTUiupi1VA6YKQw

Pretty cute but it seems borderline to me for hall of fame. Definitely a good one, but I don't know if it's top 10.

but theres no such type address and its unique i think the thread owner should add it

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Does this address make it into the hall...??

1234567891p1rBJWFPmHTUiupi1VA6YKQw

Pretty cute but it seems borderline to me for hall of fame. Definitely a good one, but I don't know if it's top 10.

98problems

sr. member

Activity: 364

Merit: 250

Quote from: tspacepilot on May 01, 2015, 05:44:49 PM

Does this address make it into the hall...??

1234567891p1rBJWFPmHTUiupi1VA6YKQw

yeah it should be on it as it seems to be 9 digits in a row vanity address, also is it yours?

BG4

legendary

Activity: 1006

Merit: 1024

PaperSafe

Does this address make it into the hall...??

1234567891p1rBJWFPmHTUiupi1VA6YKQw

basil00

member

Activity: 60

Merit: 10

Indeed, since you have to generate these as a pair, it'd be really unlikely that one person should have one half of the pair and a scammer would have the other half. They'd essentially have to vanitygen on the other half and that would take crazy long for some of these prefixes.

This is correct. For a shared prefix of n-bits, you can be sure (with n-bits of security) that they were generated as a pair. For n=80, this is a non-trivial level of security, but not considered "strong" by most standards. For reference, Bitcoin itself has 128 bits of security, so there is still a while to go.

tspacepilot

legendary

Activity: 1456

Merit: 1081

I may write code in exchange for bitcoins.

Quote from: xhomerx10 on May 01, 2015, 05:05:03 PM

Quote from: funtotry on May 01, 2015, 02:34:45 PM

Quote from: funtotry on May 01, 2015, 02:34:45 PM

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.

This is experimentation. I doubt you will see too many addresses like this in use and even if you do, they will belong to the same person anyway so the odds of your payment going to some scammer are very, very low.

Indeed, since you have to generate these as a pair, it'd be really unlikely that one person should have one half of the pair and a scammer would have the other half. They'd essentially have to vanitygen on the other half and that would take crazy long for some of these prefixes.

xhomerx10

legendary

Activity: 3808

Merit: 7912

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.

This is experimentation. I doubt you will see too many addresses like this in use and even if you do, they will belong to the same person anyway so the odds of your payment going to some scammer are very, very low.

funtotry

sr. member

Activity: 420

Merit: 250

Ever wanted to run your own casino? PM me for info