You've got the right idea towards this, having it posted on some service board. Bounties perhaps and your wallet would be created on it's required number within hours. The issue is, you don't expect any privacy of wallets created. The bounty users would always have the private keys or seed phrase to them wallets.
When you refer to coding for a means,
How do one archive that with regards to OP's quest?
When you refer to coding for a means,
How do one archive that with regards to OP's quest?
Obviously OP will get a program that creates wallets and not just the wallets themselves. This still poses a security risk that the code can be malicious and generate wallets non-randomly or send a copy to authors server, so the code should be independently verified or OP will have to just trust that they won't get robbed. But this isn't very different from typical crypto jobs when someone asks to create a service involving receiving money, and there's a risk that the developer will put a backdoor.
