Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22] - page 182. (Read 1153620 times)
I got it working! With some playing on makefile though
5.7 16.3 (with last version) Mkey/s on a Sapphire 5850
Oh sorry I'd better wake up correctly before posting...
Well, for now nothing does that, but I can look into that
Well, for now nothing does that, but I can look into that
It imports adresses found by vanitygen on the fly in a wallet.dat? At least I don't see anything about that in the thread there...
Maybe pywallet could at least take the output file of vanitygen as input for easier import?
Maybe pywallet could at least take the output file of vanitygen as input for easier import?
Edited: nvm
Would be neat to have pywallet (or some similar functionality) somehow integrated in this --> specify a wallet file at launch and get the vanity key(s) directly inserted (or after some yes/no confirmation).
After all, this is one of the most common use cases I guess...
After all, this is one of the most common use cases I guess...
I just sent a pull request before viewing your post
As it used to be 239 for testnet and 128 for bitcoin (mentionned in february) I thought it was rather accepted by all
Moreover Joric did use chr(addrtype+128) to get privkeys
As it used to be 239 for testnet and 128 for bitcoin (mentionned in february) I thought it was rather accepted by all
Moreover Joric did use chr(addrtype+128) to get privkeys
Thanks to you I just figured out something important (privtype=addrtype+128)
But anyway, isn't it supposed to be '7' for namecoin addresses? My main problem was that: I couldn't import namecoin keys, pywallet saw them as bitcoin ones
Yeah, after more tests I'm nearly sure that you use 128 instead of 128+52 for namecoin privkeys versions
I look at the code and tell you what I find
Edit: Found
'privtype = 180;' is missing
But anyway, isn't it supposed to be '7' for namecoin addresses? My main problem was that: I couldn't import namecoin keys, pywallet saw them as bitcoin ones
Yeah, after more tests I'm nearly sure that you use 128 instead of 128+52 for namecoin privkeys versions
I look at the code and tell you what I find
Edit: Found
Code:
case 'N':
addrtype = 52;
break;
At this point, I think your pywallet code is the only way to get private keys into or out of a namecoin wallet, so you get to set the conventions, and I will update vanitygen to follow this rule.
I think I found an error in the code: when vanitygen writes the base58 private key, it always uses 0 as address version instead of addrtype value
Can you give more details on this?
If it were using 0 as the address version, then wouldn't the encoded private key start with a 1? It should typically produce private keys starting with '5' for regular bitcoin and namecoin addresses, and '9' for testnet addresses.
But anyway, isn't it supposed to be '7' for namecoin addresses? My main problem was that: I couldn't import namecoin keys, pywallet saw them as bitcoin ones
Yeah, after more tests I'm nearly sure that you use 128 instead of 128+52 for namecoin privkeys versions
I look at the code and tell you what I find
Edit: Found
Code:
case 'N':
addrtype = 52;
break;
Can someone upload the oclvanitygen win32 bin somewhere? 
There's no release of oclvanitygen yet, just what's in git, and that's only half baked right now. If this doesn't bother you, I posted a binary here. Also, please let me know if it works or not, I don't have a windows system with a GPU to test it on, and AMD's OpenCL CPU compiler blows up on the kernel.
Edit: The link was updated, the first zip file was missing the OpenCL kernel.
Btw, should I push the changes I've done for compiling it on osx for review?
Please do!!
I think I found an error in the code: when vanitygen writes the base58 private key, it always uses 0 as address version instead of addrtype value
Can you give more details on this?
If it were using 0 as the address version, then wouldn't the encoded private key start with a 1? It should typically produce private keys starting with '5' for regular bitcoin and namecoin addresses, and '9' for testnet addresses.
Can someone upload the oclvanitygen win32 bin somewhere?
+1, wish it were as easy as Linux' gcc for win32
Ok I just read the code, it obviously use privtype which is always 0 (even for namecoin) except for testnet where it is 239
I really don't understand why, I think it's just making a mess
Moreover, pywallet (both) doesn't understand and see the address as a bitcoin one
great tool, tried it in my vm and got a lot of sex addresses, my favorite: 15mWHVWtR4fX66VTg1Ytn1dCB1RpX8pimp 
is there also a macintosh binary available?
We are working on that. is there also a macintosh binary available?I changed to a compiler called clc and it compiled calc_addr.cl with no errors/warnings.
That's good, but what changed? Did you pull the git changes from Thursday 7/21 and try again, or is this with the same calc_addrs.cl that caused the segv last time?
Well, I'm stumped. According to Apple's developer site, GLD is the modular OpenGL driver interface. However, Google doesn't seem to know _anything_ about a "gld context creation failed" message.
What version of OS X is this? Can you pastebin the output of clinfo? Are you able to run any other OpenCL software on this machine, besides just the clc compiler? Can you post a link to this compiler?
If you really think the third parameter is causing the problem, it would be a good experiment to change it to CL_QUEUE_PROFILING_ENABLE or even CL_QUEUE_OUT_OF_ORDER_EXEC_MODE_ENABLE.
Btw, should I push the changes I've done for compiling it on osx for review?
great tool, tried it in my vm and got a lot of sex addresses, my favorite: 15mWHVWtR4fX66VTg1Ytn1dCB1RpX8pimp is there also a macintosh binary available?
is there also a macintosh binary available? 
Can someone upload the oclvanitygen win32 bin somewhere?
Having Generated an address I want how do I get it in the client?
Use this tool: https://github.com/jackjack-jj/pywalletNice fork! I love the feature --importhex. But --info does not work. :-(
I also like the clean way EC-mathematics are presented. Perhaps I'll use them for my own purposes.
I know it's not practical, i'll change that and put some examples in the README too
Having Generated an address I want how do I get it in the client?
Use this tool: https://github.com/jackjack-jj/pywalletNice fork! I love the feature --importhex. But --info does not work. :-(
I also like the clean way EC-mathematics are presented. Perhaps I'll use them for my own purposes.
Use this tool: https://github.com/jackjack-jj/pywallet
jackjack, I see you have a fork of Joric's repo, are you developing pywallet now?
For such a handy tool, it's almost being passed under the table. Perhaps it deserves a top-level thread?
I prefer to bring many improvements available immediately for people that might need it instead of waiting him to accept my pull requests (he looks busy with his new tool). For example my other script that gets rid of 0/unconfirmed tx's needs my pywallet fork
Use this tool: https://github.com/jackjack-jj/pywallet
jackjack, I see you have a fork of Joric's repo, are you developing pywallet now?
For such a handy tool, it's almost being passed under the table. Perhaps it deserves a top-level thread?
Having Generated an address I want how do I get it in the client?
Use this tool: https://github.com/jackjack-jj/pywallet 
Having Generated an address I want how do I get it in the client?
Jump to: