Hey!

In short: looking for a couple of guys willing to fund Faster and Autonomous Large Bitcoin Collider fork.

If you like LBC and its Remote Exec Feature do not read any more.

If you do not mind to spend $1100 alone, actually you do not need me, go to upwork.com and find a freelancer.

OK, if you are still here, I'll explain.

1.
LBC itself has a BIG problem - it is heavily CPU bound.
A classic mining rig with 4-6 GPUs is almost useless with it.
Most of GPUs will be underutilized.
By contrast oclvanitygen even now uses 100% of GPU. After moving ALL processing to GPU it will be super scalable.

2.
LBC users have a BUNCH of problems - your hardware is not utilized, you do not know what addresses are in bloom filter, you do not know what Rico executes on your PC, you cannot be sure that you are actually not making doublecheck after other LBC users, you cannot be 100% sure the whole LBC is not scam. Isn't that enough?

I've created a job on upwork and the freelancer is willing to complete it for $1100.
He's good at OpenCL and already made similar Eth projects.

He's going to rewrite oclvanitygen. Technical design specification is:

1. An option to read bitcoin addresses from a text file; addresses can be compressed and uncompressed;
2. Check the generated addresses against the set and return a match if found;
3. Periodically output the current private key to a file;
4. An option to pass the private key to start with;
5. Optimize the computation of the public address by doing all cryptography-related computations on GPU (do not pass any pre-computed data to the OpenCL kernels);
6. Remove saving hashes to the GPU's memory; check the addresses immediately;
7. Batched inversion is done in local memory (right now it's in global GPU memory)

I want to split this $1100 to 2-3 persons. Everyone will get sources and binary.
I hope we will come to gentlemen agreement and will divide ranges to three parts.

I mean, for example 56 bounty is from 72057594037927936 to 144115188075855872.
One takes the first third, second the middle, third - the last.

And of course I hope the sources and binary version would not go to public.