Pretty Addy Giveaway - part 2

[LoyceV]

Prefix: PoWer (case sensitive, please).

Here you go:
Address: 1PoWer4mBDHy2QgZXBGNW4sejgFNek4Mdz
PrivkeyPart: 5HtqtqqAj4kffihHN4PY7hgVzhzgshmGRrZkx3NtzXG4fKa9wdr
1PoWer4mBDHy2QgZXBGNW4sejgFNek4Mdz (Balance: )

[1714562345]

1714562345

[1714562345]

1714562345

[1714562345]

1714562345

[sam00]

Heyy, can you try "1SAMUEL..." please ? Wish I could go for 1sam00, too bad there are no zeros

public:

Code:

044931134B309B22EF9A04ACD42CEE30EEF7CC253E2524F1207FDD92A2AC878DE8B79CCC5FB88BDD8BD8DA5D3A2282455BE75050010366CEBB69CA6C165B3C5756

private:

Code:

just kidding

thank you LoyceV!:)

[LoyceV]

Heyy, can you try "1SAMUEL..." please ?

Nope, sorry My most recent upgrade broke things:

Code:

Difficulty: 27763956579
clGetPlatformIDs(0): Unknown code -1001
clGetPlatformIDs(0): Unknown code -1001
Available OpenCL platforms:

Getting it to work (years ago) was a lot more work than I expected, so I need some time to fix it again. Without GPU, it takes far too long to generate.

Maybe someone else can jump in for now?

[sam00]

Heyy, can you try "1SAMUEL..." please ?

Nope, sorry My most recent upgrade broke things:

Code:

Difficulty: 27763956579
clGetPlatformIDs(0): Unknown code -1001
clGetPlatformIDs(0): Unknown code -1001
Available OpenCL platforms:

Getting it to work (years ago) was a lot more work than I expected, so I need some time to fix it again. Without GPU, it takes far too long to generate.

Maybe someone else can jump in for now?

No problem, good luck fixing your setup

Maybe it's time for me to fire up the vanitygen myself

[LoyceV]

Heyy, can you try "1SAMUEL..." please ?

Code:

044931134B309B22EF9A04ACD42CEE30EEF7CC253E2524F1207FDD92A2AC878DE8B79CCC5FB88BDD8BD8DA5D3A2282455BE75050010366CEBB69CA6C165B3C5756

I got it to work again, but 6 characters case-insensitive is too much for this giveaway (it takes a day for 50% chance on my old system). I got you this:
Address: 1saMuELQnb5egBTck8WfFahtesjLSbgtX (Balance: )
PrivkeyPart: 5JktvqcBdMK8odxgXY6akT2k8Vw2rJe7B3W6ogjZGrsdEijQQRi

[sam00]

Heyy, can you try "1SAMUEL..." please ?

Code:

044931134B309B22EF9A04ACD42CEE30EEF7CC253E2524F1207FDD92A2AC878DE8B79CCC5FB88BDD8BD8DA5D3A2282455BE75050010366CEBB69CA6C165B3C5756

I got it to work again, but 6 characters case-insensitive is too much for this giveaway (it takes a day for 50% chance on my old system). I got you this:
Address: 1saMuELQnb5egBTck8WfFahtesjLSbgtX (Balance: )
PrivkeyPart: 5JktvqcBdMK8odxgXY6akT2k8Vw2rJe7B3W6ogjZGrsdEijQQRi

Thank you LoyceV! Glad you got your setup working again. I experimented with vanitygen and vanitysearch myself in the past few days and luckily got my own 8-digits/character key working after I ran into a few issues.
bc1qsam00000rymzeeyfwh7f3vcmc5y79fsqam5rc2

Should've told you that you don't have to search for my prefix, sorry!

I will keep a look on this thread and maybe hop in another time when your system breaks

[LoyceV]

2 month Bump 
Free Pretty Addy still available, just follow the Instructions and post here.

[efialtis]

Hello Loyce,

I hope you are well!

Would you mind getting me another GOSU address? 

Public Key: 048B7F75DB3A24342206BAC18DAB1E176D2E6C222B588D613BA3B89BB7CB523F10BCBAE8D9F57C8 5060B122FFAC2023D4B5979783328F1EBF87B6120038952240C

Prefix: 1btcgosu

Thank you very much in advance!

[LoyceV]

048B7F75DB3A24342206BAC18DAB1E176D2E6C222B588D613BA3B89BB7CB523F10BCBAE8D9F57C8 5060B122FFAC2023D4B5979783328F1EBF87B6120038952240C

Prefix: 1btcgosu

The best I can do for 7 characters is case insensitive:
Address: 1BTCGoSUfdnhdj7rMuqupJEvbHo8UW9aQE
PrivkeyPart: 5KZGcbD6W5j9eo42U7725zyD9zV8dCGNrEMQE8n8ZW2U3bPurrY

[Clairvoyance]

Greetings Loyce!
I hope my Prefix is eligible.

Public Key:

Code:

 040FFF57C679F50029C236B7ECC3A23B13FD28B8717876CF685DA74F57C019F610265F1E1540355F06B63BA3B7DDFD7FA642814FB733E29C748EB6675B783AAF2A 

Prefix:

Code:

 1Cla1rvoyance 

[LoyceV]

I hope my Prefix is eligible.
Prefix:

Code:

 1Cla1rvoyance 

Lol
Please read the part on Limitations

[Clairvoyance]

I hope my Prefix is eligible.
Prefix:

Code:

 1Clairvoyance 

Lol
Please read the part on Limitations

Pardon my lapses, here is the new Prefix.

Code:

 1Future 

Edited;

Is there a fee if I want it to be more than 6 characters? (I will save up for this in-case)

[LoyceV]

Code:

 040FFF57C679F50029C236B7ECC3A23B13FD28B8717876CF685DA74F57C019F610265F1E1540355F06B63BA3B7DDFD7FA642814FB733E29C748EB6675B783AAF2A 

Code:

1Future 

I got you this:
Address: 1FutureZDmv2GbmJEkugaGvCvExbpqAaEj
PrivkeyPart: 5J7g65w4fytWk69evhZH7WbSj5ErUj8M9QG2Hr3cDGkbrHzwgog

Is there a fee if I want it to be more than 6 characters? (I will save up for this in-case)

I can do it for a fee, but keep in mind it can't be much longer: every additional character makes it 58 times harder to find. So 7 characters can take a while and 8 might not be possible.

[Fivestar4everMVP]

Hi LoyceV,
Thank you for such a wonderful giveaway, i have come to have my own slice of the cake .
please find my details below.

Public key :   
04532E32E45E8F5EB098D740B2CC926F53BEE40566ECF393CF5D87085FBD91971AE00F226517013 A453B19945E3EFBF0234B18A4573D257A6889067346C890E801

Prefix: 15star (if this is possible, then i will go with it since "1Fivestar" which would have been my preferred prefix is more than 6 characters which is the limit , but incase for some reasons, this doesnt or can not work, then check the option below).

Second Prefix(incase first prefix does not work): 1FiveSt

i will prefer case sensitive.
Thanks much for all the effort. 

[LoyceV]

Public key :  
04532E32E45E8F5EB098D740B2CC926F53BEE40566ECF393CF5D87085FBD91971AE00F226517013 A453B19945E3EFBF0234B18A4573D257A6889067346C890E801

Prefix: 15star

There's a problem: oclvanitygen broke after updating graphics drivers, and I can't compile it anymore. Somehow it's linked to the wrong libraries by now.

I tried WhyFhy's site 1SPLiTKEY.com, but didn't receive an email. @WhyFhy: can you check this?

[o_e_l_e_o]

Here you go:

PubAddress: 15starM7dZoz3bzD4utKJ6RRxXGv2mCRXq
PartialPriv: 5K9effT7wMAjcDRcLfsp9XX2QwStGUudKMU3G3skmHkNLD3qB3x

PubAddress: 1FiveSt1NBDYRd9Ce4LBceHCnjSXza4H9x
PartialPriv: 5JeHJcfpqPWeMCB3JUrEgdyr7ch4JAvYwoRHcu5Ef7XrBu9zGty

I believe that every time I've tried this, it hasn't worked for whatever reason without requiring the user to download VanitySearch themselves to reassemble the key.

So, I've just been poking about with this interaction between VanitySearch and bitaddress and discovered a few things.

Firstly, it works sometimes, but not other times. My initial thought was that since both pieces of software say they are adding the private keys together to reach the final private key, that it has something to do with how they deal with resulting private keys which are beyond the upper limit of the curve order. I thought that if the resulting private key is below the upper limit then they both return the same private key, but if it is above the upper limit then something is different with how they wrapping it back around and so you end up with different private keys and addresses. Both VanitySearch and bitaddress say they are simply adding the keys together modulo n, however, so this doesn't appear to the case. *shrug*

Secondly, it is not unique to segwit addresses, and the same behavior can be seen with legacy address.

However, you can still make it work by just generating a bunch of addresses with the relevant prefix and then testing them yourself in bitaddress one by one using the two public keys rather than the two private keys. You will eventually find one that works.

[Fivestar4everMVP]

Here you go:

PubAddress: 15starM7dZoz3bzD4utKJ6RRxXGv2mCRXq
PartialPriv: 5K9effT7wMAjcDRcLfsp9XX2QwStGUudKMU3G3skmHkNLD3qB3x

PubAddress: 1FiveSt1NBDYRd9Ce4LBceHCnjSXza4H9x
PartialPriv: 5JeHJcfpqPWeMCB3JUrEgdyr7ch4JAvYwoRHcu5Ef7XrBu9zGty

@LoyceV @o_e_l_e_o, I appreciate the both of you for your efforts, thank you so much, but unfortunately, the operation did not work, and I can assure you guys that I followed the instructions as it is on the first page, but after inputting the first private key which i save and also inputting the partial private key that was provided here, I got the error in the screenshot below

Probably, there's something am doing wrong, I am not sure honestly, but I am very sure I followed the instructions as its written in page 1 of this thread.

[LoyceV]

Probably, there's something am doing wrong, I am not sure honestly, but I am very sure I followed the instructions as its written in page 1 of this thread.

Have you tried to reproduce this example?

[o_e_l_e_o]

@LoyceV @o_e_l_e_o, I appreciate the both of you for your efforts, thank you so much, but unfortunately, the operation did not work, and I can assure you guys that I followed the instructions as it is on the first page, but after inputting the first private key which i save and also inputting the partial private key that was provided here, I got the error in the screenshot below

"Invalid input" means exactly that - one of the two keys you have copied in is invalid. I've double checked and both the keys I gave you above are valid, which means either you are not copying/pasting them accurately, or you did not accurately save your original private key.

Double check everything again, and if it still fails, then generate a new key pair and I will generate some new addresses for you.

[DarkStar_]

I believe that every time I've tried this, it hasn't worked for whatever reason without requiring the user to download VanitySearch themselves to reassemble the key.

So, I've just been poking about with this interaction between VanitySearch and bitaddress and discovered a few things.

Firstly, it works sometimes, but not other times. My initial thought was that since both pieces of software say they are adding the private keys together to reach the final private key, that it has something to do with how they deal with resulting private keys which are beyond the upper limit of the curve order. I thought that if the resulting private key is below the upper limit then they both return the same private key, but if it is above the upper limit then something is different with how they wrapping it back around and so you end up with different private keys and addresses. Both VanitySearch and bitaddress say they are simply adding the keys together modulo n, however, so this doesn't appear to the case. *shrug*

Secondly, it is not unique to segwit addresses, and the same behavior can be seen with legacy address.

However, you can still make it work by just generating a bunch of addresses with the relevant prefix and then testing them yourself in bitaddress one by one using the two public keys rather than the two private keys. You will eventually find one that works.

Hmm, very interesting - nice find! I do recall my first attempt at splitkey segwit vanity working when I tested it myself, but it didn't work when I tried to do it for someone else so I figured I just somehow messed up in my own testing. That might explain why I was able to do it the first time.

I do see a GitHub issue where someone asked if symmetry and endomorphism optimizations could be turned off when doing split-key generation for a third party, so I wonder if that could be related. Unfortunately I don't have the time to look through the code myself right now