I've gone through every inch of the SC of VS , his functions are incomplete when using a pub key with prefix.  Theres no discarding splitkeys in vs. if a function checks out .if it just so happens to find a child wallet it tells you that's fine. The other program doesn't. But it's nowhere near as complex as VS

The only question I really have is why does this happen with LEGACY wallets!  Why do legacy wallets have child keys?

There are more people who would probably know what's going on here  if they see the post. I didn't get into VS until 2019 or so.

Which software do you use to find a work item solution (I might've missed it in case you already wrote about it)?

Did you modify the software in any way?


I can't remember having issues to submit the first hit of a work item solution many many years ago when vanitypool was rather new and there were plenty of not terribly hard work items available (GPUs back then weren't as powerful as today's and I only had a barely middle-class one).

It would be against all odds that I was purely lucky that my first found solution to a work item was just one that worked out fine, if there were detected "solutions" that won't spit out the correct public address prefix after combining the keys.

Why would there be something like "1 in 6" chance? That's nonsense in my opinion as I don't see any mathematical proof for such ambiguity. This sounds much like some strange bug in the software.

And I also can't remember any discussion about such an issue in this thread earlier (not that I've followed the many pages of it to the word).

If you combine the public key from the requestor with the public key derived from your found private key, the combined public key (added or multiplied, don't remember what vanitypool used) should hash to the requested public address prefix. There's not much room for ambiguity.

I'm not sure if I understand what you're trying to tell. Of course the vanitypool website could still have some bugs, but if it doesn't accept your "solution" than I'd rather think something is wrong with your "solution" or your toolset than otherwise.

If you have a correct split-key solution, it will always give the proper public address prefix when combined properly (i.e. not messing up with compressed/uncompressed keys or adding split-keys when multiplying is required or vice-versa).

Out of curiosity: did you receive the payment for your solution of 1iJuniorTV?

For fun, I checked other key variants for 1iJuniorTV and out of 15 variants, only about 5 had matching prefixes.
1RoseCross found 6 variants and none of them had matching prefixes at all.
ThePiachu paid me 0.01 BTC from his own funds for the solution for 1iJuniorTV.

Your cited article doesn't have anything to do with vanitypool. I mean, I could be blind and not see a connection, so beat me to it, please.

Why do you bring up the topic of HD wallet address derivation and try to mingle that with split-key combining for a safe vanity public address that someone else has computed for you?

Vanitypool doesn't use an extended master private key or similar BIP32 stuff.

You found a solution. Not the solution. Try again.
Your keypairs  aren't merging to a known prefix .
You have about a 1 in 6 chance of getting it right the first time.
There is a slight chance something may be going wrong on the backend. But I doubt it. (This is why I'm pretty certain your keypairs are mismatched) Correct solution. Incorrect merged prefix.

I'm not saying Piachu will rug pull but BTC did just hit 100k I'm pretty sure a lot of people are going to exit soon. Just hope your endeavors don't get pulled.

You found a solution. Not the solution. Try again.
Your keypairs  aren't merging to a known prefix .
You have about a 1 in 6 chance of getting it right the first time.
There is a slight chance something may be going wrong on the backend. But I doubt it. (This is why I'm pretty certain your keypairs are mismatched) Correct solution. Incorrect merged prefix.

I'm not saying Piachu will rug pull but BTC did just hit 100k I'm pretty sure a lot of people are going to exit soon. Just hope your endeavors don't get pulled.

That's likely good news and you may collect your bounty in the end.

ThePiachu continues to work on the repair of payments of remuneration through the site, he needs time to resolve this issue! Received payment for 1iJuniorTV from ThePiachu directly in the amount of 0.01BTC.

That's likely good news and you may collect your bounty in the end.

I'm curious, do you mind telling us how long you searched for a solution?

What equipment did you use to crunch on this particular problem? Did you search only for this or also for the other available work items?

@ThePiachu Confirmed the existence of a problem with the transfer of bitcoins. And assured that he is working on solving this issue, but he needs some time to do so.

You don't provide any details to help you, except that you have some issue and it seems like you don't get the finding bounty.

How about you provide some more details for this split-key solution problem? I don't ask for the solution itself, that should be obvious.

What software did you use?
What command line arguments did you use?
Was the solution automatically submitted or did you submit the solution manually?
What address type did you use to collect the solution bounty (see below)?
Did you get some error message or something similar in your log file when trying to collect the solution bounty?
Did you check that your split-key solution actually produces a correct address prefix?

Did you contact the original creator? When I look into the profile of ThePiachu, the user was last active quite recently: 2024-10-12, 18:16:52 UTC. You can also mention him here, like with @ThePiachu, but seriously provide more details for debugging your problem. Nobody here can read your mind!


I once solved one of the former and way easier work items offered, but that was a very long time ago. The bounty payment came swiftly to my provided legacy payment address.

Did you use a legacy address type (addresses that start with 1...) as I wouldn't expect if the site can handle wrapped segwit or native segwit addresses!?

The Pool should still be up, haven't heard of anyone complain about it in awhile.

Этот токен в своё время был в лаунчпаде Gate.io и его там продавали по 9 центов, собрали всего лишь 50 000$. Не исключаю, что сама биржа решила, скупив токены по дешевке, после того как они на 99% подешевели, сейчас задрать цену и скинуть по оверпрайсу это говно еще раз своим клиентам. Справедливая цена этого актива сильно ниже 1 цента.

А с чего ты решил, что цена на мексе будет стремиться к цене гэйта, а не наоборот? Это чистое казино и заработками там даже не пахнет, скорее риском встрят на деньги. На сайтах мониторинга цена этого актива составляет 0.004, это только на гейте почему то маркетосы задрали цену.

Ага, подставляйте карман шире. Прям там дураки сидят, позволят простым хомякам такую маржу получить.



Удачи в получении иксов.