I tried to search for a specific wallet address just for fun, and it the program crashed. It was not until i removed 6 characters from the end of the public address did it do its thing. I know the chances of finding 1 specific public address is like winning the lottery 500 times in a row but i would like to be able to. Is my hardware the problem or the code?

I tried to search for a specific wallet address just for fun, and it the program crashed. It was not until i removed 6 characters from the end of the public address did it do its thing. I know the chances of finding 1 specific public address is like winning the lottery 500 times in a row but i would like to be able to. Is my hardware the problem or the code?

In order to speed up code execution the final step, adding the checksum to the result is skipped.This checksum is 32 bit, equivalent to 6-7 characters in base58.

You may want to run with the regular expression option, in this mode the checksum part is added.Code execution will slow down considerable though.

My code actually reports the prefix being to too long when using a complete address in stead of crashing,there are many versions out there :-).

Is there a parameter for vanitygen to stop it from outputting stuff to the console?I want it to run on the background of my ubuntu server, so I use './vanitygen -i 1jerodev &', but it keeps sending things to the console and it is verry anoying.

Moreover, it's an 'on average'. It's possible you could get a hit a split second after you call the command, and it's also possible it would take centuries to get a hit.

Note that this is if you absolutely must generate one for whatever reason. If you're talking about mining, then perhaps a 'maximum prefix' would be contingent upon profitability, in which case you'd have to consider whether the bounty equals or exceeds your expenses for vanity mining - and that is a calculation that is, again, subject to that 'on average' caveat.

The only theoretical limit is, I think, 30 (including the leading '1'), as that's when you exhaust the number of characters available in a bitcoin address to begin with.

I raised it to 22Mkey by overclocking the card. got no idea which params to try, but it's late now for me. maybe i'll try tomorrow.

Basically the -s, -t, -g, -b parameters, there's really not much else to tweak. A better option would be to see if you can optimize the actual code further / specifically for your card.Also use the "-F compressed" option, that should boost performance a bit further.And if you're not already using the lifeboat version, see if that gives you a performance boost as well - though read its thread for details and possible concerns.

But if you want further control - say, only mine if a given address should be generated within a week (on average!) - you'd have to set something up manually or mess with the source code yourself.

Also just to note (though I believe you understand this, mostly repeating it here for the new eyeballs on this thread) - keep in mind that it isn't really a 'pool' so much as a distributed task. If you don't find a requested vanity address, you get nothing, even if your machine's been powering away at it 24/7.