Why does my solution not always match after combining two keys it gives a completely different address? I have found the correct address.
https://gobittest.appspot.com/VanityAllI checked other options found and they also did not all match; the first symbols of the address were completely different after combining the two keys.
ThePiachu Continues to work on fixing payments from the pool site.
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).
ThePiachu Continues to work on fixing payments from the pool site.
Out of curiosity: did you receive the payment for your solution of
1iJuniorTV?
Here's a pretty good writeup explaining it all. TLDR user generated a child key.
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.