Is there a way to allow somebody else to mine a vanity prefix npub without letting them see the final private key?

Here's my thinking. I create a new Private Key by myself and I share its public key with a miner. The miner must find the private key that, when its npub is summed into mine, creates the vanity prefix I want. In that case, I can then buy the private key out of the miner, sum with mine, and have a new private key. The miner wouldn't have access to the new private key.

Does that work? Or am I missing something?

Does that mean we can create trustless mining markets that people can just take orders to mine new Nostr Keys and sell them? 🤔

Reply to this note

Please Login to reply.

Discussion

You looking to sell your Nostr profile?

🤣

3 BTC and its yours.

Haha 🤣, does that come with play store right and githubs to Amethyst? 🤣

I love this place....

🤣🤣🤣🤣

And ownership of the Name Victor Pamplona? 🤣

2.99 BTC for mine 🫡

Comes with a Steam Account

We should open a market.

Always thinking 🤔

I dunno but I tried mining a vanity npub and decided it wasn't worth it. it'd pay but I expect people will expect a lot for these.

how many characters did want in your npub?

i mined mine (7 char) in less than 2 days using a 12 core cpu along with 2 others with alternative spellings.

10. any permutation of sacredpeak with numbers and letters. I should try again.

I'm working on a new interactive poetry idea for here so I'll try again with a custom npub and be less impatient

15 :)

yucky. i feel you

why use much char when few char do trick

Wow 15, I wanted to flex with 9... :-)

Sounds possible with BIP-32. Generate a seed private key and give its xpub to a miner. The miner can computes as many public key as it wants by bruteforcing non-hardened derivation paths, and once it finds one that matches your criteria, it replies with the derivation path. Only you can compute the private key with the seed private key and the derivation path.

Throw away the seed once you're done, don't reuse, otherwise the miner might correlate your npubs.

It worked a year ago, as I recorded the demos, but now some APIs have changed and it stopped working.

I can fix them if anyone's interested.