Topic: New Pywallet 0.0.1a6 (Read 31114 times)

Thank you

Hey I have lost a wallet.dat file and allready sendt you a PM, if anyone is good with pywallet or general file recovery I have a 0.4BTC bounty to finder off file   Please contact me

Hi JackJack,

I've sent you a private message ealier today, but I would love to have your opinion on an issue i'm having with my alt coin wallet. (onion wallet)
I have the feeling you could be my hero in this quest for a solution.
Wallet cannot dump private key and cannot send out coins.
I wonder what's the latest, trusted pywallet version that's available right now.. and what about that tool you were working on?
note: as said in my private message: i'm willing to reward you if this problem can get solved..

pywallet really is enough, if you have the patience & confidence to use it.

thanks JJ

No, except on my PC

It is altcoin friendly
I'd release it but I don't think it's still necessary, things have changed since I started it, editing wallets is easier from clients now
If many people think I should finish it, I will, but I think pywallet is enough

would love to see an altcoin friendly update

Is this active anywhere?

sem ~ see my comment above and also some recent e-mail representing yet another of my recent concern (not here on this forum but it should emerge eventually)

-abisprotocol

Hello, jackjack

My little story) :

In 2011 i have coins at deepbit and local bitcoin qt wallet on my PC (windows xp). In 2012 I transfer by a mistake to old bitcoin qt wallet bitcoins from deepbit... Wallet already was deleted and no backups. Wallet doesn`t runs after transaction never. And it`s unencripted.
Now I recover wallet.dat and trying to get my bitcoins. Already install bitcoin qt and it`s totally syncronized.Replace recovered wallet.dat to bitcoin-qt directory. But balance - 0.00 and there are a new receiving address. (as i see it`s normal).

Can I check wallet.dat is the right one to that address by pywallet? And if yes, tell me how please... Or maybe some different way.

This is very interesting ~ I just looked at the github.
 [[edited 22 Dec 2014 edit: the following is the DO NOT DOWNLoad from link - perhaps you could have sandboxed it and done something but I didn't, I just used it for observation.  As I understand it you should follow the signatures of what is posted by JackJack himself and confirm it before actually downloading and using!]]

( https :// github .com / jj-jackjack / pywallet )


[YET ANOTHER EDIT after reading this...  I am of the understanding that the fake one is jj-jackjack ....?? Right? Shit, now I am confused, except for the "Check JackJack's signature" part.. because all this has my head twisted around. Please feel free to private message me and tell me I am missing something really important and because of me the world is going to suffer and please make sure to explain step by step how I should change this post because I feel like I am missing something here!]

[[ As per a thread above, a different jackjack-jj link is alleged to be a scam link which supposedly removes BTC.]]
[[More 22 Dec. 2014 edit below:

A few thoughts / suggestions come to mind as things that could be added / changed...

1) Code associated with standalone mixer plugin by BkkCoins could be added in (so that you wouldn't have to add the plugin),
currently this appears at
https://github.com/tkhaew/electrum/blob/mixer_plugin/plugins/mixer.py
Default folder will be something like this to put it in (if used as plugin for Electrum), poss. different version numbers.
/usr/local/lib/python2.7/dist-packages/Electrum-1.9.5-py2.7.egg/electrum_plugins/

[[THE tkhaew stuff is NOT fake by my understanding but.. correct me if I am wrong]]

2) Stealth support / Charity Donations section / http://abis.io ~  See https://github.com/spesmilo/sx/tree/master/tools for details

[[ http://abis.io and my repositories at https://github.com/ABISprotocol?tab=repositories including repositories I help manage such as those at BTC Foundation and Lighthouse:  I've observed them and all seems well. But if you are a contributor to one of the repositories and been affected by the recent problems in different countries / regions of late, please e-mail me and let me know (if you can), or if you can't, please use one of your network to connect with me in whatever way makes sense.

[[some stuff related to BTC and some stuff related to BCN]]]

The above is basically related to use of BTC, but I am also reminded that BCN (bytecoin.org / ring signatures / cryptonight) does not currently have a GUI and they are seeking one.  I wonder if this pywallet code could also be used / rewritten to create the first GUI wallet for BCN, as well. [[[don't know at this point, you'd have to ask the BCN devs]]]

[[  see also signature / code more recently posted from jackjack above - I've made another edit from Dec 22 2014 below... ]]


Not a scam is BitName / IDMAS evoled. Yes those are projects that I  am hoping will one day become reality, but currently has nothing because it is shown currently in another repository through github.com/cjbauer who has already developed concept much more: https://github.com/abisprotocol/bitname

I have been saying this again and again in Unsystem mailing list... but we need way better gpg procedures because between the attacks on tor networks and issues with tor relays, attacks on anarchist communities, attacks on various communities in usa / EEUU, some recent problems with git, all this happening almost at once, you could say it made my head spin.  let's please work offline on some procedures that are easy to use for our respective communities for gpg primarily in ways that make sense for all concerned regardless of whether or not we are part of core dev teams or just periodic commenters, thanks.  


uhhhhhhhhh..... sigh

Armory has it's own daemon? heheh. I'll have to check that out. But, as far as I know, Armory still does not support use of compressed keys. I'd like to avoid being responsible for adding unnecessary bloat to the block chain. I mean, 10k addresses times 256 extra bits.

Have you looked at armoryd?

While I'm at it, another simple request. Bulk import keys into an encrypted wallet.dat from csv. You may need the the private keys to derive the public keys, but the private keys will not be in the new wallet.dat.

I'm trying to create a watch-only full node, using Bitcoin Core. It's on the internet, therefore I prefer it to not have any private keys. All imported keys will be reserve keys or part of the pool. Core will not know the password/passphrase (I give it a dummy one at the start, when first creating the empty-wallet.dat) so it can't create new keys, and will use existing keys as needed.

I'm trying to import 5000 to 10000 keys, where the result will be a wallet file that only has public keys and bitcoin addresses, and the private keys are nuked.

If hackers steal the file, privacy may be lost, but no bitcoins will be lost.

Hi, jackjack.

You may want to at some point consider adding the fix-wallet-creation-crypto patch from the original pywallet in -- it looks like new pywallet is affected by those same bugs. You'd also need to re-add append_PKCS7_padding().

https://github.com/jackjack-jj/pywallet/commit/b52c955f8c93a75745166ebf281448016e1f22e2

-Chris

I have a simple request: have it get as input a typical encrypted wallet.dat, and spit out a new-wallet.dat file without the private keys. You probably don't even need the password.

The old pywallet can but not this one yet
I'll add that in the next version

jackjack, quick question. Can I use this new version to import a bunch of bitcoin addresses into a brand new wallet.dat file? With the encrypted wallet but nuked private keys. My purpose is to upload a watch-only wallet into a full node on the internet. It can see everything, but can't do anything, and hackers can't steal anything.

Here's my plan:
1. generate a few thousand addresses, using vanitygen or bitaddress or whatever.
2. start bitcoin core with an empty wallet, encrypt it with a password, then close it (shut down core).
3. use pywallet to import those addresses (I have the public key of course) to the new empty wallet.
4. run bitcoin core. It should now see all the addresses.

My issue is bulk-importing. Can pywallet accept a file as input, and what format should I put the keys in. (Does it need the private keys, or just the public keys, which is different from the bitcoin address.)

Alternatively, is there a way to get an existing wallet.dat and just kill the private keys in them? (by overwriting the part with zeros.)

What I might do instead is to import the private keys using core. Then have pywallet (or another tool) overwrite the parts where the private keys exist.

The obvious alternative is to simply import the keys, and use a 256-bit password for bitcoin core. However, I want to obliterate the private keys.

Yes I'll do that

is a windows GUI version still coming for this release jackjack?

Looks like the 0.0.1a5 was broken
I'm putting a changelog in the OP, I hope I'll think about keeping it up-to-date for the next version

GzDu81IRrahUkquiTMHmhN39qVg3uewHPoRCHrFRQDjt9/vHLX/13fgdUwhGZ6s1slqIWKySJq+BZHI8DonSRig=

http://npw.jampa.eu/files/NPW_0.0.1a6.py