Bitcoin Forum
December 08, 2016, 04:11:35 PM *
News: Latest stable version of Bitcoin Core: 0.13.1  [Torrent].
 
   Home   Help Search Donate Login Register  
Pages: « 1 2 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ... 155 »
  Print  
Author Topic: Vanitygen: Vanity bitcoin address generator/miner [v0.22]  (Read 809317 times)
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
July 26, 2011, 04:48:12 PM
 #181


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?
Joric didn't commit for almost 2 weeks now so I don't know if he wants to continue its development
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

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
1481213495
Hero Member
*
Offline Offline

Posts: 1481213495

View Profile Personal Message (Offline)

Ignore
1481213495
Reply with quote  #2

1481213495
Report to moderator
1481213495
Hero Member
*
Offline Offline

Posts: 1481213495

View Profile Personal Message (Offline)

Ignore
1481213495
Reply with quote  #2

1481213495
Report to moderator
Advertised sites are not endorsed by the Bitcoin Forum. They may be unsafe, untrustworthy, or illegal in your jurisdiction. Advertise here.
1481213495
Hero Member
*
Offline Offline

Posts: 1481213495

View Profile Personal Message (Offline)

Ignore
1481213495
Reply with quote  #2

1481213495
Report to moderator
Shevek
Sr. Member
****
Offline Offline

Activity: 252



View Profile
July 27, 2011, 06:57:53 AM
 #182

Having Generated an address I want how do I get it in the client?
Use this tool: https://github.com/jackjack-jj/pywallet

Nice 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.

Proposals for improving bitcoin are like asses: everybody has one
1SheveKuPHpzpLqSvPSavik9wnC51voBa
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
July 27, 2011, 07:49:58 AM
 #183

Having Generated an address I want how do I get it in the client?
Use this tool: https://github.com/jackjack-jj/pywallet

Nice 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.
It works, but reads the keys with --importprivkey, --info is just a non-argument flag
I know it's not practical, i'll change that and put some examples in the README too

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
HostFat
Staff
Legendary
*
Offline Offline

Activity: 2296


I support freedom of choice


View Profile WWW
July 27, 2011, 12:34:35 PM
 #184

Can someone upload the oclvanitygen win32 bin somewhere? Smiley

Eternity Wall: Messages lasting forever - The Rock Trading (ref): A good exchange / gateway Ripple, with support for multisig, since 2007. 
https://bitcointa.lk: Bitcointalk backup if offline - Bitcoin Foundation Italia - Blog: http://theupwind.blogspot.it
winnetou
Sr. Member
****
Offline Offline

Activity: 361


View Profile
July 27, 2011, 08:37:14 PM
 #185

great tool, tried it in my vm and got a lot of sex addresses, my favorite: 15mWHVWtR4fX66VTg1Ytn1dCB1RpX8pimp Cheesy is there also a macintosh binary available?
dinox
Full Member
***
Offline Offline

Activity: 126


View Profile
July 27, 2011, 09:15:41 PM
 #186

great tool, tried it in my vm and got a lot of sex addresses, my favorite: 15mWHVWtR4fX66VTg1Ytn1dCB1RpX8pimp Cheesy is there also a macintosh binary available?
We are working on that.

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.
Nothing changed, I use the same old version as last time. poclbm miner works fine using opencl. I'll try downloading newest version and the clinfo thingy tomorrow.

Btw, should I push the changes I've done for compiling it on osx for review?

blockchain.info/fb/1dinox - 1Dinox3mFw8yykpAZXFGEKeH4VX1Mzbcxe
Active trader on #bitcoin-otc - See here - Proof that my nick is dinox here
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
July 28, 2011, 12:17:30 AM
 #187

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

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

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
enmaku
Hero Member
*****
Offline Offline

Activity: 742



View Profile WWW
July 28, 2011, 12:33:54 AM
 #188

Can someone upload the oclvanitygen win32 bin somewhere? Smiley

+1, wish it were as easy as Linux' gcc for win32 Tongue

samr7
Full Member
***
Offline Offline

Activity: 140

Firstbits: 1samr7


View Profile
July 28, 2011, 12:47:32 AM
 #189

Can someone upload the oclvanitygen win32 bin somewhere? Smiley

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.
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
July 28, 2011, 01:06:04 AM
 #190

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.
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
Code:
case 'N':
addrtype = 52;
break;
'privtype = 180;' is missing

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
samr7
Full Member
***
Offline Offline

Activity: 140

Firstbits: 1samr7


View Profile
July 28, 2011, 01:18:24 AM
 #191

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
Code:
case 'N':
addrtype = 52;
break;
'privtype = 180;' is missing

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.
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
July 28, 2011, 01:30:29 AM
 #192

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

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
Sukrim
Legendary
*
Offline Offline

Activity: 1848


View Profile
July 29, 2011, 05:04:46 AM
 #193

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...

https://bitfinex.com <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with this refcode: x5K9YtL3Zb
Mail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
July 29, 2011, 06:32:38 AM
 #194

Edited: nvm

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
Sukrim
Legendary
*
Offline Offline

Activity: 1848


View Profile
July 29, 2011, 06:50:43 AM
 #195

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?

https://bitfinex.com <-- leveraged trading of BTCUSD, LTCUSD and LTCBTC (long and short) - 10% discount on fees for the first 30 days with this refcode: x5K9YtL3Zb
Mail me at Bitmessage: BM-BbiHiVv5qh858ULsyRDtpRrG9WjXN3xf
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
July 29, 2011, 07:17:14 AM
 #196

Oh sorry I'd better wake up correctly before posting...
Well, for now nothing does that, but I can look into that

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
July 31, 2011, 05:56:16 PM
 #197

I got it working! With some playing on makefile though

5.7 16.3 (with last version) Mkey/s on a Sapphire 5850

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
jackjack
Hero Member
*****
Offline Offline

Activity: 882


May Bitcoin be touched by his Noodly Appendage


View Profile
July 31, 2011, 06:55:20 PM
 #198

I found an error (which was not here before I believe):
When I use the case-insensitive flag, Namecoin addresses are seen beginning with a 'n', which is not possible with the 52 addrtype
Then this is what I got:
Code:
Prefix 'n1d' not possible
Hint: valid namecoin addresses begin with "M" or "N"

I tried to modify that in your code, but didn't find where to change that

Own address: 19QkqAza7BHFTuoz9N8UQkryP4E9jHo4N3 - Pywallet support: 1AQDfx22pKGgXnUZFL1e4UKos3QqvRzNh5 - Bitcointalk++ script support: 1Pxeccscj1ygseTdSV1qUqQCanp2B2NMM2
Pywallet: instructions. Encrypted wallet support, export/import keys/addresses, backup wallets, export/import CSV data from/into wallet, merge wallets, delete/import addresses and transactions, recover altcoins sent to bitcoin addresses, sign/verify messages and files with Bitcoin addresses, recover deleted wallets, etc.
samr7
Full Member
***
Offline Offline

Activity: 140

Firstbits: 1samr7


View Profile
August 01, 2011, 04:30:15 AM
 #199

I posted a couple of new versions of vanitygen.  Summary of changes:

  • [0.14] Add jackjack's fix for namecoin private keys
  • [0.14] First release of oclvanitygen
  • [0.15] Include the OpenCL kernel in the zip file
  • [0.15] Warn when using NVIDIA driver on Windows other than known-working version

The oclvanitygen kernel code seems to trigger problems in a number of OpenCL driver stacks.  Certain NVIDIA drivers on Windows and Linux seem to produce invalid PTX code, to the point that commenting out some number of lines in one of the kernels fixes the problem (but the commented lines are required for correct results).  It also seems to cause AMD's KernelAnalyzer to crash, and AMD's CPU OpenCL compiler is unable to build a binary without crashing, either from oclvanitygen itself, or any of the standalone OpenCL compiler programs.

I got it working! With some playing on makefile though

5.7 16.3 (with last version) Mkey/s on a Sapphire 5850

I'm glad you got it to work!

That's about the expected key rate with the latest version on a high end Radeon card.

NVIDIA cards aren't quite as fast, my GTX 285 produces about 6.3 Mkey/s.

I found an error (which was not here before I believe):
When I use the case-insensitive flag, Namecoin addresses are seen beginning with a 'n', which is not possible with the 52 addrtype
Then this is what I got:
Code:
Prefix 'n1d' not possible
Hint: valid namecoin addresses begin with "M" or "N"

I tried to modify that in your code, but didn't find where to change that
Nice find.  I'll see about fixing this.
dinox
Full Member
***
Offline Offline

Activity: 126


View Profile
August 01, 2011, 06:30:17 PM
 #200

Made a pull request for reviewing, please dont pull it yet since compiling no longer works on osx. I'm not so good in C but do you have an idea of what's causing the problem samr7? See error output here

blockchain.info/fb/1dinox - 1Dinox3mFw8yykpAZXFGEKeH4VX1Mzbcxe
Active trader on #bitcoin-otc - See here - Proof that my nick is dinox here
Pages: « 1 2 3 4 5 6 7 8 9 [10] 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 ... 155 »
  Print  
 
Jump to:  

Sponsored by , a Bitcoin-accepting VPN.
Powered by MySQL Powered by PHP Powered by SMF 1.1.19 | SMF © 2006-2009, Simple Machines Valid XHTML 1.0! Valid CSS!