I saw suggested on the forum that pywallet may work to import an address if used with the bitcoind client and the wallet is unlocked first. This seems like an easy way to work around encryption issues but I'm wondering if anyone has actually tried this?
Even though the wallet is unlocked briefly (by invoking command line to daemon client) that doesn't imply to me that the wallet file is actually then updatable by pywallet as it's possible/likely that an unlocked wallet is simply held in memory (at least I wouldn't assume that the disk file is re-written unencrypted). Anyone know for sure?
(btw I'm using the new 0.5.0 bitcoind as well as bitcoin-qt, which apparently writes the wallet differently than 0.4.0)
Topic: Pywallet 2.2: manage your wallet [Update required] - page 36. (Read 208227 times)
This is what I get, :
I think you used Python 3, you should try with Python 2 Code:
C:\Users\M7\AppData\Roaming\Bitcoin>pywallet.py --web --port 8989
File "C:\Users\M7\AppData\Roaming\Bitcoin\pywallet.py", line 109
_p = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2FL
^
SyntaxError: invalid syntax
Thanks for this jackjack!
This is what I get, :
Code:
C:\Users\M7\AppData\Roaming\Bitcoin>pywallet.py --web --port 8989
File "C:\Users\M7\AppData\Roaming\Bitcoin\pywallet.py", line 109
_p = 0xFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFEFFFFFC2FL
^
SyntaxError: invalid syntax
I tried it with Bitcoin 0.4 (not encrypted), and it worked fine for me (I only tried dumping the wallet contents and importing a private key).
Having said that, I'll still backup my wallet each time before using Pywallet.
Having said that, I'll still backup my wallet each time before using Pywallet.
Must try this someday.
I don't have my wallet encrypted, and tried to use pywallet on 0.4, and it threw an error because of the version number.
I went into the code, and changed maxversion from 32400 to 52400 and then imported into my wallet. Seemed to work fine.
(Warning, may kill your wallet)
I went into the code, and changed maxversion from 32400 to 52400 and then imported into my wallet. Seemed to work fine.
(Warning, may kill your wallet)
Hi there!
I had to leave for some time, sorry for that
I won't have as much time as before but I won't leave for months anymore
The priority is of course to make pywallet able to deal with encrypted wallets
I can't give you any ETA but I'll do my best
Btw, thanks for your pull requests on Github, I'll check and commit them
I had to leave for some time, sorry for that
I won't have as much time as before but I won't leave for months anymore
The priority is of course to make pywallet able to deal with encrypted wallets
I can't give you any ETA but I'll do my best
Btw, thanks for your pull requests on Github, I'll check and commit them
Thanks for the update!
Hi there!
I had to leave for some time, sorry for that
I won't have as much time as before but I won't leave for months anymore
The priority is of course to make pywallet able to deal with encrypted wallets
I can't give you any ETA but I'll do my best
Btw, thanks for your pull requests on Github, I'll check and commit them
I had to leave for some time, sorry for that
I won't have as much time as before but I won't leave for months anymore
The priority is of course to make pywallet able to deal with encrypted wallets
I can't give you any ETA but I'll do my best
Btw, thanks for your pull requests on Github, I'll check and commit them
Any word on getting this to work with 0.4's encrypted wallet?
Would be great if it was possible to bulk import private keys dumped from another wallet, in order to merge all keys from an old wallet into a new one.
Alternatively, does anyone know how to script this from a wallet dump using grep/sed etc?
edit: Also, how to check the balance of multiple addresses in one hit with copy and paste?
Alternatively, does anyone know how to script this from a wallet dump using grep/sed etc?
edit: Also, how to check the balance of multiple addresses in one hit with copy and paste?
I started looking at this as a way to import bitbills and other printed addresses without having to patch the client. I'm on Lion though and the broken bsddb thing is a pain. I use homebrew instead of mac ports, and eventhough I have a separate install of python, I still get "ImportError: No module named _bsddb." I'm moving my wallet onto another system soon, so its not a big deal for me (and not your fault).
One question. How does this handle the encryption that comes with 0.4?
Tried adding a private key. Broke my wallet. Seems to dump most of it just fine, though. One question. How does this handle the encryption that comes with 0.4?
I started looking at this as a way to import bitbills and other printed addresses without having to patch the client. I'm on Lion though and the broken bsddb thing is a pain. I use homebrew instead of mac ports, and eventhough I have a separate install of python, I still get "ImportError: No module named _bsddb." I'm moving my wallet onto another system soon, so its not a big deal for me (and not your fault).
One question. How does this handle the encryption that comes with 0.4?
One question. How does this handle the encryption that comes with 0.4?
Great program. I downloaded it, installed it and used it to browse my wallet and import a private key. It worked great. A small donation is on its way.
One very small feature request: Could you add the ability to import the mini private key format described here: https://en.bitcoin.it/wiki/Mini_private_key_format
All you have to do is take the SHA256 of the mini key to get the full private key and then go from there. Thanks, and keep up the fantastic work.
One very small feature request: Could you add the ability to import the mini private key format described here: https://en.bitcoin.it/wiki/Mini_private_key_format
All you have to do is take the SHA256 of the mini key to get the full private key and then go from there. Thanks, and keep up the fantastic work.
How will pywallet work with 0.4.0 client just released?
I've used pywallet several times for importing a vanitygen key into my wallet.
But now that I'm using an encrypted wallet I expect pywallet is going to choke.
Any plans to add support for the new version?
I suspect that supporting the encryption would be difficult. Is there an alternate way to solve this problem. Maybe the json-rpc interface can be used to import new keys after unlocking?
I've used pywallet several times for importing a vanitygen key into my wallet.
But now that I'm using an encrypted wallet I expect pywallet is going to choke.
Any plans to add support for the new version?
I suspect that supporting the encryption would be difficult. Is there an alternate way to solve this problem. Maybe the json-rpc interface can be used to import new keys after unlocking?
it might work, but wait for confirmation before you use it.
How will pywallet work with 0.4.0 client just released?
I've used pywallet several times for importing a vanitygen key into my wallet.
But now that I'm using an encrypted wallet I expect pywallet is going to choke.
Any plans to add support for the new version?
I suspect that supporting the encryption would be difficult. Is there an alternate way to solve this problem. Maybe the json-rpc interface can be used to import new keys after unlocking?
I've used pywallet several times for importing a vanitygen key into my wallet.
But now that I'm using an encrypted wallet I expect pywallet is going to choke.
Any plans to add support for the new version?
I suspect that supporting the encryption would be difficult. Is there an alternate way to solve this problem. Maybe the json-rpc interface can be used to import new keys after unlocking?
Jackjack,
I was wondering if pywallet supports 22-character "mini private keys" as I have been distributing on Casascius Physical Bitcoins and which I am trying to encourage as an adopted standard. Shorter keys is a universally desirable attribute both for hand-typed keys, and even QR codes (due to lower dot density, they are more readable and more dots can be spent on error correction).
If it is not yet implemented, the algorithm is simple: take the SHA256 of the 22 characters.
Validation is also fairly simple: always base58 alphabet, first character is always 'S'. A short algorithm is described in the Wiki for detecting typos, see "Mini private key format".
I was wondering if pywallet supports 22-character "mini private keys" as I have been distributing on Casascius Physical Bitcoins and which I am trying to encourage as an adopted standard. Shorter keys is a universally desirable attribute both for hand-typed keys, and even QR codes (due to lower dot density, they are more readable and more dots can be spent on error correction).
If it is not yet implemented, the algorithm is simple: take the SHA256 of the 22 characters.
Validation is also fairly simple: always base58 alphabet, first character is always 'S'. A short algorithm is described in the Wiki for detecting typos, see "Mini private key format".
How do I know if my wallet is corrupted? It's a stupid question, but I'd rather be on the safe side before I start sending out my vanity-addresses to people.
valid question, if you know how to run a brand new windows install or linux live cd or somthing, send a test amount of coins to a made address.
then on the brand new OS run bitcoin and let all blocks download. then disconnect the internet and never reconnect it after this point
now import the keys into the wallet with pywallet and slap it in the bitcoin client. now run the bitcoin client with the -rescan parameter. if you see the coins, your set, if not something messed up. if you ran the whole thing with a live cd your just turn the computer off and your good, if you installed an OS, use DBAN to wipe it out.
How do I know if my wallet is corrupted? It's a stupid question, but I'd rather be on the safe side before I start sending out my vanity-addresses to people.
Ok, I just checked, I confirm that C:\programmi is a "link" on the italian "windows 7", but it's a real "folder" on italian "windows xp".
Jump to: