Have you tried running two SpreadX11 instances simultaneously? What happens then?
I am not aware that a limit exists, but maybe you can spread your GPUs over multiple instances.

It works like this:
if your wallet is unlocked and you have "auto import to wallet" activated then you won't ever see the privkeys anyway, because the moment a privkey is found it immediately disappears from the list (never showing the privkey, not even for a blink) and goes directly to your "receive coins" list.

So having access to the privkeys themselves is for people who don't want to use them in their wallet ANYWAY... but want to export them... and then delete the job.

Qt is just one of the parts that makes everything work, and the least important too, but you have to start somewhere.
I chose to first get uptodate with Qt because it interests me anyway, because I want to do OpenGL stuff with Qt using C++.

Yes, Scrutinizing the code allowed me to now have like a map of the code in my memory, this is very helpful.

I can't make any estimations anymore (I will get better at it over time), so I will just keep posting a screenshot or two everyday so you can judge for yourself.

There are just a few tiny things left, and we can go online with the preview version.

No problem, I enjoy working with you.
Take your time and keep the enthusiasm up!

If someone has captured a users computer the way you describe all hope is lost anyway.

But here's an update just for you.

A "Show Privkeys" Checkbox:



 

BTW, vanitygen shows its privkeys in clear text, and even all wallets will post a privkey in clear text when you do a dumpprivkey.

So ... I guess if you feel secure at home with your computer you can let "your private parts hang out"?

Thanks for your feedback.
Someone needs to tell the bitcoin devs that this is still a bug even with the newest bitcoin wallet.
I guess someone already told them.
You can check this out by creating a bitcoin address with the official vanitygen and then import it into the bitcoin wallet.
After importing a privkey with importprivkey the address will also appear in the address book list first, instead of the "receive coins" list, which is weird. I don't know what the devs were thinking?

lol, well played / thanks for the donation.

Did you also encounter the error I described earlier? That the imported address is first listed in the wrong list?

I already stole the 1 SPR you put into the address I too control... 

I guess you are going to send 10k to my Signature address, because that's just the kind of guy you are?

Because everyone else can read the screenshots just like you, lol.
Everyone that knows the privkey can access the SPR tied to this address.
So I am sure some people are already eying all those addresses, hoping that one of us makes a mistake. So ... careful!

Please only ever use the SPR address in my signature if you want to donate.  


EDIT: you see what happens now? You (or someone else) sent 1 SPR to the SPR address I gave you earlier.
And I too have this address in one of my testwallets.
So now the hilarious game starts: who of all of us sends the 1 SPR to another address FASTER than anyone else. lol

EDIT2: ofcourse all those problems disappear if you just keep the privkeys to yourself and also take a ...



Privkeys are nobodies business but yours.  

You can check that it works by doing this:

1) Please first backup your wallet.dat, or better remove it from your spreadcoin data folder and put it somewhere safe. So you can copy it back when you finished this test.
When you restart the wallet without a wallet.dat, it will create a fresh wallet.dat for you. That's what you want for this test.

2) CopyPaste the privkey (that starts with 7) of this address:


DON'T USE THIS ADDRESS FOR ACTUAL PAYMENTS!
Only use it for this test, to see that it will correctly show up in your wallet address list.

3) import it into your wallet by opening the Debug Console, and typing:


you can choose whatever you want for "SOMELABEL" , but keep the "false" at the end.

4) Now, Mr. Spread's wallet and even the newest bitcoin core wallet (and pretty much ALL other wallets I tested) all have this BUG that they will show an imported address in the wrong list, the address book, instead of the receive coins list.  
So what you need to do with those wallets is quit the wallet after the import and restart it. And then it will correctly show the imported address in the "Receive coins" tab.

The wallet I am working on doesn't have this bug, and won't require that you restart the wallet for importing vanitygen addresses.

5) After you have successfully tested this, stop the wallet again, remove the new wallet.dat, replace it with your old wallet.dat and everything is back to normal.

The privatekey is visible in the VanGenList for when you want to easily dump an address (copypaste) so you can import it to some other wallet, or do whatever the hell you want with it.
Basically it's like when you do a dumpprivkey in the debug console.

Don't share the privkey with anyone, or else your address can't be considered secure anymore (which also answers your question whether you can sell the address to someone. Your seller would somehow need to calculate the address without ever knowing the privkey. It is possible to do this, but not within the wallet.)

Normally it will only show the privkey when your wallet is LOCKED, and the found addresses can't immediately be transferred to your address list.
If your wallet is unlocked and you chose "auto-import" (or select the privkeys and click "import") the address(es) will immediately disappear from the VanGen-List and reappear in your wallet-address-list.

BTW, without Match Case addresses can be found much faster,
like 100-1000 times faster, depending on the length of the pattern you are looking for.

Next update.

correctly showing estimated time for a 50% Chance of finding an address:

I added notifications bubbles when a vanity address is found:

See bottom right corner.



Stay tuned, I'll keep you updated about the progress.

haha, yes, I plan to first find all available addresses that start with Sexy.....,
so see ya again in a few quadrillion years!

Ofcourse, sorry for not doing this earlier.


I am nearly finished.

This is what the in-wallet-vanity generator looks like ATM:



It allows you to add as many patterns as you want to the list.
Once you set the parameters up you can then start the job:



Found addresses show the privatekey (which you can either copypaste or auto-import into your wallet),
not yet found addresses show animated progress dots "............" until they are finished, plus
an estimated time for a 50% chance to find a match.

Just a little bit more patience, guys,
just a handful of small problems I need to solve and it's done.

I do have one comment (will have more later).

on page 1 you say:


I wouldn't express it like this, because many full nodes prefer to run in the disabled wallet mode.
Since a few versions ago, you can start a full node with the parameter -disablewallet and it will be more "lightweight" while still fullfilling all the tasks that a fully securing node needs to do.

Sure,

Very good, I will release a preview version for windows either later today or tomorrow.