with passworded files, it will Segmentation fault (core dumped),
with non password files, just do nothing at all, you have to pipe it out.
only addresses in there, no keys as said, btc wallet version before hall brought this thing out, will give keys.
this one only lines like this.
pool 00000065 2020/03/12 1GWeaBZYsZ5XvovhuagCKCFHaPoDKkrWix
any one got that version lying around as .exe thanks ahead.
thanks a lot for that ssl issue fix thing was already on it few hours before you posted. thanks
Topic: halfinney/bc_key (Read 574 times)
Sorry for bumping this really old topic, but I have patched Hal Finney's bc_key fork to compile on OpenSSL 1.1.x.
His program, and the one by dirtyfilthy, currently work on OpenSSL 1.0.x but I think Linux distros are starting to phase that version out for 1.1.x.
Right now if you try to compile his program on 1.1.x you get a linking error about CRYPTO_malloc_init(). This function was removed from the OpenSSL library and the functionality has it provided is automatically handled by OpenSSL now. So I removed the function call from my fork and it started working again.
My fork: https://github.com/ZenulAbidin/bc_key
His program, and the one by dirtyfilthy, currently work on OpenSSL 1.0.x but I think Linux distros are starting to phase that version out for 1.1.x.
Right now if you try to compile his program on 1.1.x you get a linking error about CRYPTO_malloc_init(). This function was removed from the OpenSSL library and the functionality has it provided is automatically handled by OpenSSL now. So I removed the function call from my fork and it started working again.
My fork: https://github.com/ZenulAbidin/bc_key
could someone explain to me what is this script written by halfinney the developer who helped Satoshi Nakamoto
BTChttps://github.com/halfinney/bc_keyBTC
https://github.com/halfinney/bc_key
BTChttps://github.com/halfinney/bc_keyBTC
https://github.com/halfinney/bc_key
Listen to the man himself. I'm not that technical person though, maybe someone can elaborate it, but it's good to hear directly the reasoning from Hal through his post below.
I modified the bc_key program originally by dirtyfilthy, to dump out info on everything in the wallet.dat file.
https://github.com/halfinney/bc_key
It prints out keys (as addresses), transaction hashes, key pool addresses, address book names, etc.
Run it as:
./bc_key EVERYTHING ~/.bitcoin/wallet.dat
or wherever your wallet.dat might be. I like to pipe the output through sort.
I've noticed two oddities in the couple of wallets I've looked at:
There are no wkey entries, only keys. wkeys would hold extra stuff with Merkle branches and all that. Is this not yet (or no longer) supported, present in the code for the hypothetical "lightweight client"?
I have a very old wallet, created by the first version of bitcoin. Recently I upgraded to a modern version. However, the wallet has no pool entries. I thought the upgrade would create 100 keypool entries?
https://github.com/halfinney/bc_key
It prints out keys (as addresses), transaction hashes, key pool addresses, address book names, etc.
Run it as:
./bc_key EVERYTHING ~/.bitcoin/wallet.dat
or wherever your wallet.dat might be. I like to pipe the output through sort.
I've noticed two oddities in the couple of wallets I've looked at:
There are no wkey entries, only keys. wkeys would hold extra stuff with Merkle branches and all that. Is this not yet (or no longer) supported, present in the code for the hypothetical "lightweight client"?
I have a very old wallet, created by the first version of bitcoin. Recently I upgraded to a modern version. However, the wallet has no pool entries. I thought the upgrade would create 100 keypool entries?
could someone explain to me what is this script written by halfinney the developer who helped Satoshi Nakamoto
BTChttps://github.com/halfinney/bc_keyBTC
https://github.com/halfinney/bc_key
BTChttps://github.com/halfinney/bc_keyBTC
https://github.com/halfinney/bc_key
Jump to: